What is the proper use of destination tagging?

I’m confused by the use of the tags destination=* and destination:steet=* on a motorway_link exit ramp.

My example motorway_link exits OR 126 in Eugene, Oregon, way id:36925738, but there are many exit ramps with similar tagging in this area. It is tagged with destination=Autzen Stadium and also with the tag, destination:street=Country Club Road;Coburg Road. The destination:street tag is marked as deprecated in the Wiki but it is common (Taginfo shows 75K instances) and is apparently still very much in use.

The destination tag is intended to inform a driver of the town or city the exit leads to but in a city or residential area, the destination is often unclear or, as in this case, is not a city but two majot highways and one point of interest. IMO, such exits would be better served by using the destination:street tag, but that tagging has been deprecated. In my example, the sign for Autzen Stadium appears very close to the exit while there are several signs on the motorway 1/2 and 1/4 miles before the exit that advertise the upcoming exit as one going to Country Club Road and Coburg Road. In other words, the driver doesn’t see what’s on the signs on his GPS when approaching the exit because only the Autzen Stadium destination appears. It’s confusing and IMO misleading because except on game days the stadium isn’t the primary reason for taking that exit

I compile my own Garmin compatible maps for my GPS and I could add processing for destination:street tags in addition to the standard destination=* tag in my code but I wonder if that’s the wisest course considering that tag’s deprecated status. Another possibility would be to alter the destination tag to destination:Country Club Road;Coburg Road;Autzen Stadium.

I’m looking for opinions about the usage of both of those tags.


3 posts - 3 participants

Read full topic

Ce sujet de discussion accompagne la publication sur https://community.openstreetmap.org/t/what-is-the-proper-use-of-destination-tagging/102942