Claves

Tenga en cuenta que destination=* y destination:lanes=* son dos conceptos diferentes para respaldar el anuncio de destinos señalizados, que pueden ser evaluados de manera diferente por el software de navegación. Como no entran en conflicto, ambos enfoques pueden coexistir en una vía en particular. Consulte la figura siguiente para obtener una ilustración.

Destinos por vía

Si la carretera es oneway=yes, entonces:

• Utilice la clave destination=*.

Si la carretera es bidireccional, entonces:

• Utilice destination:forward=* para describir los carriles en la dirección de la vía OSM.
• Utilice destination:backward=* para describir los carriles en la dirección opuesta a la forma OSM.

To enable the navigation software to announce the destination at a junction, the road leaving the intersection needs to carry the respective destination=* as signposted. Multiple destinations can be tagged as semicolon-separated values.

At least the first section of a road leaving the intersection must be tagged, however the tagging can continue on further segments until some different destination is signposted. This method allows navigation software to show continuously, which destination a driver follows e.g. along a dual carriageway.

Destinos por carril

For details about the :lanes suffix, see

Artículo principal: Lanes.

Often the destinations of a road differ from lane to lane, typically in conjunction with turn:lanes. To specify those for every lane, destination:lanes=* is used on the road segment leading into the intersection. To tag them:

If the road 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 road is bidirectional, then:

• Use destination:lanes:forward=* to describe the lanes in the direction of the OSM way. Visualize the road in the direction of the OSM way.
• Use destination:lanes:backward=* to describe the lanes in the opposite direction of the OSM way. Visualize the road in the opposite direction of the OSM way.

¿Dónde utilizar?

Use destination=* together with highway=* on pieces of highway after the position of the signpost or ground writing. For details, see also the examples.

Should I use destination=* keys or a destination_sign relation?

The destination=* implementation works when all inbound ways into a junction point are signposted with the same outbound destinations for the same outbound way. This makes destination=* a popular choice among editors for: motorways and other one-way type highways; on waterway relations (waterways are by definition 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 (could happen 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 necessary granularity.

To indicate the physical location of the signpost itself, use information=guidepost.

Danger of confusion

Do not confuse with highway=motorway_junction:

• It’s only used on motorway-exit-nodes.
• The official name of an exit is expressed with the key name=* . In some countries the same name is applied equally to every exit. If so, name=* may not correctly indicate an accurate destination.

Do not confuse 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 confuse 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 confuse with direction=*.

Software que usa esta función

Value

The value of the destination tag should be the contents of the sign, as it would be read from beginning to end. Different destinations on the same sign are separated with semicolons. (See examples below.)

This key is only for values which are explicitly indicated on signposts or ground writings.

Whether abbreviations (as they exactly appear on a sign) should be used in a destination tag is being discussed and is disputed, on this tag's talk page. Numerically speaking, by a ratio of 20:1, the editing consensus on whether to use abbreviations that appear on signs is no, and to use the same standards as given in Exit Info and as specified in the OSM standard Names: ("Don't do it": If the name can be spelled without an abbreviation, then don't abbreviate it").

Further Details

There are various tags to describe further details of destination signs:

• Proposal for sub-keys to provide additional information like reference, country, special signs/icons, more than one language
• Summary of destination keys regardless of state (in-use, proposed, ...)

Ejemplos

Nota: Hay una guía del uso de la etiqueta de destino (donde se aplica a señalización de salida) y numerosos ejemplos específicos de Estados Unidos en Exit Info.

Fuente de algunas imágenes: sicherestrassen.de

See also

• Explanation of how to determine the forward / backward direction of a way.
• The Article Lanes explains the :lanes suffix.
• 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
• Lane_assist - best practices for lane assistant using turn=* and destination=*
• Exit_Info - best practices for specifying on and off ramp sign information
• information=guidepost - destination signs on on hiking/cycling/skiing routes
• User:Mueschel/DestinationTagging - a summary of available destination tagging schemes

Validators:

• Rendering of destination tags and destination_sign relations: Destination Signs
• Destination Signs - to try out tagging schemes without uploading: Destination Signs - Tagging Sandbox
• Rendering of lanes tags and some traffic and destination signs: OSM Lane Visualizer
• CheckAutopista map: checkautopista2 wiki: CheckAutopista
• Overpass-turbo: Query to find motorway links without destination=*

Examples