|The key destination describes the content of signposts or ground writing indicating the names of the locations that the tagged way is heading to.|
|Used on these elements|
|Status: De facto|
|Tools for this tag|
The key destination=* describes the content of signposts or ground writing indicating the names of the locations that the tagged way is heading to. Thus navigation systems can refer to road signs that the driver actually sees.
Should I use destination=* keys or a destination_sign relation?
The destination=* implementation works when all inbound ways into a junction point indicate the same outbound destinations. This makes destination=* a popular choice among editors for: motorways and other one-way type highways; on waterway relations (waterways are by definition are one-way, their direction of flow); and for simple intersections.
At intersections where the indicated destination=* depends upon the direction the driver is arriving from (most typical at two way intersections or roundabouts), this implementation cannot provide enough detail to be unambiguous for navigation, because multiple destinations apply for the same outbound way. In these cases, the destination_sign relation must be used to provide the necessarily granularity.
|Key variation||Valid for||Description|
||Way||Describes the destination of the complete OSM way. Worthwhile only if used in combination with oneway=yes.|
||Direction||Describes the destination of all lanes of the OSM way, running in the same direction as the way itself.|
||Direction||Describes the destination of all lanes of the OSM way, running in the opposite direction as the way itself.|
||Lane||Describes the destination of each lane of the OSM way. Worthwhile only if used in combination with oneway=yes.|
||Lane||Describes the destination of each lane of the OSM way, running in the same direction as the way itself.|
||Lane||Describes the destination of each lane of the OSM way, running in the opposite direction as the way itself.|
Destinations per lane
For details about the
:lanes suffix, see Main article: Lanes.
Often the destinations of a road differ from lane to lane. To specify those for every lane, destination:lanes=* is used. To tag a way with different destinations for each lane we do the following:
If the way is oneway=yes, then:
- Use the key destination:lanes=*.
- Visualize the road in the direction of the OSM way.
- Add the lane-values to the value, starting with the leftmost lane and ending with the rightmost. Separate each lane-value with a | (vertical bar).
If the way has both directions, then:
- To describe the lanes in the direction of the OSM way use destination:lanes:forward=*. Visualize the road in the direction of the OSM way.
- To describe the lanes in the opposite direction of the OSM way use destination:lanes:backward=*. Visualize the road in the opposite direction of the OSM way.
forward and backward
Important note: If an entry and an exit share one OSM way, because they're not build separated, tag the destinations with destination:forward=* and destination:backward=*. If you change the direction of the OSM way pay attention also to exchange those destinations-tags, too! JOSM shows (at least since version 3208) a warning message and suggests to exchange destination:forward=* with destination:backward=*. iD swaps the tags automatically upon reversing the way.
Just take the text of the signpost or of the ground writing.
This key is only for values which are explicitly indicated on signposts or ground writings.
Where to use?
Danger of confusion
- It’s only used on motorway-exit-nodes.
- In its key name=* the official name of the exit is told, but in some countries this is on every exit for this junction the same one. So this name may be identical for every exit of this junction and therefore may not give a proper indication of the destination.
Do not mistake with Relation:destination_sign:
- This relation is designed for any sign showing in any direction (very flexible). In principle it would be possible to use the relation for every destination sign, but it brings all drawbacks for relations with it (in opposite to a simple tag like “destination”).
Do not mistake with designation=*:
- It is the official legal classification of a road or path and has nothing to do with the information about where a way goes to. Please don’t confuse to the similar writing.
Do not mistake with direction=*.
Software that uses this feature
destination=* is used in the following navigation apps:
Note: There is guidance and numerous United States specific examples of use of the destination tag (where it applies to Exit Signage), at Exit Info .
|Signpost||No. Link||Ctry||Tag(s)||Where to tag?||Occurrence||Note|
|430||DE||destination=Berlin||Directly at the highway=motorway_link||Signpost at a motorway entry||Additionally it is possible to set ref=A 2 on the highway=motorway.|
|448||DE||destination=Düsseldorf-Benrath||At the following highway=motorway_link||Signpost at motorway junctions||Additionally it is possible to set ref=26 on the highway=motorway_junction.|
|332||DE||destination=Mainz;Wiesbaden||At the following highway=motorway_link||Signpost at motorway exits||Multiple destinations are separated with a semicolon.|
|DE||destination:lanes=Oberhausen;Düsseldorf;Köln-Nord|Oberhausen;Düsseldorf;Köln-Nord|Oberhausen;Düsseldorf;Köln-Nord|K-Zentrum|Olpe;Gummersbach||At the highway=motorway directly after the signpost||Signpost at motorways|
|At the highway=motorway directly after the signpost||Signpost at motorways|
Source of some images: sicherestrassen.de
- Explanation of how to determine the forward / backward direction of a way.
- The Article Lanes explains the
- The relation destination_sign may provide detailed information about the type and colour(s) of the road sign
- Proposal for sub-keys to provide additional information like reference, country, special signs/icons, more than one language
- Discussion@wiki Discussion about right to exist in Germany and situation in US
- Discussion in the mailing list talk-de
- Signposts in Germany