|This revision of a section is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. This content is open to changes from anyone during construction. If you would like to make changes or have questions, please send a private message to this user.|
A wayfinder gives a user an instruction directing them how to continue on the road the user is already on, in situations where it may be unclear, and there would otherwise be no instruction.
A wayfinder is warranted in the following cases:
- The continuation path on a controlled-access highway or freeway, when an exit is present on the typical side, has at least two fewer travel lanes after the exit than before it;
- The continuation path on an uncontrolled highway, or when an exit is present on the atypical side, has at least one fewer travel lanes after the exit than before it;
- The continuation path consists of a single lane; or
- Other conditions exist that may suggest a split rather than an exit (use your better judgement, and discretion) -- for example:
- The physical roadway itself forks or diverges with no clear straight-ahead direction;
- Signage and striping do not clearly provide all expected "exit" indications, or do so inconsistently; or
- Signs are present with arrows pointing left and right but no sign clearly establishes the continuation.
A travel lane is a lane which is long enough that a naïve driver might consider it a long-distance lane. For our purposes we will clarify this as any lane which;
- before nearing the exit, is neither striped nor signed as a departing lane over a significant length (approximately ¾ a mile, or its full length, whichever is shorter), and
- has not just started within a mile before the exit.
| The original text of the wayfinder criteria to be replaced
|Need sample images for "lane drops" and "non-obvious continuations"; also, example of BGS with lane arrows|
In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.
Keep these basic principles in mind:
- The OUT segments must both be the same type (either , , , or , as explained below).
- Each OUT segment must have a name different than the IN segment.
- OUT segments should be named with the information displayed on the roadway signs.
- However, if this would leave an OUT segment with the same name as the IN segment, the OUT segment should be left with no-name.
- If there is no roadway signage, and the OUT segment is a continuation of the same road; it should be left with no-name.
- If there is no roadway signage, and the OUT segment is an exit; it should be named following the guidelines for an unsigned exit.
- If there is no roadway signage, and the OUT segment is a short continuation of the same road leading to an exit or road termination; it should be named following the guidelines below beginning with "to ".
| Previously in these situations segment naming was modified in one of the following ways in order of preference:
- Do not use "to" at the beginning of the name of the OUT segment if it is for a continuation of the same road, e.g. a freeway split where one side is the continuation of the same freeway (the user is already on the road, not going "to" it).
- The exceptions to this rule would be:
- If the control city on the BGS ONLY applies to the second road (I-280 in our example), then the control city should be placed after that highway, e.g. "I-80 / to I-280 / Morristown".)
- (e.g. The left OUT of this wayfinder should be named "to I-71 N / Columbus" because after you pass it you are still on I-471 for a while.)
- unsigned exit guidelines. However it may be appropriate (if there are no House Numbers, or other on ramps past this wayfinder before it reaches the exit, to leave this entire portion with no-name, and the instruction will inherit the name of the next road you are going to.
- Each "stub" segment should be 19.69 ft (6 m) long. This is long enough so it will not cause routing problems, but it is short enough to suppress display of the names (on Freeway stubs) and keep freeways looking contiguous (on Ramp stubs).
- The OUT segments should have a turn angle of 10°-20° off of the mid-line on opposite sides of each other, consistent with the geometry for freeway splits. This will allow for easy identification in WME, but still look seamless in the client app.
To configure the wayfinder,
- If the numbered/signed exit is on the right, the OUT segments should be type. This will give an "exit right" instruction for the exit and a "stay to the left" instruction for the continuation.
- If the numbered/signed exit is on the left, the OUT segments type should be the same as , in the following examples we will use the type. This will give "stay to the" instructions on both sides (if segments were used, Waze would give a confusing "exit right" instruction for the continuation).