Changes

From Wazeopedia

Junction Style Guide/Interchange

306 bytes added, 1 year ago
added anchors
Specific examples of how to handle common junction types are provided in the following sections. All of those examples use these road types. If you are unsure what road type you should use, refer to the [[road types]] article.
=== {{anchor|Exits}}Basic exit/entrance ===
A basic exit is a junction where a single ramp exits a highway and leads to another road, and the continuation of the highway is obvious to drivers. Most exits fit this description.
Similarly, a basic entrance is where a single ramp joins an existing highway, and the path of the highway is obvious to drivers. The geometry of a basic entrance junction should be mapped just like a basic exit, but with directions reversed.
==== {{anchor|Exit geometry}}Basic exit geometry ====
: [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]]
See [[#Ramp geometry and complexity|ramp geometry and complexity]] for information on setting the angles of basic exits.
==== {{anchor|Exit naming}}Basic exit naming ====
The highway/freeway segments before and after the junction should be named the same. The ramp segments should be named in accordance with the section on [[Road names#Exit|exit ramp names]]. In addition, if an exit carries a concurrent route away from the highway, for example a US route that was carried by an interstate up to the exit but splits off at the exit, that route designation should be added as an alternate name on all ramp segments that carry it.
A complex exit is a junction where one or more exit ramps leave the highway, and the continuation of the highway is not obvious to drivers. Therefore, another instruction is needed for traffic continuing on the highway. This can be a "keep" or "continue" instruction. When mapping complex exits, the geometry should match the instruction given, so for "continue" instructions the geometry should be set up as described for exits in [[#Ramp geometry and complexity|ramp geometry and complexity]], and for keep instructions (i.e. most wayfinder exits), the geometry should be set up in the same way as a [[#Freeway fork geometry|freeway fork]]. For criteria and further details on mapping complex exits, see [[wayfinder]] and [[turn instruction override]].
=== {{anchor|Freeway/highway splits|Freeway/highway forks}} Freeway/highway fork===
A highway/freeway fork is a junction where one freeway or highway splits into two, and there is no obvious straight through direction for a driver. This can happen at the end of a concurrency of highway routes or where one or both highway routes begin. This is synonymous with the MUTCD term "split."
For further details on freeway fork mapping, see the [[wayfinder]] page.
=== {{anchor|Ramp-ramp forks}}Ramp fork ===
A ramp may itself fork and branch into two directions. This is synonymous with the MUTCD term "bifurcation." Most of the time a ramp fork should be mapped to give instructions to traffic going either direction. This is accomplished by using the ramp type for both outgoing segments and names that are different from the incoming segment or turn instruction overrides where necessary.
== Configurations ==
=== {{anchor|Diamond Interchange}}Diamond ===
: [[Image:Jct_diamond.png]]
''See also: [[Wikipedia:Diamond_interchange|Diamond interchange article on Wikipedia]]''
The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.
=== {{anchor|Cloverleaf Interchange}}Cloverleaf ===
: [[Image:Jct_cloverleaf.png]]
'''Note on elevation: '''The single surface street segment between the inner most ramps should be either raised or lowered in relation to the freeway segments depending on the actual geography at the interchange.
=== {{anchor|Folded Diamond Interchange}}Folded diamond ===
: [[Image:Jct_folded_diamond.png]]
''See also: Discussion of Folded Diamonds and A2/B2 Partial Cloverleafs on the [[wikipedia:Partial_cloverleaf_interchange|Partial Cloverleaf Interchange article on Wikipedia]]''
==== {{anchor|Collector/distributor interchanges}}Collector/distributor interchange ====
Some interchange configurations make use of collector/distributor lanes to separate lower-speed merging traffic from high-speed through traffic. This is often used in cloverleaf interchanges and in groups of nearby exits.
The [[Detour Prevention Mechanisms|detour prevention mechanism]] will discourage Waze from routing users onto the collector-distributor and back onto the freeway – as long as the city name on the freeway is the same (or set to "no city") before, throughout, and after the collector-distributor. Previously this feature was not available and the ramps were set up to restrict the through route. Some of these ramp configurations may still be set up that way, so they can now be configured as pictured above with the through route enabled.
==== {{anchor|Complex collector/distributor interchanges}}Complex collector/distributor interchange ====
[[Image:Collector-distributor-exit.png|thumb|right|450px|Collector-distributor lanes used in an interchange on I-81 in Christiansburg, Virginia (Exits 118A-B-C)]]
{{clear}}
=== {{Anchor|
Diverging diamond interchange|Diverging_diamond_interchange|DDI}}Diverging diamond (DDI) ===
1,231
edits