Changes

From Wazeopedia

Wayfinder

98 bytes added, 2 years ago
Configuration: continue geometry qualifiers
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 (usually) 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.
* The Unless a [[#Continue instruction|continue instruction]] is given 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.
=== Continue instruction ===
With the creation of turn instruction overrides, continue instructions can be given. Where a keep or exit instruction would be misleading, a continue instruction can be given, as explained [[Turn_instruction_override#Supplement_a_wayfinder|here]]. The [[turn instruction override]] page also has other use cases for the continue instruction on highways, most of which are not wayfinders (i.e. it is clear how to continue on the highway, but an instruction is nonetheless useful). Where a continue instruction is used to supplement a wayfinder, the geometry should match the instruction, so the deviation of the continuing highway should not deviatebe close to 0°.
== Segment naming ==
1,270
edits