Changes to Editor - New Automatic Detected Problem

[shawndoc]

This routing down dead end streets has me wondering if the terminal junction on the segment is corrupt or has some connectivity issues. I've noticed that sometimes the JNF script will actually 'fix' the terminal node on a dead end even though the highlights scrip doesn't indicate anything's wrong. I think a self connected terminal node may cause, or at least allow, this type of route to come out of the server.

Nah, its just that dead end segments are the only place Waze officially supports U-Turns. So if Waze wants the user to go back the other direction, and there's no "around the block" routes it can give them, it sends them to the closest dead end to turn around.

The problem with this system generated UR, is it will only show 2 segments of the route. The segments before and after the turn. Waze just wants us to double check that the turn is properly allowed, not to troubleshoot the entire route. So if it is allowed, and it looks like a dead end u-turn, mark as solved. If it looks like it is allowed, and its not a dead end u-turn, you might want to scan ahead to see if there's anything else wonky going on at the next few junctions to cause Waze to want to turn someone too early. But with only 2 segments of the route, and no idea where they are going its often impossible to know why Waze gave the turn direction and why drivers ignored it.

[CBenson]

Nah, its just that dead end segments are the only place Waze officially supports U-Turns. So if Waze wants the user to go back the other direction, and there's no "around the block" routes it can give them, it sends them to the closest dead end to turn around.

I don't believe that this is true. First, its not like waze gives a U-turn instruction on dead end segments. Second, there are plenty of time that waze does not send me to the closest dead end to turn around, but rather passes up several dead end roads to turn around on another.

[j2brown]

I came across another round of these errors this morning. For at least two of them in my area the Waze suggested route went through turns that were marked as restricted. Is this an artifact of using old data, as discussed above, or is there something new afoot?

Here's an example:

https://www.waze.com/editor/?zoom=7&lat ... s=53326141

The route that users ignored was a U turn in the Y


Possibly related: I've noticed a few cases recently where Waze won't route straight through what appears to me to be a correct intersection, but instead send folks down the side street to make a U turn, then return to the route of travel and continue in the same direction. (right turn, left handed u-turn, another right turn). It's usually at the intersection of two divided roads ( # ). At first I thought that the short segments in the intersection (making up the box) might be the issue, but they appear to be of the proper road type, in the proper direction, with the proper turns allowed/restricted.

Unfortunately I don't have a handy example of that.

Thoughts?

jeff
sdg

[Mike-1323]

Possibly related: I've noticed a few cases recently where Waze won't route straight through what appears to me to be a correct intersection, but instead send folks down the side street to make a U turn, then return to the route of travel and continue in the same direction. (right turn, left handed u-turn, another right turn). It's usually at the intersection of two divided roads ( # ). At first I thought that the short segments in the intersection (making up the box) might be the issue, but they appear to be of the proper road type, in the proper direction, with the proper turns allowed/restricted.

Unfortunately I don't have a handy example of that.

Thoughts?

The way that I've chosen to interpret that type of routing is that there is such a large delay in the junction transit time when waiting for a red light at an intersection that the routing server calculates it is faster to take a low-delay right turn, two low-delay left turns and another low-delay right turn. Of course this theory falls apart when the routing server directs somebody to make a u-turn on a dead end and then continue in the same direction on the original road when there's no light or stop sign along the original road.

[j2brown]

The way that I've chosen to interpret that type of routing is that there is such a large delay in the junction transit time when waiting for a red light at an intersection that the routing server calculates it is faster to take a low-delay right turn, two low-delay left turns and another low-delay right turn. Of course this theory falls apart when the routing server directs somebody to make a u-turn on a dead end and then continue in the same direction on the original road when there's no light or stop sign along the original road.

I've thought that too. I've seen one instance where Waze tried to route me down a frontage road to get around slow traffic. The traffic was caused by a crossing guard, and the frontage road emptied at the same intersection, so the route would not only have been slower but if enough folks followed it it would really mess up traffic when school is getting out. Not much we can do in this case, but it does show Waze trying a similar tactic to get around a slow intersection.

jeff
sdg

[sockslabs]

About one out of 10 times:

https://www.waze.com/editor/?zoom=0&lat ... TTTTTTTTFT

I see a few dozen "Most users did not follow the suggested route" automatic reports. Most times the radar is clean.

When I try to resolve one, the "save" button is unavailable. But if I click between solved and unidentified enough times, the save button becomes available and I can save it.

Here's what I think is happening: there's one Waze server out of a dozen that is out of sync with the others, and it's causing both symptoms.

Is anyone else noticing this behavior?

[j2brown]

I'm seeing the "save button unavailable" issue as well.

[nnote]

Save button unavailable. Also very slow this morn.
These auto generated are also showing me where alot of times waze is trying to cut a corner of an intersection where people are turning left. Instead of turn left at a light, it tries to send them down a side street to turn left onto that major road. I'd rather turn left at a light then from a side street..

[vickimachado]

Save button unavailable. Also very slow this morn.
These auto generated are also showing me where alot of times waze is trying to cut a corner of an intersection where people are turning left. Instead of turn left at a light, it tries to send them down a side street to turn left onto that major road. I'd rather turn left at a light then from a side street..

I've been noticing the same thing on a regular route of mine. Waze passes the left-turn at the intersection with a light and directs me to a U-turn at a break in the highway median.

[sockslabs]

The following sequence seems to unwedge the save button:

• Click on the report.
• Hit Solved.
• Hit Close.
• Click on the report again.
• Hit Not identified, and the save button wakes up.