User:PesachZ/Wayfinders View history

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.

Wayfinders

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 for a controlled-access ramp, highway or freeway for an exit on the typical exit side, has at least two fewer travel lanes after the exit, than before it;
• The continuation path for an uncontrolled ramp or highway, or for an exit 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
• Some or all of the associated signage may be interpreted as suggesting a split -- for example;
  • lacking typical exit language, or
  • with arrows pointing left and right but no clear "straight-ahead" choice, or
  • is otherwise unclear or inconsistent so that drivers may be confused as to which way is the continuation or whether there is a continuation at all.

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;

1. before nearing the exit, is neither striped nor signed as a departing lane over a significant length (approximately ¾ a mile, or its full length), and
2. has not just started within a mile before the exit.

The original text of the wayfinder criteria to be replaced A wayfinder gives a user an instruction reminding them to stay on the road the user is already on, in situations where a reminder is warranted. A wayfinder is warranted in the following situations: Lane drops, where at least as many lanes leave the road as stay on the road; Non-obvious continuations, where at least one "exit only" lane exists on the side of the road where exits are not normally placed (in a right-hand traffic country, exiting traffic is to the left and continuing traffic is to the right); and Inconsistent signage, where a highway continues as a numbered route, but signs call it only by a name.

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 be the same type (either Freeway or Ramp, 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.

Previously in these situations segment naming was modified in one of the following ways in order of preference: Add a control/destination city, if it is known, to the OUT segment name. Remove the compass cardinal from the OUT segment name. Add a space to the end of the OUT segment name (note that this will be flagged by the WME Validator script, if active, and possibly result in undoing by another editor) Create a stub in the IN segment just before the junction with no street name. NOTE: This option should only be used as a last resort because it prevents the routing server from properly calculating turn delays, and may result in inefficient routing through the area. If you see any of these set-ups, please correct it to one of the two the proper methods listed above.

• Do not use "to" at the beginning of the name of the 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).
• Each "stub" segment should be Segment length/Minimum 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 midline 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  Ramp  type. This will give an "exit right" instruction for the exit and a "stay to the left" instruction for the continuation.
  • For a basic exit, use a named Ramp stub for the continuation, and a standard Ramp for the exit.
  • For a freeway split, use a Ramp stub on both sides.
• If the numbered/signed exit is on the left, the OUT segments should be  Freeway  type. This will give "stay to the" instructions on both sides (if Ramp segments were used, Waze would give a confusing "exit right" instruction for the continuation).
  • For a basic exit, use a named Freeway stub for the continuation, and an unnamed Freeway stub followed by a named Ramp for the exit.
  • For a freeway split, use named Freeway stubs on both sides.

Exit direction	Type	Left OUT configuration	Right OUT configuration	Example
Right	Basic exit	Continuation side  Named Ramp stub  →  Named Fwy	Exit side  Named Ramp
Right	Fwy split	Continuation side  Named Ramp stub  →  Named Fwy	Exit side  Named Ramp stub  →  Named Fwy
Left	Basic exit	Exit side  Unnamed Fwy stub  →  Named Ramp	Continuation side  Named Fwy stub  →  Named Fwy
Left	Fwy split	Exit side  Named Fwy stub  →  Named Fwy	Continuation side  Named Fwy stub  →  Named Fwy