User:Minh Nguyen/destination:street

From OpenStreetMap Wiki
Jump to navigation Jump to search
Key:destination:street
Status: Draft (under way)
Proposed by: Minh Nguyen
Tagging: destination:street=*
Applies to: way
Definition: Supplemental road name that accompanies a route shield on a guide sign
Rendered as: Hidden

This is a proposal for a new destination:street=* tag for supplemental road names[1] that appear on freeway guide signs. This proposal builds on Proposed features/Destination details. It aims to address shortcomings in the definition for destination:street=* that was originally proposed in Exit Info and recently added to Proposed features/Destination details.

Proposal

A guide sign bearing a supplemental road name (Aurora Parkway).

destination:street=* contains a supplemental road name that accompanies a route shield on a guide sign at the beginning of a link road (such as at a motorway junction).

In some U.S. states, it is standard practice to accompany a route shield with the associated road name on guide signage. Supplemental road names are included to aid local motorists who are more familiar with the road name than the route number. They are not considered primary destinations.

A primary destination is placed beneath the route shield in full-size lettering. By contrast, a supplemental road name is placed to the right of the route shield, similar to a cardinal direction. A supplemental road name is usually set in small type, sometimes in fine print.

Use destination=* for a road name that appears as a primary destination, with the same prominent presentation that a place name typically receives. Do not assume that destination=* necessarily names the road to which the link road directly leads.

As with other destination:*=* tags, variations such as destination:street:lanes=* and destination:street:forward=* may occur in some cases.

Rationale

Routing software may include the supplemental road name in destination:street=* in turn instructions for informational purposes, as space or time allows. For example, a tool that renders realistic-looking guide sign diagrams[2] may use this tag to display the supplemental road name in the style described above. On the other hand, real-time turn-by-turn instructions may omit the supplemental road name if the maneuver location is imminent and not enough time is available to read the destination sign in full. The supplemental road name may also be omitted on a second or third reading of an instruction. This is in contrast to any road names in the destination=* tag, which are to be given the same prominence as any place names in that tag.

Relevant standards

In the United States, the national Manual of Uniform Traffic Control Devices discourages placing road names and city names on the same guide sign.[3] However, guide signs that mix road names and place names are widespread: road names and place names appear in the same font, with the road names often listed above the place names.

This proposal is about a related practice, widespread in some states, in which the road name is posted on a guide sign as a supplement to a route shield. A road's route number is presented to out-of-town motorists at the same time that the same road's more familiar name is presented to local motorists. To avoid information overload,[4] these supplemental road names are laid out differently than ordinary destinations: they appear to the right of a route shield in a smaller font. The details vary by state:

  • In Kentucky, KYTC has standardized supplemental road names in its Traffic Guidance Operations Manual (TO-404-38). The road name is set in all capital letters at the same size as a cardinal direction. It is only included if space allows, the road is maintained by the state, and the name does not indicate a commercial or industrial establishment.
  • In Maryland, the State Highway Administration has standardized supplemental road names in Maryland Standard Highway Signs. Compare sign D3-2(4) with the road name to sign D3-2(3) with the cardinal direction. The road name is set in title case at a slightly smaller size than the main destinations. It may be left, center, or right aligned. In some cases, there is no destination besides the shield and accompanying road name.
  • In Massachusetts, MassDOT's Guide Sign Policy for Secondary State Highways is silent on the issue of road names next to route shields. The road name is set in all capital letters at the same size as a cardinal direction and center aligned.
  • In Tennessee, TennDOT's Supplemental Rules for Guide Signs on Freeways, Expressways and Conventional Highways appears to proscribe supplemental road names on guide signs, yet examples include guide signs to Saturn Parkway.

A distinction between supplemental road names and other destination road names appears to be peculiar to the MUTCD as implemented in these states. Countries that adhere to the Vienna Convention on Road Signs and Signals are unlikely to need the proposed tag; all road names can go into destination=* without losing information about the names' prominence.

Examples

Road names are signposted beside route shields on guide signs in at least the following states:

Tagging

The destination:street=* tag is to be used in conjunction with tags such as destination=*, destination:ref=*, destination:symbol=*, etc.

Applies to

Ways, especially ways tagged highway=motorway_link or highway=trunk_link.

Rendering

This tag would not be rendered by a general-purpose map renderer.

Features and pages affected

Alternatives considered

All streets in destination:street

Exit Info proposes to use destination:street=* or destination:street:to=* for any street on a guide sign.[5] Valhalla uses this tag to distinguish between streets and place names in instructions, such as "Take exit 6B on the right onto MD 170 South/Camp Meade Road toward Linthicum" (emphasis added). [1]

This approach fails to distinguish destination road names from supplemental road names. As explained above, it is not always necessary to include a supplemental road name in a guidance instruction, especially on the instruction's second or third reading. destination:*:to=* should be reserved for cases where "To" is present on signage, because it should also be safe to omit these destinations when necessary.

Most importantly, pulling road names out of the list in destination=* assumes that road names always come before place names on signage.[6] Yet guide signs not infrequently list a place before a street, usually due to a subsequent fork. Currently, there are at least 583 cases in OpenStreetMap in which destination=* contains a road name after a place name.[7]

Incorrectly guessing the sign order will cause a router to list the destinations in reverse order, making it more likely that a motorist would miss an exit looking for the wrong name. The following examples illustrate Valhalla's behavior given tagging that adheres to Exit Info:

Migration

Even though quite a few non-supplemental road names are currently tagged as destination:street=*, existing routing software can transition smoothly to the new definition with little or no change.

OSRM

OSRM uses destination:street=* as a fallback when destination=* is missing. If destination=* is present, destination:street=* is omitted. Under this proposal, OSRM will produce more accurate instructions in cases where standard road name destinations are currently tagged as destination:street=*. The following examples illustrate what would happen to OSRM's output, assuming no software changes:

Valhalla

Valhalla currently produces instructions like "Take exit junction:ref=* on the right onto destination:ref=* (destination:street=*) toward destination:ref:to=*/destination:street:to=*/destination=*". As discussed above, this approach can produce suboptimal instructions. The following examples illustrate what would happen to Valhalla's output, assuming no software changes, as ways are retagged from the scheme described in Exit Info to the scheme proposed here:

Telenav / Scout

tbd

Notes

  1. To my knowledge, there is no official name for this phenomenon, but it is widespread enough to warrant a tag.
  2. Such as CheckAutopista.
  3. "Section 2E.10 Amount of Legend on Guide Signs", 2009 Manual of Uniform Traffic Control Devices.
  4. roadfro, "Re: city names on freeway signs", AARoads Forum.
  5. These tags were first added to Exit Info in 2015 but did not go through the tag approval process. At that time, there were no occurrences of either tag. The first occurrences appeared within a month in Pennsylvania and Maryland. It was added to Proposed features/Destination details in October 2017.
  6. A tagging list thread from January 2017 discusses the problems with this assumption.
  7. This is a very naïve search that can only detect when a road with a prefix like "Road" or "Avenue" occurs after a single-word destination, which is unlikely to be a street name. However, it fails to account for multi-word place names, which are also quite common. It is also unknown how many cases there are among ways that have been tagged with destination:street=* according to the proposal in Exit Info.
  8. Note that southbound I-71/I-75 does not lead to Second Street, and neither does Second Street lead to I-71/I-75.