Lane Guidance: Difference between revisions View history

Road attributes Routing
VisualWikitext
No edit summary
(Marked this version for translation)
 
(35 intermediate revisions by 4 users not shown)
Line 2: Line 2:
<languages /><translate>
<languages /><translate>


'''IMPORTANT''' - ''Please make sure not to share any information about lanes outside the community. As any other feature in beta this is '''confidential'''.
== What is the Lane Guidance Feature? == <!--T:1-->


<!--T:7-->
<!--T:7-->
Line 21: Line 19:


<!--T:10-->
<!--T:10-->
- For primary streets and minor Highway it will happen ~500m before the junction. For highways and Major Highway ~1km.
- For primary streets and minor Highway it will happen ~500m before the junction. For Freeways and Major Highway ~1,5km.


== Important to know == <!--T:11-->
== Important to know == <!--T:11-->
Line 28: Line 26:


<!--T:13-->
<!--T:13-->
* TTS is currently not yet supported.
* More complicated types of junctions. We currently only support +, H and # junctions.
* The Visual indication for “continue straight” in case there is no turn involved.
* More complicated types of junctions. We currently support +, H and # junctions.


=== What is currently out of scope? === <!--T:14-->
=== What is currently out of scope? === <!--T:14-->
Line 36: Line 32:
<!--T:15-->
<!--T:15-->
* Lanes on Roundabouts.
* Lanes on Roundabouts.
* Merging lanes
* Lanes on AA , the whole platform is undergoing a restructure and redesign in order to make it easier to add features.
* Lanes on AA , the whole platform is undergoing a restructure and redesign in order to make it easier to add features.
* Lane guidance on "snake route" through JB.
* Bus lanes (and other not allowed lanes)


=== Known issues === <!--T:16-->
=== Known issues === <!--T:16-->


<!--T:17-->
<!--T:17-->
* Lanes are available on Carplay but are not centered, slightly aligned to the left.(We won't collect any CarPlay feedback until iOS 13.5 officially comes out.)
* Lanes are available on Carplay but are not centered, slightly aligned to the left.
* Editors with a lower level won’t be able to see the lanes tab and lanes data in WME for now.
* Editing segments with lane guidance, i.e: splitting them, will cause lanes data removal so make sure to add map comments where necessary.
* Editing segments with lane guidance, i.e: splitting them, will cause lanes data removal so make sure to add map comments where necessary.
<br />
<br />
Line 51: Line 49:
We created this '''[https://docs.google.com/document/d/1cXlvoKXLp9bnIp33Ito3KjmLaMqL7cWq5VDL8JBgXkg/edit#heading=h.82emqwgz41eb Lanes Knowledge Base]''' in order to help you start smoothly and have a snapshot of all the knowledge created during the alpha and beta stage. We’ll make sure to update it periodically with new content if needed.
We created this '''[https://docs.google.com/document/d/1cXlvoKXLp9bnIp33Ito3KjmLaMqL7cWq5VDL8JBgXkg/edit#heading=h.82emqwgz41eb Lanes Knowledge Base]''' in order to help you start smoothly and have a snapshot of all the knowledge created during the alpha and beta stage. We’ll make sure to update it periodically with new content if needed.
<br />
<br />
==Exits and weaving sections== <!--T:3-->
<!--T:4-->
This examples can be used for Freeway MH and mH for non at-grade connections.
These are draft proposals
{| class="wikitable"
|Exit||[[File:Straight.png]] [[File:Straight Slightly Right.png]]||[[File:Exit with taper 0.jpg]]
|-
|Weaving section or parallel Exit > 150m||[[File:Straight.png]]  [[File:Straight.png]] [[File:Slightly Right.png]]||[[File:Exit 150me.jpg]] [[File:Weaving Section.jpg]] [[File:Weaving section2.jpg]]
|-
|Exit with taper||[[File:Straight.png]] [[File:Straight Slightly Right.png]] [[File:Slightly Right.png]]||[[File:Exit with taper 1.jpg]] [[File:Exit with taper 2.jpg]]
|-
|Split||[[File:Straight.png]]  [[File:Straight.png]] [[File:Slightly Right.png]] [[File:Slightly Right.png]]||[[File:Split.jpg]]
|}


== At-grade crossings == <!--T:5-->
== At-grade crossings == <!--T:5-->
Line 85: Line 68:
<!--T:26-->
<!--T:26-->
[[File:Heuristics.jpg|right|500px]]
[[File:Heuristics.jpg|right|500px]]
At the moment 5/2020 this works only for RBS(routing beta server)


<!--T:30-->
On those crossing the Lane Guidance instructions will be combined. (Heuristics)
On those crossing the Lane Guidance instructions will be combined. (Heuristics)


Line 94: Line 77:
* Straight segments must be in a straight line (option for a 20° offset)
* Straight segments must be in a straight line (option for a 20° offset)
* Left turn must be between 70° a 110°) You can Use "Micro Doglegs"
* Left turn must be between 70° a 110°) You can Use "Micro Doglegs"
* The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (i.e., no new lanes are added or subtracted in the median).
* All intermediate segments, having more than 1 allowed direction, must be configured with LG and number of lanes must not change withing that segment.


<!--T:28-->
<!--T:28-->
Line 100: Line 85:
<!--T:29-->
<!--T:29-->
{{clear}}
{{clear}}
== Junction Box == <!--T:31-->
<!--T:32-->
Lane Guidance 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.
<!--T:42-->
LG offers more options when applied to a segment entering a JB.  This is documented in the page about the JB.


== Bus Lanes == <!--T:20-->
== Bus Lanes == <!--T:20-->
Line 105: Line 98:
<!--T:21-->
<!--T:21-->
Normally bus lanes are not mapped. Except when you may use this lane on the next crossing to go Left or right. So they can only be marked with: [[File:Left.png]]  [[File:Right.png]]
Normally bus lanes are not mapped. Except when you may use this lane on the next crossing to go Left or right. So they can only be marked with: [[File:Left.png]]  [[File:Right.png]]
<br />


== What’s next? == <!--T:22-->
== Guidelines on when LG can be used == <!--T:35-->
 
<!--T:43-->
With some exceptions, LG are used only on Freeway, Major Highway, Minor Highway.
 
<!--T:44-->
In following cases, there is usually a possible confusion about which lane(s) to use, hence configure LG, unless the local situation is exceptional.
 
<!--T:45-->
* On regular junctions where there are at least 2 lanes for 1 of the given directions.
* On regular junctions where incoming lanes have a mandatory direction other than straight ahead.
* On complex junctions. Example there are 2 segments on the right (first with an angle of <90° and the other one  with an angle of > 90°[[File:Lanes052.png|thumb]]
 
== Guidelines on when '''NOT''' to use LG == <!--T:36-->
 
<!--T:46-->
In following cases, there is generally no possible confusion about which lane(s) to use, hence do not configure LG, unless the local situation is exceptional.  Our aim is indeed, to generate instructions only when they are necessary.
 
<!--T:47-->
* On highways, for a simple 1 lane exit where the number of lanes before and after the exit remains the same.
* On regular junctions where the pre-sorting lanes are rather short
* On regular junctions with only 1 lane for each direction, unless some incoming lane cannot be used to continue straight ahead.
 
<!--T:37-->
== Guidelines on when to use CS (Continue Straight) ==
Continue Straight lane's are not shown by default. This can be overruled. [[File:LG-CS.jpg|200px|thumb|right]]
 
<!--T:38-->
=== view only ===
* If there can be confusion with another LG within the threshold distance (Freeway and Major Highway 1,5km, minor Highway 500m) before.
 
<!--T:39-->
=== view and hear ===
* When some of the lanes before the junction are not anymore available after the junction
{{clear}}
 
<!--T:40-->
==Tools==
* <b>Lane Tools</b>
: [https://github.com/SkiDooGuy/WME-LaneTools/blob/master/WME-LaneTools.user.js Go to script ] And click on RAW


<!--T:23-->
* The team is currently working on TTS (Text To Speech) for Lanes and the indication on ‘Continue Straight”.
* We are going to rollout lanes to the wider beta community in the client in the next few days. This will allow us to get feedback while you are mapping and increase the lane coverage.
* We will be in touch with the coordinator to plan a per country gradual rollout to production
<br />


<!--T:41-->
[[Category:Road attributes{{#translation:}}]] [[Category:Routing{{#translation:}}]]
</translate>  
</translate>  
{{Bottomline}}
{{Bottomline}}

Latest revision as of 17:14, 20 February 2024

We are currently updating the pages to include all regionally different guidelines. If you find inconsistencies, please refer to the English page. Thank you!
Other languages:

The ability to provide driving instruction based on lanes, a clearer and smoother driving experience for drivers.
While mapping, pay attention to the different types of junctions.


If you cannot add lanes, instead of hacking the map or creating a workaround please add the feedback to the spreadsheet, choose the right type of feedback, and explain the reason why.

How does it look in the app?

- The next turn indication will transition to a lane guidance for streets where the lanes have been added from the Waze Map Editors community.

- For primary streets and minor Highway it will happen ~500m before the junction. For Freeways and Major Highway ~1,5km.

Important to know

What is currently not supported, but we are working on?

  • More complicated types of junctions. We currently only support +, H and # junctions.

What is currently out of scope?

  • Lanes on Roundabouts.
  • Merging lanes
  • Lanes on AA , the whole platform is undergoing a restructure and redesign in order to make it easier to add features.
  • Lane guidance on "snake route" through JB.
  • Bus lanes (and other not allowed lanes)

Known issues

  • Lanes are available on Carplay but are not centered, slightly aligned to the left.
  • Editing segments with lane guidance, i.e: splitting them, will cause lanes data removal so make sure to add map comments where necessary.


Where can we find more information about Lanes?

We created this Lanes Knowledge Base in order to help you start smoothly and have a snapshot of all the knowledge created during the alpha and beta stage. We’ll make sure to update it periodically with new content if needed.

At-grade crossings

At intersections with a stop line, take all existing lanes. In the example at the right this will give the following:


Avoid to use at-grade connectors. See also the Global wiki

H and # crossings

On those crossing the Lane Guidance instructions will be combined. (Heuristics)

There are some conditions that must be taken into account.

  • The intermediate segment must be less than 50m.
  • Straight segments must be in a straight line (option for a 20° offset)
  • Left turn must be between 70° a 110°) You can Use "Micro Doglegs"
  • The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (i.e., no new lanes are added or subtracted in the median).
  • All intermediate segments, having more than 1 allowed direction, must be configured with LG and number of lanes must not change withing that segment.

Junction Box

Lane Guidance 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.

LG offers more options when applied to a segment entering a JB. This is documented in the page about the JB.

Bus Lanes

Normally bus lanes are not mapped. Except when you may use this lane on the next crossing to go Left or right. So they can only be marked with:

Guidelines on when LG can be used

With some exceptions, LG are used only on Freeway, Major Highway, Minor Highway.

In following cases, there is usually a possible confusion about which lane(s) to use, hence configure LG, unless the local situation is exceptional.

  • On regular junctions where there are at least 2 lanes for 1 of the given directions.
  • On regular junctions where incoming lanes have a mandatory direction other than straight ahead.
  • On complex junctions. Example there are 2 segments on the right (first with an angle of <90° and the other one with an angle of > 90°

Guidelines on when NOT to use LG

In following cases, there is generally no possible confusion about which lane(s) to use, hence do not configure LG, unless the local situation is exceptional. Our aim is indeed, to generate instructions only when they are necessary.

  • On highways, for a simple 1 lane exit where the number of lanes before and after the exit remains the same.
  • On regular junctions where the pre-sorting lanes are rather short
  • On regular junctions with only 1 lane for each direction, unless some incoming lane cannot be used to continue straight ahead.

Guidelines on when to use CS (Continue Straight)

Continue Straight lane's are not shown by default. This can be overruled.

view only

  • If there can be confusion with another LG within the threshold distance (Freeway and Major Highway 1,5km, minor Highway 500m) before.

view and hear

  • When some of the lanes before the junction are not anymore available after the junction

Tools

  • Lane Tools
Go to script And click on RAW



  Main Page | Index

Retrieved from "https://www.waze.com/wiki/Belgium/index.php?title=Lane_Guidance&oldid=25892"