| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your countries local Wazeopedia.
When traffic moves between two roads that are at the same grade, these connecting segments are not technically ramps to Waze (unless it falls into one of the Exceptions listed below). How to handle these connectors depends on the exact situation.
Should the connector be mapped?
First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes.
There are only a few situations in which connectors are called for in an intersection:
- When the turn lane physically separates from the main road well in advance of the intersection
- When the 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 the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier
- When there are user complaints (Update Requests) that the audible was too late, or that the map should have shown a connector
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.
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 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.
- Ex: Minor Highway to Primary Street should be Primary Street type.
- Ex: Primary Street to Primary Street should be Primary 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.
In most cases, checking None for the 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.
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.
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.
AND, at the end of the connector, the left turn must be restricted:
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:
|This revision of a section is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. Content is being prepared by one or more users. Do not make any changes before you post a message in this forum.|
Median U turn intersection (MUTI)median U turn (aka "Michigan left") intersection should be set to the type.
Restricted crossing U turn (RCUT) intersectionrestricted crossing U turn (aka "J turn" or "Superstreet") intersection should be set to the type.
Displaced left turn (DLT) intersectiondisplaced left turn (or "continuous flow") intersection should be set to the type.
JughandleJughandle segments should be set to the type.
Signed, numbered exit
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 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.
|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).|