Create and integrate new module for mapping human-usable labels to tag names #42

New Issue

2026-04-21T09:42:10Z

raucao commented

2026-04-21 09:42:10 +00:00

Rendering raw tag values with some extra rules works OK, but it's not ideal. Examples:

shop=bicycle just renders as Bicycle because we can't add "shop" to all the shop types where it doesn't make sense. And "Bike shop" would be even better than "Bicycle shop"
Some tags differ directly from how they're supposed to be understood. For example "tourism=chalet" is supposed to be a Holiday Home or Vacation Home, not a hut in the mountains.

The labels can then be used not just to render content, but also for tagging, when adding/editing OSM places in Marco.

Since any JS/TS app will have to do this themselves at the moment, we'll create a new shared module that can be used across apps.

Rendering raw tag values with some extra rules works OK, but it's not ideal. Examples: * `shop=bicycle` just renders as `Bicycle` because we can't add "shop" to all the shop types where it doesn't make sense. And "Bike shop" would be even better than "Bicycle shop" * Some tags differ directly from how they're supposed to be understood. For example "tourism=chalet" is supposed to be a Holiday Home or Vacation Home, not a hut in the mountains. The labels can then be used not just to render content, but also for tagging, when adding/editing OSM places in Marco. Since any JS/TS app will have to do this themselves at the moment, we'll create a new shared module that can be used across apps.

raucao added the ui/ux feature labels 2026-04-21 09:42:10 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: raucao/marco#42