Changes

From Wazeopedia

At-grade connectors

2,842 bytes added, 4 years ago
Marked as global wiki page
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(Road types/USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation.
== Should the connector be mapped? ==
When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.
== {{anchor|How to label the connector type}} Road type ==
Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below.
The connector segment's type should be set based on the '''lowest''' of the types of roads it connects.
Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection.
== {{anchor|How to name the connector}} Road name ==
In most cases, leaving checking None for the segment unnamed Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the connector segment connects.
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector.
== {{anchor|Geometry of the connector}} Geometry ==
The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors.
== {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions ==
Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler.
== Exceptions ==
{{construction
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666
| contacttype = forum
| draft = yes
| open = no
| revision = yes
| section = yes
| talk = no
}}
 
=== Median U turn intersection (MUTI) ===
 
[[File:MUTI.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09057/ median U turn (aka "Michigan left") intersection] should be set to the {{Ramp}} type.{{clear}}
 
=== Restricted crossing U turn (RCUT) intersection ===
[[File:RCUT.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09059/ restricted crossing U turn (aka "J turn" or "Superstreet") intersection] should be set to the {{Ramp}} type.{{clear}} ===Displaced left turn (DLT) intersection == Connector is = [[File:DLT.png|250px|thumbnail|right]]The crossover left turn lanes and the resultant elongated right turn lanes in a signed[http://www.fhwa.dot.gov/publications/research/safety/09055/ displaced left turn (or "continuous flow") intersection] should be set to the {{Ramp}} type.{{clear}} === Jughandle === [[File:Jughandle.png|250px|thumbnail|right]][http://www.fhwa.dot.gov/publications/research/safety/07032/ Jughandle] segments should be set to the {{Ramp}} type.{{clear}} === Signed, numbered exit ===
[[File:GSP_10.jpg|right|border]]
'''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA.  The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce is reduced, and at-grade intersections with signed, numbered exits become a mix of are interspersed with controlled access sections using grade -separated ramps and at-grade intersections.  In order to receive produce an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for to Exit Right]] for the at-grade intersections, rather than Keep Right or Turn Right, we must use a junction angle of less than 45 degrees and a connector segment of a road type other than Freeway or Highway. Ramp type is ideal for this connector needs application because it does not display road names in the app. Segments for numbered exits are named to produce specific visual and TTS instructions, rather than by standard rules for at-grade connectors, and it would be a rampinappropriate to display such names on the map.
{{clear}}
Administrators, translate-proofr, Widget editors
3,474
edits