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 CBenson » Fri Jan 18, 2013 5:34 pm

It would be helpful if any reports regarding the problems not showing (or any reports that they are showing correctly) be posted in this thread:
viewtopic.php?f=8&t=37502&start=20
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

Re: Changes to Editor - New Automatic Detected Problem

Postby kodi75 » Fri Jan 18, 2013 5:22 pm

With this new batch of automatic Waze reports, I (and others) have experienced problems getting the reports to even show up. Any tricks / workarounds? My cache is set to clear every time I close the browser ...

Waze's servers are probably just overloaded - hopefully lesson learned for next time they run the script.
kodi75
Country Manager
Country Manager
 
Posts: 841
Joined: Mon Jul 02, 2012 3:43 am
Location: Central Maryland
Has thanked: 743 times
Been thanked: 254 times

Re: Changes to Editor - New Automatic Detected Problem

Postby ArlenBystander » Thu Jan 17, 2013 6:37 am

sockslabs wrote: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.


My trick was to click Solved then change one other item (change a turn, move a segment, etc.). This would enable the save and undo buttons (number of changes would be off by one). I would then undo the last change (now the number of changes is correct) and then save.
ArlenBystander
Map Raider
Map Raider
 
Posts: 475
Joined: Fri Oct 26, 2012 11:42 am
Location: Chicago western suburbs
Has thanked: 4 times
Been thanked: 198 times

Re: Changes to Editor - New Automatic Detected Problem

Postby HandofMadness » Wed Jan 16, 2013 6:40 pm

CBenson wrote:
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.


I've never had it happen to me, but I've seen many UR's where it shows more of the route, and it has the user turn into a dead end, turn around at the end, and head back out going back the way they came.
HandofMadness
Area Manager
Area Manager
 
Posts: 1802
Joined: Mon Apr 16, 2012 7:44 am
Location: Californialand, USA
Has thanked: 19 times
Been thanked: 375 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
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 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.
Machete808
Country Manager
Country Manager
 
Posts: 1403
Joined: Mon May 28, 2012 12:36 am
Location: Kaneohe, HI
Has thanked: 229 times
Been thanked: 267 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..
nnote
US Waze Champs
US Waze Champs
 
Posts: 575
Joined: Sun Jun 19, 2011 6:25 pm
Location: Arizona USA
Has thanked: 65 times
Been thanked: 281 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.
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
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: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
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

Next

Return to Waze Map Editor

Who is online

Users browsing this forum: andrewhappybark, Yahoo [Bot]