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: 3604
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 HandofMadness » Wed Dec 19, 2012 10:42 pm

They didn't start showing up for me until I cleared my cache.
CM: Thailand CM: USA
Image
HandofMadness
Area Manager
Area Manager
 
Posts: 3604
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 HandofMadness » Wed Dec 19, 2012 6:46 pm

AlanOfTheBerg wrote:If Wazers continually get stuck in the back-ups waiting a long time to make a difficult turn, then Waze will eventually have that data and be less likely to give that turn instruction at the times of day where it finds traversing that segment-to-segment pair is very slow. I say let the data do the work.


You are assuming they'll get backed up there, vs saying "This won't work" and making a right turn causing this error to be generated.
CM: Thailand CM: USA
Image
HandofMadness
Area Manager
Area Manager
 
Posts: 3604
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 HandofMadness » Wed Dec 19, 2012 6:29 pm

These aren't time restricted turns. They're perfectly legal instructions, just hard to follow. My preference would be to close these as solved and not change anything, however I feel we may need to put something in the Wiki to refer new users to. I expect with this new auto-generated problem we'll find a lot of legal turns restricted in order to "solve" the problems.
CM: Thailand CM: USA
Image
HandofMadness
Area Manager
Area Manager
 
Posts: 3604
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 HandofMadness » Wed Dec 19, 2012 5:45 pm

This brings up an age old question: How to handle left turns that may be difficult/impossible at certain times of the day?

In Los Angeles, Waze loves to route people down side or residential roads, and will often direct people to either turn left or go straight across when hitting the major roads. These directions are perfectly legal, however during busier periods these directions are hard/dangerous to follow, since there is no light and it often requires crossing 4~6 lanes of busy road.

I bring this up, since this new "problem" brings up a ton of these.
CM: Thailand CM: USA
Image
HandofMadness
Area Manager
Area Manager
 
Posts: 3604
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 esochan » Wed Dec 19, 2012 10:28 pm

CrackedLCD wrote:Is this feature only in certain areas so far? I zoomed out just a little while ago and didn't see any new errors beyond the existing ones on locked roads that I cannot fix and are leaving for Level 5s in the area to handle.

I find it hard to believe we're totally error free in my region, but it would kinda awesome if it were true. There's some hard working editors around here who've really made these roads shine over the last six months or so.


My immediate area was error free. I had to scroll down to the Sacramento and surrounding areas where there were numerous ones.
Area Manager: Yuba City/Marysville, Oroville, Chico/Paradise/Magalia, California
Image
esochan
 
Posts: 162
Joined: Sat Oct 06, 2012 3:21 am
Location: Chico, CA, USA
Has thanked: 6 times
Been thanked: 3 times

Re: Changes to Editor - New Automatic Detected Problem

Postby CrackedLCD » Wed Dec 19, 2012 9:37 pm

Is this feature only in certain areas so far? I zoomed out just a little while ago and didn't see any new errors beyond the existing ones on locked roads that I cannot fix and are leaving for Level 5s in the area to handle.

I find it hard to believe we're totally error free in my region, but it would kinda awesome if it were true. There's some hard working editors around here who've really made these roads shine over the last six months or so.
~CrackedLCD
AM for Baldwin-Mobile Cos., AL // Grenada-LeFlore-Carroll Cos., MS // Escambia-Santa Rosa Cos., FL // CM for the USA

Moto Droid Turbo (Android 5.1) on Verizon Wireless
Image
CrackedLCD
Area Manager
Area Manager
 
Posts: 852
Joined: Thu Aug 02, 2012 12:37 am
Location: LA (Lower Alabama)
Has thanked: 97 times
Been thanked: 63 times

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

Re: Changes to Editor - New Automatic Detected Problem

Postby CBenson » Wed Dec 19, 2012 3:21 pm

joshellis625 wrote:sweet baby jesus I have never seen so many SRP's before.

Well then send a note of thanks to arl16, jondrush and the other editors that have also been working in NE MD, it really doesn't take long for the MPs to clutter the map without constant vigilance. I've been leaving Baltimore for you guys and trying to make some inroads in DC, where the problems have piled up a bit.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users