Usage of the destination and destination:street tag with the street name

Hello! I’m Anastasia. I’m an OSM communications specialist on the OSM mapping team at Lyft.

Due to the lack of a unified approach in OSM, we would like to bring up the topic of using the destination:street/destination tags with street names.

While working on our Destination signs project (Exit and Destination Signs project · Issue #18 · Test-DCT/OSM-LYFT-DCT · GitHub) we came across the issue of tagging street names.
Currently while mapping US cities, we are relying on Minh Nguyen’s proposal in our workflow.
According to this proposal the destination:street tag is used only if the street name is a supplemental that accompanies a route shield.

But we encountered a different point of view. It seems, an active mapper strongly prefers to add all the street names only to the destination:street and massively modify our edits by moving values to the destination:street tag.

We’ve been following the discussions in the OSM slack channels and have come to the conclusion that there is no final decision yet on the use of the tag and no rules strictly prohibiting adding street names to the destination tag.

One of the main arguments in favor of the proposal is that many destination signs have both streets, cities (and/or other POIs) and the distribution to the different tags can break their priority order in navigation systems. As a result, drivers may receive information about a less significant POI instead of the street that is listed first and where the “exit” actually leads.

Ex: Motorway link has both destination=Tulsa Zoo and destination:street tag=Sheridan Road tags.
Here is a simulation: OSRM
Guidance ignores destination:street at all, while it’s a main destination.

We would greatly appreciate your input regarding the usage of the “destination:street” tag. Our goal is to reach a consensus and avoid any potential conflicts. Your thoughts and insights are invaluable in this process.

Thank you for your contribution!

3 posts - 2 participants

Read full topic

Ce sujet de discussion accompagne la publication sur