Junction Box/en: verschil tussen versies Geschiedenis weergeven

Huidige versie van 25 apr 2023 om 15:30

Andere talen:

English
Nederlands

Junction Box

Junction boxes (JBs) are used to improve ETA calculations and routing through complicated intersections, and interchanges. Junction boxes are displayed as multiple segments with multiple inputs and outputs. They are basically a hint editors can give the Waze routing services that “although these few segments are cut in a few places, they generally should be treated as a single point which connects traffic from several sources”.

Considering a complex intersection as a single point has several beneficial properties:

Traffic speed data for each path through the junction box can be collected separately.
Turn restrictions can also be separately controlled for each path through the junction box.
Voice prompts can be separately controlled for each path through the junction box.
Turn instructions can be separately controlled for each path through the junction box.
The shape of a junction box cannot be changed afterwards
You cannot create new junction nodes in a junction box
You cannot move a junction node out of the junction box
If you're going to draw a junction box, make sure you can see all the segments you want in it, otherwise you'll end up with strange, incomplete paths.

For ETA purposes, the routing server does not consider segments wholly within the junction box, but rather treats the junction box as if all the segments which enter or exit the the junction box are connected to at a single junction node.

Junction boxes are considered only by the routing server. Junction boxes have no effect on navigational prompts. Junction boxes have no visibility in the client or on the live map. Junction boxes do not effect the search engine; the origin or destination of route may be contained in a junction box.

For editing a junction box L4 is needed. The segment with the highest lock within a JB determines the auto lock level of the JB.

Name Junction Box

If possible, state the reason for the junction box in the name.

Turn Instruction Overrides on JB's

Behaviour of TIOs on JBs:

If there's a TIO from entry to 1st short segment, it will be used, and a TIO on the virtual segment (entry > exit) will be ignored
if there's a TIO from any short segment to the next one, it will be used, and a TIO on the virtual segment will be ignored.
Otherwise, if there is a TIO on the virtual segment, it will be used as the only instruction between entry and exit.

Limitations

Maximum size junction box is about 5 Km.
A junction box must include at least two junction nodes which must be connected by a segment.
A junction node cannot be included in multiple junction boxes.
No more than 32 controllable entry/exit paths can pass through a single-junction node within a junction box.
- Adjacent connections not displayed in the routing box list are also counted.
- Having u-turns enabled on a two-way segment increases the number of paths.

More information

For an extensive explanation of the Junction Box see:

The USA wiki: Junction box page
The Australian wiki: Junction box page

Main Page | Index

@@ Regel 1: / Regel 1: @@
-Informal mentoring helps everyone involved and happens all the time.  It is not tracked or managed.  Keep doing what you do and have fun!  The following ideas and resources might be useful as you think about your need for training and mentoring or your desire to help others.
+{{TopLine}}
+[[Category:Editing aspects]]
+<languages />
+==Junction Box==
+[[File:Junction-box-map.png|right|260px]]Junction boxes (JBs) are used to improve [[Abbreviations|ETA]] calculations and routing through complicated intersections, and interchanges. Junction boxes are displayed as multiple segments with multiple inputs and outputs. They are basically a hint editors can give the Waze routing services that “although these few segments are cut in a few places, they generally should be treated as a single point which connects traffic from several sources”.<br />
+  [[File:Junction-box-attrib.png|right|260px]]
+<br />
+Considering a complex intersection as a single point has several beneficial properties:
+* [[Speed|Traffic speed]] data for each path through the junction box can be collected separately.
+* [[Turn restriction|Turn restrictions]] can also be separately controlled for each path through the junction box.
+* Voice prompts can be separately controlled for each path through the junction box.
+* [[Junction_Arrows#Turn_Instruction_Overrides|Turn instructions]] can be separately controlled for each path through the junction box.
+* The shape of a junction box cannot be changed afterwards
+* You cannot create new junction nodes in a junction box
+* You cannot move a junction node out of the junction box
+* If you're going to draw a junction box, make sure you can see all the segments you want in it, otherwise you'll end up with strange, incomplete paths.
+<br />
+For ETA purposes, the routing server does not consider segments wholly within the junction box, but rather treats the junction box as if all the segments which enter or exit the the junction box are connected to at a single junction node.<br />
+<br />
+Junction boxes are considered only by the routing server. Junction boxes have no effect on navigational prompts. Junction boxes have no visibility in the client or on the live map. Junction boxes do not effect the search engine; the origin or destination of route may be contained in a junction box.<br />
+<br />
+For editing a junction box '''L4''' is needed. The segment with the highest lock within a JB determines the auto lock level of the JB.
+{{Clear}}
+===Name Junction Box===
+[[File:Junctionbox-voorbeeld.png|left]]
+{{Clear}}
+If possible, state the reason for the junction box in the name.
-== Details ==
+===Turn Instruction Overrides on JB's===
+Behaviour of TIOs on JBs:
+# If there's a TIO from entry to 1st short segment, it will be used, and a TIO on the virtual segment (entry > exit) will be ignored
+# if there's a TIO from any short segment to the next one, it will be used, and a TIO on the virtual segment will be ignored.
+# Otherwise, if there is a TIO on the virtual segment, it will be used as the only instruction between entry and exit.
-* Editors asking and answering questions in the forums and live chat.
+===Limitations===
-* Can take place anytime, without any special process to set up the interaction.
+* Maximum size junction box is about 5 Km.
-* There is no approval process to be an informal mentor.
+* A junction box must include at least two junction nodes which must be connected by a segment.
-* Advice can range from exceptionally good to highly questionable depending upon the provider.
+* A junction node cannot be included in multiple junction boxes.
-* Task oriented: solve a current problem in editing and nothing more (e.g., how to fix a particular junction that is giving bad directions or bad map appearance).
+* No more than 32 controllable entry/exit paths can pass through a single-junction node within a junction box.
-* Generally lasts a few minutes or a few hours, with little to no recurring communication expected.
+** Adjacent connections not displayed in the routing box list are also counted.
-* Provides instant answers to questions, but cannot track the quality of the information provided.
+** Having u-turns enabled on a two-way segment increases the number of paths.
-* Not expected to significantly change the abilities of the Mentee and no expectation for change in rank during or after the mentorship.
+<BR>
+===See also===
+* The page on [[Junction Box over Roundabout|Junction Boxes over Roundabouts]]
+* The page on [[Far Lanes]]
+<br>
+===More information===
-== Informal mentoring ideas ==
+For an extensive explanation of the Junction Box see:
+* The USA wiki: [https://wazeopedia.waze.com/wiki/USA/Junction_box Junction box page]
-* Ask a question in a Waze Forum.
+* The Australian wiki: [https://wazeopedia.waze.com/wiki/Australia/Junction_boxes Junction box page]
-* Ask for help in [[WME Chat]].
-* Send a PM to a higher-level editor you have seen around Waze, or an Area Manager, State Manger, or Regional Coordinator for that region (check on your [[:Category:USA|state wiki]] for an Area Manager list).
+__NOTOC__
-* Utilize web conferencing/screen sharing to communicate with one or more editors while learning and editing on a project (there are many free tools for this, such as Google Hangouts).
+{{Bottomline}}
-* Establish a Google+ Communities area to help local or regional editors.  For example, see [http://plus.google.com/u/0/communities/100673692273347499558 Waze Arizona].
-* Organize a local Meet-up of editors in your region for a Waze conversation over lunch.
-<!-- Place all page content above this line. -->
-<!-- Add additional categories below this line. -->
-[[Category:Global]]
-[[Category:Mentoring]]

Zoeken