Changes

From Wazeopedia

At-grade connectors

4,611 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/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? ==
There are only a few situations in which connectors are called for in an intersection:
*when When the turn lane physically separates from the main road well in advance of the intersection;*when When the ramp turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation*when When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a ramp connector lets you notify the driver a little earlier*As an When there are user complaints ([[Area ManagerUpdate_Requests_in_Waze_Map_Editor|Update Requests]], when you get a user complaint ) that the audible was too late, or that the map should have shown a ramp*in the new editor, if resolving map problems of the type 'The roads are too far apart from each other and most likely a road is missing in between'. This problem would be located at an intersection and the GPS tracks show that the turning lane is far enough from the intersection. in some cases the intersection can be reworked to resolve this problem.connector
When in doubt, leave it out. Each ramp 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 intersectionor 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.
*Ex: Street to Minor Highway should be Street type.
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.
 
In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector.
 
[[Image:Atgrade example3.jpg]]
 
 
AND, at the end of the connector, the left turn must be restricted:
 
[[Image:Atgrade example2.jpg]]
 
 
If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function:
 
[[Image:Atgrade example4.jpg]]
== 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 ===
 
[[File:DLT.png|250px|thumbnail|right]]The crossover left turn lanes and the resultant elongated right turn lanes in a [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 is reduced, and at-grade intersections with signed, numbered exits are interspersed with controlled access sections using grade-separated ramps.
 
In order to produce an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction 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 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 inappropriate to display such names on the map.
{{clear}}
 
{|style="margin: 0 auto;"
|- valign="top"
| [[File:GSP_10A.jpg|x162px]]
| [[File:GSP_10B.jpg|x162px]]
| Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south).
|}
 
=== Connector is a signed, numbered exit ===[[Category:Style Guides]][[Category:Waze Map Editor]]'''Example[[Category:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. Going south, the right turn lane is signed as Exit 10A and the left turn lane is signed as Exit 10B (and reversed going north).Update what links here]]
Administrators, translate-proofr, Widget editors
3,474
edits