|
|
| (4 intermediate revisions by the same user 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|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 Separate 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 Separate 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.
| |
| ==== Center two-way left-turn lanes ====
| |
| [[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]
| |
| Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.
| |
| ==== HOV or other restricted lanes ====
| |
| HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance.
| |
| <gallery>
| |
| File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes.
| |
| File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane.
| |
| File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right.
| |
| File:Lanes_Choices3.png|The HOV lanes is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.
| |
| </gallery>
| |
| | |
| === When to map lanes ===
| |
| Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes 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.<br clear=all>
| |
| ==== To clarify which road to take ====
| |
| Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.
| |
| {{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}
| |
| <gallery>File:Lanes_Choices.png|example 1
| |
| File:Lanes_Choices2.png|example 2</gallery>
| |
| ==== When the driver needs reinforcement or reassurance for safety ====
| |
| [[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]
| |
| There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right. Drivers have no choices. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.
| |
| | |
| === When not to map lanes ===
| |
| ==== When drivers have no choice ====
| |
| [[File:Nolanessimple.png|150px|thumb|right|suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all>
| |
| ==== Merges and new lanes ====
| |
| Waze does not offer lane guidance for a reduction in the number of lanes.
| |
| [[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all>
| |
| === How Waze selects 'Waze Selected' lane arrows ===
| |
| Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}
| |
| ''Expand for more information...''{{Collapsible section content}}
| |
| The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.
| |
| Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]
| |
| {{Collapsible section bottom}}
| |
| === When to override lane arrows ===
| |
| See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows
| |
| Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat - choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, u-turn, slight right, etc) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.
| |
| When you change the arrow associated with one outgoing segment, check the remaining segments. In general, do not use the same arrow for more than one outgoing segment
| |
| ==== When more than one outbound segment have the same 'Waze selected' arrow ====
| |
| Change one or more of them in a way that makes sense.
| |
| ==== Where segment geometry doesn’t match reality ====
| |
| [[File:Lanes Override2.png|150px|thumb]]This happens in some locations because waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all>
| |
| ==== Where the Waze selected arrow doesn't match reality ==== | |
| Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.
| |
| These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br>
| |
| However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br>
| |
| [[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all>
| |
| <big>In this example, continuing road veers left; while side road exits straight ahead. Both the street-level and overhead imagery clearly shows the driver's perspective, and the need for adjustments.</big>
| |
| {| class="wikitable" style="width: 100%;"
| |
| | style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''
| |
| | style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''
| |
| |-
| |
| | style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]
| |
| | style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]
| |
| |}
| |
| | |
| ==== Ramp splits, wayfinders, and forks in the road ====
| |
| Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br>
| |
| | |
| Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).
| |
| == Adding lanes to the map ==
| |
| Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#link to What counts as a lane]] for more.
| |
| {{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows at zoom level 4 and higher. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}
| |
| === Adding lanes to a segment === | |
| 1. Click the segment for which you would like to add lanes.
| |
| 2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]
| |
| 3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]
| |
| 4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]
| |
| 5. Add the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See [[#What counts as a lane?|the 'What counts as a lane section?' above]] for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]
| |
| 6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all>
| |
| 7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update.
| |
| {{mbox|text=Mousing-over the turn arrow in the lanes panel will<br>
| |
| highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}
| |
| === Editing existing lanes ===
| |
| Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br>
| |
| 1. Click the segment.<br>
| |
| 2. In the left pane, click the Lanes tab.<br>
| |
| 3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all>
| |
| | |
| === Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} ===
| |
| [[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab.
| |
| # Click the segment.
| |
| # In the left pane, click the Lanes tab.
| |
| # Click “Edit lane guidance”.
| |
| # Click the given turn angle icon under the TURNS header to open the Override turn angle menu.
| |
| # Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all>
| |
| === Junction Boxes ===
| |
| Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. All turn arrows inside a Junction Box must be green (unrestricted) in order for lane guidance to work. Use the Junction Box itself to restrict any necessary turns.
| |
| | |
| {{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}
| |
| === Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===
| |
| At intersections where one or both roads are divided, lanes cannot always be added directly.<br>
| |
| | |
| Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br>
| |
| {{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}
| |
| For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:
| |
| # Both left and right turns are possible at the intersection;
| |
| # The two portions of the divided roadway are essentially parallel to each other;
| |
| # The two intersecting roads are more or less perpendicular to each other;
| |
| # The median segment in question is 50 m or shorter; and
| |
| # The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).
| |
| If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.
| |
| {{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br>
| |
| [[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]
| |
| }}
| |
| {{mbox
| |
| | type = important
| |
| | text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn.
| |
| }}
| |
| ==== Mapping lanes on divided roadways ====
| |
| ===== Hash intersections =====
| |
| [[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]
| |
| First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br>
| |
| | |
| For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''
| |
| # On the entry segment, include the total number of lanes entering the segment.
| |
| ## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.
| |
| ## Right turn lanes should be mapped as normal.
| |
| # On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all>
| |
| {| class="wikitable" style="width: 100%;"
| |
| | style="width: 50%; text-align:center" | '''Entry segment: '''
| |
| | style="width: 50%; text-align:center" | '''Median segment: '''
| |
| |-
| |
| | style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]
| |
| | style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]
| |
| |}
| |
| The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br>
| |
| | |
| '''<big>Lanes resulting from heuristics:</big>'''
| |
| [[File:Lanes result.png|224px|frameless|left]]<br clear=all>
| |
| ===== H Intersections =====
| |
| The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.
| |
| {| class="wikitable" style="width: 100%;"
| |
| | style="width: 50%; text-align:center" | '''Undivided road side:'''
| |
| | style="width: 50%; text-align:center" | '''Divided road side:'''
| |
| |-
| |
| | style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]
| |
| | rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]
| |
| |-
| |
| | style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]
| |
| | style="width: 50%; text-align:center" |
| |
| |}
| |
| {{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br>
| |
| [[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]
| |
| }}
| |
| ===== Checking your work =====
| |
| There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.
| |
| # The total number of lanes on the entry segment should equal the total number of lanes at the intersection:
| |
| #* total lanes (intersection) = total lanes (entry)
| |
| # The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:
| |
| #* total lanes (median) = total lanes (entry) – right turn only lanes (entry)
| |
| # The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:
| |
| #* straight-ahead lanes (entry) = total lanes (median)
| |
| If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.
| |
