[Page Update] Junction Box

[Nagamasa]

https://wazeopedia.waze.com/wiki/USA/Junction_box

@top_gun_de

The topic of resource-usage was brought up […] in the WE-EU-meetup, and staff explicitly said that this is no longer an issue. We should use Junction boxes whenever they make sense to improve ETA.

@MapSir

Hey Guys,

Indeed most resource issues were solves and you can use JB’s as long as they make sense.

I’d like to update the Function and When not to use sections:

The junction box enables a complex intersection, or interchange composed and displayed as multiple junction nodes to be treated by the routing server as a single junction node with multiple inputs and outputs. A junction box:

• collects traffic speed data for each path separately.
• allows an editor to set turn restrictions separately for each path.
  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. They do not have an effect on navigational prompts and have no visibility in the client or on the live map. They also do not affect the search engine; the origin or destination of route may be contained in a junction box.

Segment construction that were created solely to work around turn restrictions across multiple segments or segment timing across multiple nodes should generally be deprecated and replaced with a Junction Box.

When not to use
Junction boxes do not currently allow editing of some properties of the connected segments. If editing is required, they must be deleted and then re-created.

Consequently, they should be avoided when:

• The impact of the superior data collection is limited. Don’t use a junction box at every intersection, as you’d be locking away every segment!
• The underlying segments are knowingly incomplete or imminently changed. Make sure the segments are as complete as possible, and so it require minimal updating in the future.
• The only purpose is to disallow a u-turn, and is geometrically feasible in Waze.

[RussPA]

There is a major redo of the Junction Box in the works. Other changes to the guidelines will likely need to be made after that time as well.

[Nagamasa]

Yes we would, but from what I’ve read there, none of it affects the content I’m changing.

[ehepner1977]

I agree with the proposed additions/corrections, and also agree that the update will not affect the proposal. I don’t want to put words in RussPA’s keyboard, but I suspect his point was that the JB wiki will need a major revamp when the new stuff comes online, so why not hold off until that happens? If that’s the case, I sort of agree, but don’t see any real harm in fixing existing guidance while we wait for Waze to sort out all of the back end issues.

I did note a a minor grammar nit pick

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.

The to in “to at” is superfluous.

[RussPA]

@ehepner1977

I don’t want to put words in RussPA’s keyboard, but I suspect his point was that the JB wiki will need a major revamp when the new stuff comes online, so why not hold off until that happens?

Yes, that was my point, I could have made that clearer. The wiki will need many changes, I figured it would be easier to make them all at once, and to make sure nothing in the proposed change will itself be changed with the new JB.

[Nagamasa]

I suppose so.

I haven’t updated anything technical.

All I’ve changed is removing language about heavy server use and we should use them instead of workarounds.

When the next update comes around, we can update the actual meat of the JB article!