User:Nzahn1/Lanes View history

No edit summary
No edit summary
 
(49 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}
== Best practices and examples  ==
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual.
=== At-grade connectors and Lanes ===
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br>
First and foremost, the existing [[At-grade_connectors]](AGCs) guidance must be considered. The addition of Lanes data won't impact the necessity of using AGCs in most cases.  
 
==== Preserving AGCs while adding Lanes ====
There are some important considerations regarding lane guidance in Waze:
In instances where the AGCs are preserved, Lanes data should be added to the segment approaching the AGC and the next segment approaching the intersection. Additionally, lanes data
* '''Lane guidance does not affect routing''' - it is merely a visual feature.
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes on divided roadways (“H” and “#” intersections)|heuristics for intersections on divided roads]].
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].
{{mbox | type      = protection | text      = {{As of|2020|04|26}} The Lanes tab is only visible in the WME to [[Editing restrictions|rank 4 editors]] and lane guidance in the App is only visible to beta testers. The lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development.  Please check this guide frequently for updates to features and guidance.}}
{{mbox| type      = caution| text      = {{As of|2020|04|26}} The lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development.  Please check this guide frequently for updates to features and guidance.}}
== Mapping guidance ==
=== What counts as a lane? ===
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br>
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br>
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.
==== Freeway exits and other ramps ====
'''<big>Example 1: Not a Seperate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br>
<br>
'''<big>Example 2: Not a Seperate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br>
<br>
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br>
<br>
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.
=== When to map lanes ===
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes (one or more) is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.
==== When the driver needs to choose the correct lane ====
[[File:Lanes DriversChoice.png|thumb|right]]
Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.

Latest revision as of 00:37, 30 May 2020

Best practices and examples

At-grade connectors and Lanes

First and foremost, the existing At-grade_connectors(AGCs) guidance must be considered. The addition of Lanes data won't impact the necessity of using AGCs in most cases.

Preserving AGCs while adding Lanes

In instances where the AGCs are preserved, Lanes data should be added to the segment approaching the AGC and the next segment approaching the intersection. Additionally, lanes data