There are two methods to assign exit sign information into OpenStreetMap:
The collective node and way method - the exit sign information is stored on both nodes and ways
The node only method - all of the exit sign information is stored on a node
The preferred approach is the collective node and way method for the following technical reasons:
It can handle complex interchanges, as where a motorway_link and its associated reference number can split multiple times (such as 3A-B-C)
It handles turnoffs different from a country's standard without requiring tagging exceptions (e.g. a 'left' exit in right side driving countries), meaning it is easier for data consumers to be programmed for it
Associating the exit sign information with the *_link way clarifies route guidance
Data consumers Telenav and OsmAnd(+) both issue route guidance using node-and-way, and do not support node-only tags. A tool exists for OSRM installations to convert node-only tagging to node-and-way tagging.
node-and-way method
The exit sign information is stored on both nodes and ways as follows:
<motorist services> (Optional: populate when there are motorist services located at exit)
* junction:ref is recommended on all outbound junction points from a motorway, and should have the same value of ref=* on the node. While a node provides user-readable indicators of an exit's reference as indicated, junction:ref gracefully handles routing edge cases unambiguously, such as:
'left' exits in right-side-driving countries (and vice-versa)
Nodes where multiple exit references fork away from the same node
node-only method
All of the exit sign information is stored on the node where a link splits from the motorway as follows:
This method was popularized in the U.S. but is no longer recommended. This method is less structured than the node-and-way method and requires routers to rewrite exit_to as destination.
The location(typically a city) that the exit/ramp/slip road will head toward
<branch route number>
The route number that the exit/ramp/slip road will branch onto
<toward route number>
The route number that the exit/ramp/slip road will head toward
<branch road name>
The road name that the exit/ramp/slip road will branch onto
<toward road name>
The road name that the exit/ramp/slip road will head toward
<junction/exit number>
Populate when a exit/ramp/slip road splits at a common node and has different junction/exit numbers Example: 51A (the node <junction/exit number> will have 51A-B)
<safe exit speed>
Populate when a exit/ramp/slip road has an advisory speed sign
<motorist services>
Populate when the exit/ramp/slip road has access to services motorist need
This article or section may contain out-of-date information: Contradictory usage between two directions. If you know about the current state of affairs, please help keep everyone informed by updating this information. (Discussion)
Interstate 695 Outer Loop at Baltimore Washington Parkway exit sign
The above exit sign information shall be added to OpenStreetMap as follows:
Exit names are usually found on toll roads. On guide signs, exit names look similar to road names. The above exit sign information shall be added to OpenStreetMap as follows:
This exit has no visible number signage. Unnumbered exits are common on controlled-access U.S. routes and state highways in many parts of the U.S., as well as on Interstate freeways in California.
When adding interchange information to ways - please review the relationship of the interchange sign information and the connected ways. Sometimes a way will need to be split between an off ramp and an on ramp. Here is an example of when interchange information was added to a way that was both an off ramp and an on ramp: