|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| {{mbox
| |
| | type = critical
| |
| | text = Currently, junction boxes require rank {{rank|jb}} or higher to create or edit them.}}<br />
| |
|
| |
|
| [[File:Junction Box 7a.png|right]]A '''junction box''' ('''JB''') is a tool used to group separate junction nodes and the segments between them into a single big junction for improved data collection, routing control and navigation instructions. In simple terms, junction boxes tell the routing server, “Although the segments coming into here are connected in a few separate places, they should be treated as if they all connected together at one place." Because of this, junction boxes provide an extra layer of information on top or instead of the information associated with individual nodes, segments and turns.
| |
|
| |
| ==Overview==
| |
| The junction box enables a complex intersection, or interchange composed and displayed as multiple [[Glossary#Segment|segments]] to be treated by the routing server as a single [[Glossary#Junction|junction node]] with multiple inputs and outputs. Considering a complex intersection as a single point has several beneficial properties:
| |
|
| |
| *[[Routing_server#Turn delays|Traffic speed data]] for each path through the junction box can be collected separately.
| |
| *[[Glossary#Turn_Restriction|Turn restrictions]] can be separately controlled for each path through the junction box.
| |
| *[[Voice prompt|Voice prompts]] can be separately controlled for each path through the junction box.
| |
| *[[Turn instruction|Turn instructions]] can be separately controlled for each path through the junction box.
| |
| *Additional beneficial features of a junction box will be listed here as they become available.
| |
|
| |
| For [[Glossary#Estimated_Time_of_Arrival|ETA]] purposes, the [[Routing_server|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 a single junction node.
| |
|
| |
| Junction boxes are considered only by the routing server. Junction boxes have no visibility in the client or on the live map. Junction boxes do not affect the search engine; the origin or destination of a route may be contained in a junction box.
| |
|
| |
| NOTE: Junction boxes are only considered by the routing server when the route fully traverses through the junction box. Routes that start or end inside a Junction Box will use the underlying segments for routing and instructions. This means that junction box speed data, route restrictions, and instructions that have been overridden by the junction box will not be used by the app in these cases. Examples where this could occur are: when a route's destination is inside the bounds of a junction box; when a route's origin is inside the bounds of a junction box; when a route is recalculated inside the bounds of junction box, such as after a missed turn.
| |
|
| |
| ===Improving data collection===
| |
| <!-- The original page, specifically this entire section was reviewed 2015-11-10 by staff Ohad and confirmed as accurate. Staff quote "it looks really great, comprehensive and correct". -->
| |
| [[File:Junction Box 3.png|right|75px]]
| |
| Waze routing servers use junction box traffic data instead of the underlying segment and node traffic data, though Waze continues to collect both sets of data.
| |
|
| |
| A complex intersection can skew turn delay transition speed data. At first glance the following example seems like a pretty simple intersection, but if it usually experiences heavy traffic this intersection could be collecting bad data.
| |
|
| |
| [[File:Junction Box 4.png|right]]
| |
| Assume that all the roads are two-way and all turns are enabled. Consider the drivers going from A to E, and from A to F, when there is a traffic jam for the left turn (at point D), but traffic going straight through D is flowing fine.
| |
|
| |
| Without a junction box, the traffic from point A to point C is considered to be the same for both the red and the blue cars. The same statistical data is gathered and the average speed skews the ETA for everyone. The turn delay data is only different for the red and blue cars on the one segment before the turn at D, from C to D.
| |
|
| |
| [[File:Junction Box 5.png|right]]
| |
| Adding a junction box solves this problem. With a junction box, historical and real time data are collected separately for each one of the possible routes through the intersection - all 12 of them.
| |
| {{columns|
| |
| * A ➡ B
| |
| * A ➡ E
| |
| * A ➡ F
| |
| * B ➡ A
| |
| * B ➡ E
| |
| * B ➡ F
| |
| * E ➡ A
| |
| * E ➡ B
| |
| * E ➡ F
| |
| * F ➡ A
| |
| * F ➡ B
| |
| * F ➡ E
| |
| |4}}
| |
|
| |
| With a junction box the paths of A to F, and A to E are being measured separately, the traffic jam for the red cars turning at D does not have a negative effect on the blue cars going straight through D. Their ETAs are being recorded separately.
| |
|
| |
| {{Anchor|Fixing update request example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Fixing update request example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| Thus, [[Glossary#Update_Request|URs]] resulting from the inability to distinguish left turn delays from straight through traffic can be dealt with using the junction box. Draw a junction box over the intersection where the straight traffic is being improperly detoured, in order to provide better data collection and hopefully better routing. U-turns that are legal should not be restricted.
| |
|
| |
| [[File:JBRoutingExample1.png|400px]]</br>
| |
| <small>[[#Fixing update request example|Link to fixing update request example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| {{Anchor|Understanding inside a junction box example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Understanding inside a junction box example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| {{mbox|text=''There are many types of scenarios where a junction box may be indicated, this sample is used just to explain the function of a junction box, and not meant as guidance on where to use them.''}}
| |
| [[File:Junction Box 3a.png|right|250px]]
| |
| To illustrate the improving data collection concept, let's take a look at this intersection. There are five segments entering/exiting the junction box (segments which are only partially inside the junction box). There is one segment which is wholly inside the junction box. If there were no junction box at this intersection the individual [[Routing server#Turn delays|turn delay]] ''AKA the time it takes to turn from one segment to the next'' data for the outer five segments would be merged together at the inner four segments, and be distorted. The junction box here alleviates the problems with collecting accurate turn delay transition timing caused by the short segments in the middle.</br>
| |
| <small>[[#Understanding inside a junction box example|Link to understanding inside a junction box example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| {{Anchor|Timing example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Timing example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| If a junction box is drawn around these intersections (below left), then when considering a route that would traverse a segment within the box, the routing server treats the intersection like one large junction node for the purpose of calculation transition timing ''AKA turn delays'' (below right).
| |
|
| |
| A route path from point A to point B (westbound Mill Grove Rd to southbound Idlewild Rd to westbound Indian Trail Fairview Rd) is treated as a single transition, even though in actuality it traverses four segments (3 transitions). The green path is the actual junction box route in WME.
| |
|
| |
| <center>[[File:Timing_Junction_Box_4e.PNG|300px]] [[File:Junction Box B.png|300px]]</center></br>
| |
| <small>[[#Timing example|Link to timing example]]</small>
| |
| {{Collapsible section bottom}}
| |
| {{clear}}
| |
|
| |
| ===Turn arrow tooltip on a junction box exit arrow===
| |
| [[File:Wme_turn_override_hover5.png|250px|right]] The turn arrow tooltip has five elements: Voice prompt, Instructions, Restrictions, Switch Route (when applicable), and Difficult turn. Junction boxes have no effect on these elements, unless these elements are changed in the turn arrow tooltip.
| |
|
| |
| {{Anchor|Turn instructions example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Turn instructions example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| Looking back at our timing example path, going from point A to point B (westbound Mill Grove Rd to southbound Idlewild Rd to westbound Indian Trail Fairview Rd), let's analyze how the junction box works with voice prompts. Our path is considered for routing as one transition, and judging by the angles it would be a straight transition making it a [[best continuation]] with no voice prompt. But as we just said 'junction boxes have no effect on voice prompts', therefore the actual voice prompt given for this path (point A to point B) will consider the three junction nodes and produce:
| |
|
| |
| *[[File:Big_direction_left.png|25px]] Turn Left onto Idlewild Rd, and then
| |
| *[[File:Big_direction_right.png|25px]] Turn right onto Indian Trail Fairview Rd".
| |
|
| |
| This is to say that the voice prompts are still controlled by the actual names, types, and angles of the segments within a junction box.
| |
| {{Details|How Waze determines turn / keep / exit maneuvers|Waze selected voice prompts}}</br>
| |
| <small>[[#Turn instructions example|Link to turn instructions example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| ====Voice prompt====
| |
| *If a voice prompt is added in the junction box's exit arrow tooltip, then all internal Waze selected voice prompts are removed and the voice prompt is announced at the first junction node using the first named road segment on that route from the first junction node.
| |
| *If a voice prompt is added in the junction box's exit arrow tooltip, the voice prompt will be given at the first junction node. Unless there is an editor selected voice prompt (other than Waze selected) on a node along the path, then the editor selected voice prompt on the node will override the junction box' exit arrow voice prompt (junction box's exit arrow voice prompt will not be given).
| |
| *If a voice prompt is added in the junction box's exit arrow tooltip, and lane guidance has also been added to the segment entering the junction box at the first node inside the box, the lane guidance will be displayed with the voice prompt. This can be undesirable, and it is recommended to check the lane guidance when adding a voice prompt to junction box paths.
| |
|
| |
| {{Anchor|Voice prompt example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Voice prompt example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| In the example below, adding a voice prompt to the junction box’s exit turn arrow tooltip can cause problems with the correct location of the voice prompt and the announced road name.
| |
| <center>[[File:OR JB TIO1.png|300px]] [[File:OR JB TIO3.png|300px]]</center>
| |
|
| |
| Eastbound {{Major Highway|State Hwy 22E}} has a left exit to {{Ramp|OR-99E BUS / Keizer / Portland}}. There is an "exit left" voice prompt[[File:OR_JB_TIO3.PNG|250px|right]] on the junction box's route which exits for that ramp. The junction box's voice prompt overrides all the internal Waze selected voice prompts and the voice prompt is "Exit left to State Hwy 22E" at junction node A in the picture above, which gives the user very bad instructions. The voice prompt is given too early (just before crossing the water) and the wrong road name is announced. This is because the junction box's voice prompt is announced at the route's '''first''' junction node within the junction box and utilizes the '''first''' named road segment after that junction node. If you take off the primary name of the{{Major Highway|State Hwy 22E}}'s two segments between that first junction node and the ramp, then the first named road segment becomes the ramp segment. This does have the desired road name announced, but the announcement will still be just prior to crossing the water.
| |
|
| |
| *Moral of this example is, don't put the exit left voice prompt on the junction box exit arrow. Instead, just have it on the major highway's turn arrow tooltip and it should announce the correct ramp name at the correct location.</br>
| |
| <small>[[#Voice prompt example|Link to voice prompt example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| ====Instructions====
| |
| [[File:JB Turn instructions panel.png|250px|right]]
| |
| Similar to the Instructions on turn arrow tooltip, Instructions is an option on a junction box exit arrow tooltip. The Turn instructions panel has the same options but there are special considerations when the options are used on the junction box exit arrow.
| |
|
| |
| =====Visual instructions=====
| |
| Visual instructions can be added to a junction box's exit arrow.
| |
| *Just like voice prompts, visual instructions will be given at the first node that the path encounters through the box.
| |
| *Unlike JB voice prompts, JB visual instructions will work together with subsequent node-based visual instructions inside the junction box. In these cases the junction box's visual instruction will be shown at the first node, and then the node-based visual instruction(s) will be shown at the subsequent node(s) through the junction box.
| |
| *When adding visual instructions to a junction box's exit arrow do not add visual instructions directly to the first node of that route, to avoid a conflict between the junction box's visual instruction and the node-based visual instruction on that first node.
| |
| *Both node-based and junction-box-based visual instructions require an associated navigation instruction in order to be visible in the app, either resulting from default behavior, a voice prompt or a View and hear lanes override. If the driver is not told to turn, exit, continue, etc. at a node, no visual information can be displayed there.
| |
|
| |
| Adding visual instructions to a junction box route is useful for situations where multiple signs are displayed for a single turn, with each sign pertaining to the next turn. For example, in complex interchanges it's common to have multiple lanes exit the highway together at one place and then split apart a short distance after exiting, with the different lanes marked by different signs. Using a JB visual instruction allows the driver to see only the visual instructions that pertain to their route.
| |
|
| |
| {{Anchor|Visual instructions example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Visual instructions example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| [[File:WME JB Visual BGS.jpg|300px|thumb|right|At the first node there are signs for I-75 N » Dayton, Exit 1D: US-50 W • River Rd, and Exit 1C: Fifth St]]
| |
| The example route is traveling northbound on I-75 to Exit 1D: US-50 W • River Rd where I-75 N and I-71 N fork. At the first node on our route there are signs for {{nowrapcode|I-75 N » Dayton}}, {{nowrapcode|Exit 1D: US-50 W • River Rd}}, and {{nowrapcode|Exit 1C: Fifth St}}. Trying to display all of this visual information information at the first node would be difficult to accomplish in one visual instruction; it would give the driver a lot of information they don’t need; it would also make the verbal instructions unnecessarily long to the point where it could truncate future instructions.
| |
| Adding visual instructions to the junction box path we can give the driver instructions only what they need to see and hear for their route to Exit 1D: US-50 W • River Rd.
| |
| {{Clear}}
| |
| Adding only these instructions will give clear directions for this route
| |
| {|style="margin: 0 auto;"
| |
| | [[File:WME JB Visual1.jpg|250px|thumb|First, add this on the junction box exit arrow tooltip for the Exit 1D: US-50 W • River Rd route]]
| |
| | [[File:WME JB Visual2.jpg|250px|thumb|Then, at the I-75 N / Exit 1C: Fifth St fork add the view only lane guidance on the highlighted segment]]
| |
| | [[File:WME JB Visual3.jpg|250px|thumb|Finally, at the fork for I- 75 N add the visual instruction for Exit 1D: US-50 W • River Rd on the turn arrow tooltip]]
| |
| |}
| |
| This will result in the following instructions in the app
| |
| {|style="margin: 0 auto;"
| |
| | [[File:JB Visual App1.png|250px|thumb|The first instruction approaching the first node entering the junction box]]
| |
| | [[File:JB Visual App2.png|250px|thumb|Followed by a visual only continue instruction at the second node in the junction box]]
| |
| | [[File:JB Visual App3.png|250px|thumb|The last instruction will be for Exit 1D: US-50 W • River Rd]]
| |
| |}</br>
| |
| <small>[[#Visual instructions example|Link to visual instructions example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| =====TTS=====
| |
| Even though the TTS (text to speech) box will show the name of the exit segment in gray, this name may not actually be what's spoken. If the name of the exit segment is required in TTS, be sure to confirm it by clicking the TTS field, then clicking Apply, before saving the junction box turn instruction.
| |
|
| |
| ====Restrictions====
| |
| Partial restrictions, including time-based restrictions, can be added to junction box paths just like they are to normal node-based turns. In fact, when a junction box is created, any partial restrictions that existed on segments and turns within the box are automatically copied into the applicable junction box paths, making these JB exit arrows yellow. This is similar to how drawing a JB over nodes with full turn restrictions causes applicable JB paths to have red exit arrows. After a junction box is created, all restrictions are controlled by hovering over its exit arrows and making changes there rather than on underlying segments or turns.
| |
|
| |
| =====Internal turn restriction(s)=====
| |
| The turn restrictions or time based turn restrictions for junction arrows on segments that enter the junction box are visible on the junction node within the junction box as of January 2020. Selecting that segment displays turn restrictions just like selecting a segment that is not in a junction box. There are also turn restrictions or time based turn restrictions on each exit arrow of a junction box route, this is because the junction box has taken over the exit from the entry segment and this(these) turn restriction(s) is(are) now the turn restriction(s) on the junction box exit. The same is true for time based segment restrictions on segments that enter the junction box.
| |
| [[File:JBTR.png|left|300px]][[File:JBTBSR.png|300px]]
| |
|
| |
| ====Switch Route====
| |
| There can only be one route from a specific entrance to a specific exit in a junction box. In cases where there is more than one routing option available, then the '''Switch Route''' option will appear. The switch route option will allow you to select the appropriate route through the junction box. The allowed route through a junction box should always be enabled and shown with the green path. A red exit turn arrow means that any route from the selected entry segment to the selected exit turn arrow will be disabled
| |
|
| |
| {{Anchor|Switch Routes example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Switch Routes example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| Example of the route selection in a situation where there are some alternate looping routes available. The first picture shows the typical green path for eastbound Franklin St NE as it continues across Rhode Island Ave NE. If the straight path was prohibited by a Jersey barrier and signage, then the editor can select the alternate path of southbound 15th St NE to northeast-bound Rhode Island Ave NE to eastbound Franklin St NE. The second route as shown in the second picture was set by clicking the Switch Route forward button one time.
| |
| <center>[[File:DC Route Toggle Example1a.PNG|400px]] [[File:DC Route Toggle Example2a.PNG|400px]]</center>
| |
|
| |
| Using the same example, the first picture below shows the typical green path for eastbound Franklin St NE as it continues across Rhode Island Ave NE. Disabling the path of southbound 15th St NE to northeast-bound Rhode Island Ave NE to eastbound Franklin St NE will disable all paths for eastbound Franklin St NE continuing through the junction box. Which is not the same as allowing the green path for eastbound Franklin St NE as it continues across Rhode Island Ave NE.
| |
| <center>[[File:DC Route Toggle Example1a.PNG|400px]] [[File:Example3a.jpg|400px]]</center></br>
| |
| <small>[[#Switch Routes example|Link to switch Routes example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| ====Difficult turn====
| |
| Difficult turns and time based difficult turns are available on junction box routes the same way they are used on segment turn arrows.
| |
| *Junction box difficult turns may be useful for paths that are legal but directly contradict guide signs and/or require quick weaving through multiple lanes of traffic, such as entering a highway from the right and then quickly exiting to the left.
| |
|
| |
| ===Controlling turns===
| |
| Junction boxes permit disabling multi-segment turns that are difficult to control in complex intersections. Without a junction box, controlling complex turns may require adding artificial segments and/or reducing the intersection to a single point using a [[Bowtie#Bow_tie|bow-tie]] configuration.
| |
|
| |
| {{Anchor|Controlling turns example}}
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Controlling turns example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| Take the intersection of (Leesburg Pike & Fairfax Sq/Fashion Blvd, Tysons Corner, VA) as an example. There, some turns are not allowed based upon on which street it was originally approached from. Additionally U-turns are prevented in both directions.
| |
|
| |
| When traveling northwest on {{Major Highway|Leesburg Pike}}, it appears that you may turn right using the at-grade connector (AGC) to {{Street|Fashion Blvd}} or left onto {{Street|Fairfax Sq}} or continue on {{Major Highway|Leesburg Pike}}. If you were already traveling northwest on {{Major Highway|Leesburg Pike}} before {{Ramp|Exit 47A: SR-7 W / Leesburg Pike / Tysons Corner}} or if it was entered from {{Street|Mervis Way}} to {{Primary Street|Towers Crescent Dr}}, then you are allowed to make either turn or go straight. But if you entered Leesburg Pike from I-495 S regular lanes' Exit 47A ramp, then the left turn is prohibited to Fairfax Sq; you can only turn right or go straight. The left is prohibited by a sign at the ramp.
| |
| [[File:Ramp no left turn at light.png|center|200px]]
| |
|
| |
| Without a junction box here our options to reflect these restrictions on the map would require creating artificial parallel segments connecting north from {{Ramp|Exit 47A: SR-7 W / Leesburg Pike / Tysons Corner}} to its junction node with {{Street|Fairfax Sq}} with the connections from {{Street|Mervis Way}} to {{Primary Street|Towers Crescent Dr}} that don't turn onto this artificial parallel road. This option separates the traffic flow of those vehicles approaching on {{Major Highway|Leesburg Pike}}, from those vehicles approaching from {{Street|Marvis Way}} and visually disrupts the map with the parallel segments. Another option for other areas is to layer the segments, which is discouraged by Waze since layered segments can cause data collection problems. In either case we are adding artificial segments which are unnecessary and difficult to maintain on the map.
| |
| <center>[[File:Tysons Corner Parallel Segments.png|300px]] [[File:Tysons Corner Layered.png|300px]]</center>
| |
|
| |
| With a junction box in place, we don't need to add any extra segments, to artificially alter any segment's geometry, or to create a bow-tie. We use just the one segment of {{Major Highway|Leesburg Pike}}, and draw the junction box to include the junction nodes with the ramp/major highway all the way to the major highway/left and right local streets. We can then use the junction box's turn restrictions to select which paths through the junction box should be allowed, and which should be disallowed.
| |
| [[File:Tysons Corner JB.png|center|600px]]
| |
|
| |
| Have the entire junction box within the editing screen, then select the junction box. The available entrances show up as a list to the left of the editing screen. Small white arrows appear on the junction box boundary to indicate a segment entering the junction box. If the entire junction box is not selected then all of the entrances or even no entrances may appear in the list.
| |
| [[File:Tysons Corner JB w Entrances.png|center|600px]]
| |
|
| |
| Click on either an entrance from the list to the left or the appropriate small white arrow. This displays the routes from that entrance. The initial selection from the {{Ramp|Exit 47A: SR-7 W / Leesburg Pike / Tysons Corner}} shows seven (7) Green Turn restrictions and one (1) Red Turn restriction. The exits from this segment are listed to the left. All routes are initially enabled as a Green Turn restriction '''UNLESS''' there is a simple two segment intersection that has a Red Turn restriction. In this example nw bound Leesburg Pike's right turn to Fashion Blvd is prohibited because of the At grade connector; therefore the initial junction box has that TR as red. Also note that the selected entrance segment is colored a light blue, the long green route along the allowed paths, and the very short red "non-route" on the one prohibited path. The list on the left shows the same colored Turn restriction as is on the segment. Clicking the list to the left or the actual junction box exit arrow will toggle the Turn restriction. Hovering over a junction box exit arrow shows the turn arrow tooltip.
| |
| [[File:Initial_TRs_on_JB_ramp.png|center|600px]]
| |
|
| |
| Now we will restrict the left turn from northwest-bound Leesburg Pike to Fairfax Sq, based on the restriction sign at the ramp. Click on the green arrow, and it turns to a red arrow. After clicking save '''we have the prohibited turn easily and simply mapped'''! Both the turn restriction on the junction box and the junction exit list to the left are displaying the prohibited restriction. Also there is a long red "non-route" on the prohibited route. [[File:Tysons_Corner_JB_ramp_left_only_restricted.png|center|600px]]</br>
| |
| <small>[[#Controlling turns example|Link to controlling turns example]]</small>
| |
| {{Collapsible section bottom}}
| |
|
| |
| ==Where to use==
| |
| Junction boxes are suitable only where their functions are required. If problems are easily solved with other features such as [[Glossary#Turn_Restriction|turn restrictions]], a junction box should not be used. Appropriate reasons to use a junction box:
| |
| *To prohibit a route on the same exit path when there are two different entrances, where using a regular turn restriction would also prohibit other routes that should be allowed.
| |
| *To prohibit U-turns in one or more directions on median segments between divided roads at H or # intersections
| |
| *To disable improper U-turn prevention that would otherwise be activated by the natural geometry of an intersection
| |
| *To collect more granular data on traffic that backs up unequally across different lanes of a road through multiple junction nodes, due to conditions like heavy weaving between entrances and exits on a freeway, or busy left turns through an intersection with long cycle times
| |
| *To ensure proper routing and data collection through intricate intersections containing multiple short segments
| |
| *To provide more appropriate voice prompts for movements through intersections, where segment geometry and node-based voice prompts would provide improper navigation instructions
| |
| *To provide more accurate turn instructions for a turn with multiple signs for different destinations past the turn
| |
| *To correct routing issues or improper turn instructions in [[Roundabout#Junction box|roundabouts]]
| |
|
| |
| ===Drawbacks===
| |
| Certain things cannot be done to segments and nodes that are part of a junction box without first deleting the junction box. These include:
| |
| *Changing a segment's direction between two way and one way
| |
| *Moving a junction node across the boundary of a junction box
| |
| *Adding or deleting a junction node inside a junction box
| |
| *Adding, deleting, connecting or disconnecting a segment inside a junction box
| |
|
| |
| For these reasons, junction boxes should not be used for every intersection. Where they are used, turn information should be applied to node-based turns rather than junction box paths, if possible, to avoid rework if the junction box needs to be deleted in the future.
| |
|
| |
| Note that for many years it had been impossible to cut or merge a segment, even if only an end of it was part of a junction box; the junction box had to be deleted first. This is no longer true.
| |
|
| |
| ===Overriding U-turn prevention===
| |
| A junction box will override U-turn prevention if one or more of the junction nodes are inside the junction box. Unless a prohibited turn restriction prohibits both the left turn and one turn for the U-turn.
| |
|
| |
| There are three cases to consider:
| |
|
| |
| #[[U-turn_prevention|U-turn prevention]] is properly set up and a junction box is installed over all or part of the intersection. All u-turns previously prevented by the three criteria are now allowed - '''unless prohibited by the junction box'''
| |
| #U-turns are allowed by the intersection's segment geometries but the junction box is able to prevent the u-turn by having its turn restriction prohibited
| |
| #A prohibited turn restriction prevents a left turn and a U-turn inside a junction box; the junction box is not able to override the red turn restriction and neither path will show up as an option in the junction box.
| |
| #If the JB has a <14 m segment that only has one of its nodes within the JB then the u-turn is allowed. (Even if u-turn prevention is properly set up since the JB acts like another node (median is seen as two segments) and the u-turn is routed).
| |
|
| |
| After the junction box is set up, the selected pathways through it supersede the segments' turn restrictions on the pathway within it. Therefore, if a segment's turn restriction within the pathway is later changed, that change is ignored and the pathway(s) selected through the box are not affected.
| |
|
| |
| {{Collapsible section top}}
| |
| {{HighlightBar|'''Overriding U-turn prevention example'''}}
| |
| Just click on the expand link to the right ------>
| |
| {{Collapsible section content}}
| |
| So continuing with the example in Tysons Corner, VA above:
| |
| Note that the Leesburg Pike/Fashion Blvd/Fairfax Sq intersection is properly set up for U-turn prevention; but the junction box overrides that set up and the green turn arrows now enable all U-turns in both directions. Since both U-turns are prohibited by signage at the intersection, we now have to go to '''every''' entrance and prohibit the U-turn. This means that a total of six turn restrictions have to be clicked from green to red from the ramp, from northwest-bound Leesburg Pike, from Marvis Way, from the unnamed Local Street, from Tysons Crescent Dr, and from southeast-bound Leesburg Pike. Here is the picture of the final set up from the ramp. Note the small red "non-route" on the U-turn segment, the red arrow on the junction box's path, and the red arrow on the list to the left.
| |
| [[File:Tysons_Corner_JB_ramp_left_restricted.png|center|400px]]
| |
|
| |
| [[File:Partial Coverage of intersection.png|right|200px]]You might be asking why was the SE-bound Leesburg Pike included in the Junction box instead of just having the NW-bound segments. Why couldn't the junction box look like the picture to the right? The '''entire''' Leesburg Pike/Fashing Blvd/Fairfax Sq intersection was selected in the junction box for a reason - U-turn prevention. If the top of the junction box was ending on the unnamed Local Street between Fashion Blvd and Fairfax Sq, then the U-turn prevention would be ignored and there would be no way to prevent the U-turns in either direction. Installing a red turn restriction arrow would prohibit the left and the U-turn. The left turn is allowed for all but the traffic coming from the I-495 ramp. So this feature of overriding U-turn prevention with junction boxes needs to be considered and carefully evaluated for the final shape of the junction box.
| |
| {{Collapsible section bottom}}
| |
|
| |
| ==Editing==
| |
| A Junction box is created by selecting Junction box from the [[Map_Editor_Interface_and_Controls#Draw_segments_menu|draw segments menu]] (Shortcut key {{key press|J}}). Click at one vertex of the junction box. Continue to click at each vertex of the box until the box surrounds all the junction nodes of the intersection. Double click to complete the box.
| |
| *The boundaries of the box cannot be changed once created. If you need to change the shape of the junction box, you must delete it and create it again.
| |
| *Before creating a junction box at an intersection, make sure that there are no incorrect turn restrictions including U-turns. Routes through the junction box that are prevented by existing turn restrictions cannot be enabled in the junction box.
| |
| *The routes through a junction box can be edited when it is selected. To select a junction box, click on it.
| |
| *When the junction box is selected, the left pane will show the potential connection paths through the junction box as illustrated above. Clicking the check box next to each connection path toggles between enabling or disabling routing between the indicated entry/exit pair.
| |
| *The left pane includes a button to "Select included segments." Clicking this button will select all the segments with both ends in the junction box (these are the segments that are not considered for ETA routing purposes).
| |
| *The left pane includes a name box and an address. A name can be added to the name box and the address may be edited. However, currently the name and address of a junction box has no effect.
| |
| *To delete a junction box, select the junction box and click the [[Map_Editor_Interface_and_Controls#Delete_button|delete button]] [[File:Wme_button_delete.png|25px]] (Shortcut key {{key press|Del}}).
| |
| *Changes to junction boxes (and adding new junction boxes) require a [[Tile_update#Updates|tile update]] to affect routing.
| |
| *If a junction box is deleted and then recreated using the same segments before too much time passes, the Waze routing servers can use the previously stored junction box data for any segment IDs that have not been deleted.
| |
|
| |
| ===Effects In Editor===
| |
| Junction boxes can only be edited by editors of at least [[Your_Rank_and_Points#Waze_Map_Editing_Ranks|rank]] {{rank|jb}}. Junction boxes appear in the Waze Map Editor when the [[Map_editor_interface#Layers|Junction Boxes layer]] is turned on; the two pieces of paper in the upper right of the map editing area. Junction boxes appear as a polygon around all the junction nodes of an intersection.
| |
|
| |
| All segments that enter the junction box are only partially editable. Selecting a segment that is part of a junction box results in a message: "Some attributes cannot be edited. This segment is part of a junction box. Use the junction box to edit this segment's restrictions." For further details on which attributes can be edited and which cannot, see [[#When to use|when to use]].
| |
|
| |
| [[File:Tysons_Corner_JB_w_Entrances_2021.png|500px|right]]Selecting the junction box causes the left pane to display the junction box properties. The properties show the editor that created the junction box with the date and the editor of the last update to the junction box. If changes are needed to the junction box or segments associated with the junction box, contact the identified editor or other rank {{rank|jb}} or higher editor in your area.
| |
|
| |
| The left pane shows potential entry/exit pairs with a check box ticked for each pair enabled for routing. Note that only entry/exit pair paths which are fully visible on screen are displayed. So make sure you can see the whole boundary of the JB to be sure you're getting a full list of entry/exit pair connections in the left pane.
| |
| {{Clear}}
| |
| *Routes through the junction box that pass through a single junction node (and do not cross any JB internal segments) are not controlled by the JB. Instead, they are controlled by turn restrictions in place when the junction box is created.
| |
| *Routes through the junction box that are prohibited by red turn restrictions between segments within the junction box are not considered.
| |
| *Difficult turns can be set on the junction box's turn restrictions and do affect routing in the server if the user has the appropriate setting selected.
| |
| *Any green or yellow turn restriction on a junction box can have the difficult turn attribute added for either 24/7 coverage or with time/day/date restrictions. Please refer to the [[Partial_restrictions#Adding.2Fediting_a_difficult_turn|Difficult turn]] section for editing directions.
| |
| {{clear}}
| |
|
| |
| ===Switch route selection===
| |
| [[File:WME_JB_Switch_Route.png|250px|right]]
| |
| *Select the '''entry segment''' of the junction box that you want to compare routes on.
| |
| *Hover over the appropriate '''exit turn arrow''' that you want to select the desired route.
| |
| *The switch route selection will appear between the restrictions and difficult turn options in the turn arrow tooltip box.
| |
| *Click the forward or back arrow to cycle thru the allowable routes.
| |
| *For a route that you wish to allow, always select the green route from the entry segment to the exit turn arrow. In other words do not select a route that should be disabled, select the route that should be allowed.
| |
| *A red arrow on the exit turn arrow means that any route from the selected entry segment to the selected exit turn arrow will be disabled
| |
|
| |
| If there is only one route available in the junction box then the switch route selection will not appear. Note it may take several clicks to get to the desired route.
| |
|
| |
| ===Errors when editing===
| |
| *'''Max size''' - The length of a junction box cannot exceed 0.01° latitude and 0.01° longitude. In terms of distance, the north-south linear limit is always 1110m (0.01°), while the maximum east-west linear limit varies depending on your latitude, because the length of a longitudinal degree decreases as you travel further from the equator. In the southernmost part of the continental US, 0.01° longitude translates to about 1010 m; along the Canadian border (49° N), however, 0.01° longitude is about 730 m. So the max size of a JB in Key West is about 1110 m x 1010 m (N-S "height" × E-W "width"), but along the Canadian border the max size of a JB is 1110 m x 730 m (N-S "height" × E-W "width").
| |
|
| |
| *'''Two junction node minimum''' - A junction box must include at least two junction nodes. Two junction nodes within the junction box must be connected by a segment. A junction box with only one junction node cannot be saved.
| |
|
| |
| *'''No overlapping''' - A junction node cannot be included in multiple junction boxes.
| |
|
| |
| *'''Sixteen paths max''' - No more than 16 controllable entry/exit paths can pass through '''a single-junction node''' within a junction box. A save error occurs if a junction node has more than 16 connections. This also counts the adjacent connections not displayed in the routing box list that do not cross any of the internal segments like A to G, D to J, etc.
| |
|
| |
| *'''Enabled U-turn on a two-way segment''' - Note that having U-turn(s) enabled on a two-way segment inside the junction box will increase the number of paths and can lead to the saving error message.
| |
| *'''Non-navigable segments''' - Junction nodes within a junction box can't be connected to [[Road types#Non-drivable roads|non-drivable road types]] unless connected by a virtual node. Connected non-drivable road types will generate a save error and should be disconnected from the junction within the junction box.
| |
|
| |
| ===Adding complexity===
| |
| Adding segments or junction nodes to an intersection to workaround the "one connection for every entry/exit pair" and "no more than 16 connections per node" limitations is not recommended. If such a workaround is required, please consult with your [[Country_Manager#Coordinators|country]] manager or [[Regional_Coordinator|regional coordinator]].
| |
|
| |
| ===Final Checks===
| |
| *For the final configuration, if there is not an allowed path from the entrance segment to the exit segment then there needs to be a red turn restriction arrow and red route/path.
| |
| *For the final configuration, if there is an allowed path then there needs to be a green (or yellow) turn restriction arrow and a green route/path.
| |
| *It is recommended to save the final configuration of the junction box, then either soft or hard refresh the map. After these steps recheck every route from every possible entry segment to each exit segment. This is recommended because occasionally during the save process WME will set an incorrect route and rechecking each route through the junction box will catch these errors.
| |
