Post Reply

[Page Update] Junction Style Guide

Post by
We have a number of threads covering some changes to the Junction Style Guide (JSG) right now.

Sketch, myself, and others have discussed some upcoming changes we are all proposing, so I wanted to have a thread where we could coordinate them.

In general the overall JSG is much too large to follow all the way through. We have proposed moving some of the larger sections into subpages and leaving the JSG as a master index to everything related to junctions.

I currently have some updates I am proposing for the following sections:

The new basepage https://wiki.waze.com/wiki/Junction_Sty ... e/Revision will move into the original JSG pagename. It will only include the changed content from the sections currently holding:
The basics (reformatted the orignal)
Diverging roads (moved content to a subpage)
Crossing roads (moved content to a subpage)
Controlling turn instructions (this may need to get incorporated into changes already being proposed by sketch.)

These pages in these links become subpages of the JSG linked from the JSG. I have reformatted these sections to be a little more organized and edited the content a bit for clarity.

Any other content from the current JSG page or other changes proposed by sketch or others in other sections would not be overwritten.

Post by CBenson
I said something similar in the other thread, but I don't believe the geometry guidance laid out in this JSG. I have never found an intersection configuration that gives an instruction at 33 degrees where you could eliminate the instruction by changing the angle to zero degrees. I do not believe that having a departure angle between 0-21 degrees does anything to suppress navigation instructions.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
I'm confused again. I thought your testing showed this to be true for a split with two options as well.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
I see that as being true for a two way split as well. But I guess for a two branch split it is correct, while for more branches it becomes problematic.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902


Post by Bigbear3764
qwaletee wrote:
Thanks. I guess this one sort-of-is sort-of-isn't truly an interchange. Be nice to mention some of the major interchange types on the main page in the summary section.
I see what you mean. Someone must have fixed the redirect on it. I searched now and got the 2 results for Junction Style Guide and Junction Style/Interchanges.
Bigbear3764
Country Manager
Country Manager
Posts: 2620
Has thanked: 202 times
Been thanked: 962 times

Post by CBenson
I would just note that if the information here is correct, then a plain box intersection has the disadvantage that the timing data for a straight movement is not distinguished from the timing data for a left turn. There is some question as to how much this contributes to right/U/right routes in place of straight through routes. Theoretically, neither the bowtie nor the diagonals in the box method suffer from this problem.

I acknowledge this is highly speculative as it depends on how the data is collected and assigned to small segments is small areas.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
qwaletee wrote:A plain box intersection as opposed to what? A bowtie with a single convergence point?
Yes. A plain box as opposed to either a bowtie with a single convergence point or a box with diagonals with the three segments (one for each direction) connected to the segment on which you wait for the light.
qwaletee wrote: The box breaks off the right from the left and straight through. The only problem might be the chunking of left together with other traffic, at a left turn restrictive signal.
Exactly.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
Your conclusion doesn't seem to address your premises.
PesachZ wrote:Based on my under standing of the turn delay recordings, and how it is affected by these small segments it would not cause the right-u-right vs. straight.
Here you say right-u-right vs. straight.
PesachZ wrote:This will not cause a Right-Uturn-Right though instead of a left unless the time it takes to complete that maneuver is less than the time it would take to pass through the intersection from the beginning of that short segment and turn left (a very short time). If the situation is such that a right-u turn-right is faster than a left, it would be suggested even without the short segment in the mix.
Here you say Right-Uturn-Right instead of a left.

I think I agree with your facts and logic, but you haven't actually addressed right-u-right vs. straight routes.

The theory is that the short segment between the split segments causes waze to fail to distinguish between traffic turning left and traffic going straight. Say there is a long red for the left turn when the straight through is green, but not the opposite, a fairly common configuration. Then as waze doesn't distinguish between the left turn traffic and the straight traffic, waze thinks the left turn is a faster than reality and that the straight traffic is slower than reality. We do see the occasional right-u-right route. Anything that causes waze to underestimate the time of the straight route, should in theory contribute to more right-u-right routes.

The question is simply whether the cross-segment causes waze to fail to distinguish between left turn traffic and straight traffic. If the bowtie and the box with diagonals configurations enable waze to distinguish between left turn traffic and straight traffic, then that would be an advantage to those configurations.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by Bigbear3764
Something to consider, and I'm not sure where you would put. I had someone on chat with a UR where someone was routed off and back on a highway. When I started looking at the road names to make sure the detour prevention mechanism was working properly, I found a segment with no name. The person on chat said he had just requested a wayfinder at the interchange. So in order to get the 2 out Freeway segments to be different names, he had changed the one to No Name.

It was a simple fix to divide the No Name segment and to name it before the next ramp to get the detour prevention mech to work.

Maybe just a note to be aware of other situations in the area like Detour Prevention.
Bigbear3764
Country Manager
Country Manager
Posts: 2620
Has thanked: 202 times
Been thanked: 962 times

Post by Bigbear3764
KB_Steveo wrote: Yeah, I've noticed this, the other day I took a left on to a road with a roundabout, just after I took my left, I heard "continue straight for xx minutes to Hwy-YY" or something similar, with no mention of the roundabout. When I got to the roundabout, it only told me to continue straight, with no mention of the street name, and then reminded me of my turn at Hwy-YY.
CR-A, north of Grand Chute? I go thru there quite a bit. That one use to work fine, after the update, no. Toolbox doesn't highlight it as wrong either.
Bigbear3764
Country Manager
Country Manager
Posts: 2620
Has thanked: 202 times
Been thanked: 962 times