Changes to Editor - New Automatic Detected Problem

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Re: Changes to Editor - New Automatic Detected Problem

Postby HandofMadness » Wed Jan 16, 2013 12:28 am

Mike-1323 wrote: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.
CM: Thailand CM: USA
Image
HandofMadness
Area Manager
Area Manager
 
Posts: 1801
Joined: Mon Apr 16, 2012 7:44 am
Location: Californialand, USA
Has thanked: 18 times
Been thanked: 372 times

Re: Changes to Editor - New Automatic Detected Problem

Postby CBenson » Wed Jan 16, 2013 11:57 am

shawndoc wrote: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.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10333
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2354 times

Re: Changes to Editor - New Automatic Detected Problem

Postby j2brown » Wed Jan 16, 2013 12:32 pm

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
Area manager for Sterling, VA
Maintainer of Unofficial advice for editors and frequent UR responses
Image
j2brown
Area Manager
Area Manager
 
Posts: 118
Joined: Thu Mar 15, 2012 12:03 am
Location: Sterling, VA
Has thanked: 3 times
Been thanked: 7 times

Re: Changes to Editor - New Automatic Detected Problem

Postby Mike-1323 » Wed Jan 16, 2013 2:15 pm

j2brown wrote: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. :roll:
Mike-1323
Area Manager
Area Manager
 
Posts: 1026
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 186 times

Re: Changes to Editor - New Automatic Detected Problem

Postby j2brown » Wed Jan 16, 2013 2:19 pm

Mike-1323 wrote: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. :roll:


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
Area manager for Sterling, VA
Maintainer of Unofficial advice for editors and frequent UR responses
Image
j2brown
Area Manager
Area Manager
 
Posts: 118
Joined: Thu Mar 15, 2012 12:03 am
Location: Sterling, VA
Has thanked: 3 times
Been thanked: 7 times

Re: Changes to Editor - New Automatic Detected Problem

Postby sockslabs » Wed Jan 16, 2013 2:43 pm

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?
SocksLabs
Area Manager: Shrewsbury/Northboro/Westboro, MA
Image
Helpful resources: Map Editor | Best Practices
sockslabs
Area Manager
Area Manager
 
Posts: 231
Joined: Tue May 24, 2011 6:58 pm
Location: Shrewsbury, MA
Has thanked: 22 times
Been thanked: 32 times

Re: Changes to Editor - New Automatic Detected Problem

Postby j2brown » Wed Jan 16, 2013 2:50 pm

I'm seeing the "save button unavailable" issue as well.
Area manager for Sterling, VA
Maintainer of Unofficial advice for editors and frequent UR responses
Image
j2brown
Area Manager
Area Manager
 
Posts: 118
Joined: Thu Mar 15, 2012 12:03 am
Location: Sterling, VA
Has thanked: 3 times
Been thanked: 7 times

Re: Changes to Editor - New Automatic Detected Problem

Postby nnote » Wed Jan 16, 2013 3:30 pm

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..
USA Territories Regional Coordinator : USA Champ : L6 State Manager Arizona
Image
G+ Waze Arizona
Waze Arizona Twitter
nnote
US Waze Champs
US Waze Champs
 
Posts: 563
Joined: Sun Jun 19, 2011 6:25 pm
Location: Arizona USA
Has thanked: 60 times
Been thanked: 268 times

Re: Changes to Editor - New Automatic Detected Problem

Postby Machete808 » Wed Jan 16, 2013 4:47 pm

nnote wrote: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.
Aloha,
Vicki
Hawaii State Manager
Area manager, Los Angeles
Country manager, Thailand
Image Image
Need support?
support.google.com/waze > Popular topics > FAQs > Other > Open a ticket
Welcome, new editors:
Here's a good place to start!
Machete808
State Manager
State Manager
 
Posts: 1298
Joined: Mon May 28, 2012 12:36 am
Location: Kaneohe, HI
Has thanked: 194 times
Been thanked: 214 times

Re: Changes to Editor - New Automatic Detected Problem

Postby sockslabs » Wed Jan 16, 2013 5:16 pm

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.
SocksLabs
Area Manager: Shrewsbury/Northboro/Westboro, MA
Image
Helpful resources: Map Editor | Best Practices
sockslabs
Area Manager
Area Manager
 
Posts: 231
Joined: Tue May 24, 2011 6:58 pm
Location: Shrewsbury, MA
Has thanked: 22 times
Been thanked: 32 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Bing [Bot]