Kartografer (talk | contribs) (fleshed out overview with existing image links) |
Kartografer (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
[[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 are all connected together at one place." Because of this, junction box connections provide an extra layer of information on top or instead of the information associated with individual nodes, segments and turns. | [[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 are all connected together at one place." Because of this, junction box connections provide an extra layer of information on top or instead of the information associated with individual nodes, segments and turns. | ||
==== A note on terminology ==== | |||
As development around junction boxes has progressed, different words have been used to describe them and their parts. In the underlying data of the [[WME|Waze Map Editor]] junction boxes are called bigJunctions, and each allowed route from an entry segment through a junction box to an exit segment is called a crossroadConnection. The newer and similar [[path]] entity is called a pathConnection in WME data. The '''connections''' between the entry and exit segments of both junction boxes and paths are also known as '''far turns''' in some parts of the WME interface; just as a normal turn crosses one node to another segment, a far turn crosses multiple nodes and intermediate segment(s) to another segment. Although editors have often called these parts of a junction box "paths", for clarity this page primarily uses the term "connection" when referring to the routes through junction boxes, with "far turn" used as a synonym when referring to certain parts of the user interface. | As development around junction boxes has progressed, different words have been used to describe them and their parts. In the underlying data of the [[WME|Waze Map Editor]] junction boxes are called bigJunctions, and each allowed route from an entry segment through a junction box to an exit segment is called a crossroadConnection. The newer and similar [[path]] entity is called a pathConnection in WME data. The '''connections''' between the entry and exit segments of both junction boxes and paths are also known as '''far turns''' in some parts of the WME interface; just as a normal turn crosses one node to another segment, a far turn crosses multiple nodes and intermediate segment(s) to another segment. Although editors have often called these parts of a junction box "paths", for clarity this page primarily uses the term "connection" when referring to the routes through junction boxes, with "far turn" used as a synonym when referring to certain parts of the user interface. | ||
Line 56: | Line 56: | ||
===Controlling turns=== | ===Controlling turns=== | ||
[[File:Ramp no left turn at light.png|300px|thumb| | [[File:Ramp no left turn at light.png|300px|thumb|Drivers on this ramp who merge onto the next highway can be prevented from turning left at the next intersection, with the left turn allowed for all other drivers.]]Junction boxes permit disallowing, partially restricting or marking as difficult turns complex intersections. Without a junction box, controlling complex turns formerly required adding artificial segments and/or resorting to unrealistic road geometries. | ||
===Fine-tuning instructions=== | ===Fine-tuning instructions=== | ||
[[File:WME JB Visual BGS.jpg|300px|thumb | [[File:WME JB Visual BGS.jpg|300px|thumb|At complex, multi-lane and multi-sign exits, Waze now has the ability to give only the relevant information to the driver based on their next turn.]]Both junction boxes and paths enable editors to give drivers much more specific instructions through complex intersections than are otherwise available. This could be telling the driver to user only the rightmost of three right-turning lanes, because their route has another right turn in quick succession. Or it could involve showing and reading just one of multiple exit signs present at a freeway exit. Far turn instructions and far lanes are powerful tools to improve the navigation experience in Waze. | ||
==Where to use== | ==Where to use== | ||
Junction boxes are suitable only where their functions are required. If problems are easily solved with other features such as | Junction boxes are suitable only where their functions are required. If problems are easily solved with other features such as paths or simple 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 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 | *To prohibit U-turns over median segments between divided roads at four-way H or # intersections. | ||
*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 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 ensure proper routing and data collection through intricate intersections containing multiple short segments. | ||
*To correct routing issues or improper turn instructions in [[Roundabout#Junction box|roundabouts]]. | |||
Junction boxes provide the ability to fine-tune voice prompts, visual instructions, TTS and lane guidance through them. However, paths also offer this functionality and are easier to use in most cases. Therefore, a junction box should not be used purely to alter navigation instructions or lane guidance. These are secondary uses of a junction box that is already required for the reasons listed above. | |||
*To correct routing issues or improper turn instructions in [[Roundabout#Junction box|roundabouts]] | |||
===Drawbacks=== | ===Drawbacks=== | ||
Line 78: | Line 77: | ||
*Adding, deleting, connecting or disconnecting a segment 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 | 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 far turns, 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 | Note that for many years it had been impossible to cut or merge a segment that enters or exits a junction box; the JB had to be deleted first. This is no longer true. However, if you encounter a permissions error after cutting or merging one of these segments, try disallowing one of the JB far turns that exits at the cut/merged segment. This will usually let the save happen, after which the far turn can be allowed again and saved. | ||
==Editing== | ==Editing== | ||
Line 102: | Line 101: | ||
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. | 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. | ||
*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 simple turn restrictions. | |||
*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 | |||
*Routes through the junction box that are prohibited by red turn restrictions between segments within the junction box are not considered. | *Routes through the junction box that are prohibited by red turn restrictions between segments within the junction box are not considered. | ||
===Far turn menu=== | ===Far turn menu=== | ||
[[File:Wme_turn_override_hover5.png|250px|right]] The far turn menu for junction box connections has five elements: Voice prompt, Instructions, Restrictions, Switch Route (when applicable), and Difficult turn. If none of these elements is changed, Waze will simply use whatever settings exist for the underlying turns through the nodes that make up the junction box connection. | [[File:Wme_turn_override_hover5.png|250px|right]] The far turn menu for junction box connections has five elements: Voice prompt, Instructions, Restrictions, Switch Route (when applicable), and Difficult turn. If none of these elements is changed, Waze will simply use whatever settings exist for the underlying turns through the nodes that make up the junction box connection. | ||
====Voice prompt & Instructions==== | ====Voice prompt & Instructions==== | ||
{{User:Kartografer/ | {{User:Kartografer/Far turn instruction}} | ||
====Restrictions==== | ====Restrictions==== | ||
Partial restrictions, including time-based restrictions, can be added to junction box far turns just as to normal node-based turns. In fact, when a junction box is created, any partial restrictions that exist on segments and turns within the junction box are automatically copied into the applicable junction box far turns, making these JB turn arrows yellow. This is similar to how drawing a JB over nodes with full turn restrictions causes applicable JB far turns to have red arrows. After a junction box is created, all restrictions are controlled by hovering over its far turn arrows and making changes there rather than on underlying segments or turns. | Partial restrictions, including time-based restrictions, can be added to junction box far turns just as to normal node-based turns. In fact, when a junction box is created, any partial restrictions that exist on segments and turns within the junction box are automatically copied into the applicable junction box far turns, making these JB turn arrows yellow. This is similar to how drawing a JB over nodes with full turn restrictions causes applicable JB far turns to have red arrows. After a junction box is created, all restrictions are controlled by hovering over its far turn arrows and making changes there rather than on underlying segments or turns. |
Revision as of 15:09, 24 February 2023
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 are all connected together at one place." Because of this, junction box connections provide an extra layer of information on top or instead of the information associated with individual nodes, segments and turns.
A note on terminology
As development around junction boxes has progressed, different words have been used to describe them and their parts. In the underlying data of the Waze Map Editor junction boxes are called bigJunctions, and each allowed route from an entry segment through a junction box to an exit segment is called a crossroadConnection. The newer and similar path entity is called a pathConnection in WME data. The connections between the entry and exit segments of both junction boxes and paths are also known as far turns in some parts of the WME interface; just as a normal turn crosses one node to another segment, a far turn crosses multiple nodes and intermediate segment(s) to another segment. Although editors have often called these parts of a junction box "paths", for clarity this page primarily uses the term "connection" when referring to the routes through junction boxes, with "far turn" used as a synonym when referring to certain parts of the user interface.
Overview
The junction box enables a complex intersection or interchange comprising multiple segments to be treated by the routing server somewhat like a single junction node with multiple entry and exit segments. Considering a complex intersection as a single entity has several beneficial properties:
- Traffic speed data for each connection through the junction box can be collected separately.
- Turn restrictions can be separately controlled for each far turn through the junction box.
- Voice prompts can be separately assigned for each far turn through the junction box.
- Turn instructions can be separately assigned for each far turn through the junction box.
- Lane guidance can be separately assigned for each far turn through the junction box.
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 that enter or exit it are directly connected.
Junction boxes are stored on the routing server. They are not visible 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.
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.
- When the user experiences loss of Internet connection and must rely on client-based routing.
Improving data collection
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.
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.
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.
- A ➡ B
- A ➡ E
- A ➡ F
- B ➡ A
- B ➡ E
- B ➡ F
- E ➡ A
- E ➡ B
- E ➡ F
- F ➡ A
- F ➡ B
- F ➡ E
With a junction box the connections from A to F, and from 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.
Controlling turns
Junction boxes permit disallowing, partially restricting or marking as difficult turns complex intersections. Without a junction box, controlling complex turns formerly required adding artificial segments and/or resorting to unrealistic road geometries.
Fine-tuning instructions
Both junction boxes and paths enable editors to give drivers much more specific instructions through complex intersections than are otherwise available. This could be telling the driver to user only the rightmost of three right-turning lanes, because their route has another right turn in quick succession. Or it could involve showing and reading just one of multiple exit signs present at a freeway exit. Far turn instructions and far lanes are powerful tools to improve the navigation experience in Waze.
Where to use
Junction boxes are suitable only where their functions are required. If problems are easily solved with other features such as paths or simple 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 over median segments between divided roads at four-way H or # intersections.
- 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 correct routing issues or improper turn instructions in roundabouts.
Junction boxes provide the ability to fine-tune voice prompts, visual instructions, TTS and lane guidance through them. However, paths also offer this functionality and are easier to use in most cases. Therefore, a junction box should not be used purely to alter navigation instructions or lane guidance. These are secondary uses of a junction box that is already required for the reasons listed above.
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 far turns, 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 that enters or exits a junction box; the JB had to be deleted first. This is no longer true. However, if you encounter a permissions error after cutting or merging one of these segments, try disallowing one of the JB far turns that exits at the cut/merged segment. This will usually let the save happen, after which the far turn can be allowed again and saved.
Editing
A Junction box is created by selecting Junction box from the draw segments menu (Shortcut key 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 connections 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 connections 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 delete button (Shortcut key Del).
- Changes to junction boxes (and adding new junction boxes) require a 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 rank 4. Junction boxes appear in the Waze Map Editor when the 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.
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 4 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.
- 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 simple turn restrictions.
- Routes through the junction box that are prohibited by red turn restrictions between segments within the junction box are not considered.
The far turn menu for junction box connections has five elements: Voice prompt, Instructions, Restrictions, Switch Route (when applicable), and Difficult turn. If none of these elements is changed, Waze will simply use whatever settings exist for the underlying turns through the nodes that make up the junction box connection.
Voice prompt & Instructions
Just as with turns through nodes, voice prompts, turn instructions and TTS can be customized for far turns through junction boxes and paths.
Please note: Although turn instruction information is added by hovering over the exit arrow of the far turn, in most cases it is applied at the entrance. Think about what the driver sees at the entrance when adding turn instruction information to paths and JBs.
Voice prompt
If a voice prompt override is added to a far turn, then all internal Waze selected voice prompts are removed, and the voice prompt is announced at the first node of the path or JB connection. As of February 2023[update] (except for in some in-car interfaces like Android Auto) the name of the exit segment is displayed and spoken by default, just as the turn arrow tooltip indicates, even there is a named segment before it inside the path/JB.
If a voice prompt override is added to a far turn, and lane guidance has also been set up where the voice prompt is given, the lane guidance will be displayed with the voice prompt. Make sure to check the lane guidance when adding a voice prompt (and anything else, really) to far turns, and add far lanes if necessary.
Instructions
A voice prompt can also be added in the Instructions panel. If all other fields in this panel are blank or unchanged from their default values, the voice prompt override will function alone, just as if it had been added directly from the turn arrow tooltip. On paths the voice prompt can only be changed in the Instructions panel.
All other elements of the Instructions panel function together (the various visual instruction fields and TTS). They are usually given at the first node, like the voice prompt, but if the criteria of the 50-meter rule are met, they are given at the next full turn instruction. They require a full turn instruction to have an effect; if the driver is not told to turn, exit, continue, etc. where this information would be given, no visual instructions can be displayed there, and no auditory instructions can be spoken.
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 (turning the text from gray to black), then clicking Apply, before saving the far turn instruction.
Usage of far turn instructions
Where they are used, turn instructions should be applied to simple, node-based turns rather than far turns (JBs and paths), if possible, to avoid rework if the junction box or path needs to be deleted in the future. Reasons for customizing far turn instructions include:
- Multiple signs are displayed for a single turn, with each sign pertaining to the next turn (see example at right). Customize the visual instructions and TTS, but usually not the voice prompt, so as not to suppress the next turn instruction.
- A sign pertains to a straight movement through a divided road intersection, and a continue straight instruction is necessary. Customize the visual and TTS instructions, and add a Continue voice prompt.
- One or more divided roads meet at a roundabout, and normal instructions are desired and/or there are different signs at different entrances that pertain to the same exit. Customize the visual instructions and TTS, and/or add turn right/continue/turn left/U-turn voice prompts, as necessary.
- Segments connect in an intersection in such a way that, with realistic geometry and node-based turn instructions, incorrect voice prompts are given. Customize the far turn's voice prompt.
Conflicts
Far turn voice prompts conflict with all near turn (single node) voice prompts within the connection. If a voice prompt is set on any of the near turns that make up a connection, the far turn's voice prompt has no effect.
Far turn visual and/or TTS instructions only conflict with near turn instructions where they are given (usually on the first node, or on the first turn where the far lanes 50-meter rule is active). Visual and/or TTS instructions can be used on the other turns in paths or junction box connections. Be sure to remove conflicting information from near turns when working with far turn instructions.
For more information on turn instructions, see the turn instruction page.
Restrictions
Partial restrictions, including time-based restrictions, can be added to junction box far turns just as to normal node-based turns. In fact, when a junction box is created, any partial restrictions that exist on segments and turns within the junction box are automatically copied into the applicable junction box far turns, making these JB turn arrows yellow. This is similar to how drawing a JB over nodes with full turn restrictions causes applicable JB far turns to have red arrows. After a junction box is created, all restrictions are controlled by hovering over its far turn 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. Selecting an entry segment displays normal 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.
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.
Difficult turn
Difficult turns (including time-based ones) can be applied to junction box far turns the same way that they are applied to normal turns. They cause a routing penalty to be applied to the far turn if the user has difficult turn avoidance turned on, which is the default setting for all new users at least since 2019. Please refer to the Difficult turn section for editing directions.
Difficult turns may be useful for far turns 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.
Switch route selection
- 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 to be used for the connection.
- The switch route selection will appear between the restrictions and difficult turn options in the far turn menu 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, 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").
- No overlapping - A junction node cannot be included in multiple junction boxes, nor can a segment be included in both a junction box and a path.
- One connection minimum - A junction box must include at least two junction nodes and one segment, with at least one allowed connection (green or yellow far turn) through them. Otherwise, there is nothing to control. A junction box with only one junction node cannot be saved.
- Sixteen connections maximum - As of February 2023[update] no more than 16 routable connections 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 does not count fully restricted connections, where the far turn arrow has been made red, as this actually deletes the connection. It is unclear whether the system counts near turns (single-node U-turns or other turns that do not cross the JB's internal segments) as part of this total. In some situations, WME will say that the sixteen-connection limit has been exceeded, even where the number of visible allowed far turns is lower, even as low as twelve. In other situations, WME will save a junction box that has more than sixteen far turns and near turns through a node, even as high as twenty.
- Note that having a U-turn enabled on a two-way segment inside junction box will increase the number of connections and can lead to the saving error. If you encounter this message, look for connections to disallow.
- Adding artificial complexity to work around the sixteen-connection maximum is not recommended. If such a workaround is required, please consult with your state manager or regional coordinator.
- Non-navigable segments - Junction nodes within a junction box can't be connected to 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. This includes railroads.
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.
Select example use cases