Changes

From Wazeopedia

Wayfinder

137 bytes removed, 2 years ago
Criteria: added image and changed wording and organization at the top
=== Criteria ===
[[File:75split.png|thumb]]An instruction should be given where it is unclear how to continue on the highway on which one is driving. Usually this is a keep instruction, but sometimes, as explained [[#Continue instruction|below]], it should be a continue 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 right side, has at least two fewer ''travel lanes'' after the exit than before it;
*The continuation path on a controlled-access highway or freeway has the same number of lanes as, or fewer lanes than, the exit path after the fork;
**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.
  {{NeedImage| Need sample images for "lane drops" and "non-obvious continuations"; also, example of BGS with lane arrows}} [[File:FreewayS-inS-out.png|200px|right]]In these cases, we need to use a wayfinder configuration. Each wayfinder configuration will have one "IN" segment and two "OUT" segments.
==== Configuration ====
Multiple methods exist for forcing instructions on highway continuations, such as matching the road type of both outgoing segments even where it creates a discontinuity or falsely using an alternate name on the non-continuation side to match the continuation side. Since Waze editors have the ability to create turn instruction overrides, the preferred approach is to use correct road types and alternate names, stubs named to match signage and turn instruction overrides where necessary.
 [[File:FreewayS-inS-out.png|200px|right]]Each wayfinder configuration will have one ''in'' segment and at least two stub or continuous ''out'' segments.* 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°-15° off of the mid-line on opposite sides of each other, consistent with [[Junction_Style_Guide/Interchanges#Freeway_split_geometry|the geometry for freeway forks]]. This will allow for easy identification in WME, but still look seamless in the client app.
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway fork|freeway fork]], use a named freeway stub on both sides with an exit right TIO on the right side, unless "keep right" seems more appropriate for the numbered exit.
* If the numbered/signed exit is on the '''left''':
** For an [[Junction Style Guide/Interchanges#Exits|exit]], use a named highway stub of the same type as the ''in '' segment for the continuation, and an "exit left" TIO for the exit followed by a ramp.
** For a [[Junction Style Guide/Interchanges#Freeway.2Fhighway fork|freeway fork]], use named highway stubs on both sides, and use an "exit left" TIO on the left side, unless "keep left" seems more appropriate for the numbered exit.
1,270
edits