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: krankyd, Unholy

Re: Changes to Editor - New Automatic Detected Problem

Postby mdqueenz » Wed Dec 19, 2012 12:54 pm

Sure helps in detecting errors. Picks up on tons of stuff that is incorrect, yet drivers don't ever report it.

MD
Image
NYC / Long Island Based US Country Manager
Iphone 4S - IOS 6.0.1 - AT&T
mdqueenz
 
Posts: 95
Joined: Tue Dec 01, 2009 1:53 pm
Has thanked: 0 time
Been thanked: 2 times

Re: Changes to Editor - New Automatic Detected Problem

Postby mdqueenz » Wed Dec 19, 2012 1:25 pm

What does the number in the bubble represent (in the driver's actual route)? Is it the number of times that instruction has been ignored?
Image
NYC / Long Island Based US Country Manager
Iphone 4S - IOS 6.0.1 - AT&T
mdqueenz
 
Posts: 95
Joined: Tue Dec 01, 2009 1:53 pm
Has thanked: 0 time
Been thanked: 2 times

Re: Changes to Editor - New Automatic Detected Problem

Postby mdqueenz » Wed Dec 19, 2012 2:47 pm

Yes, a lot of the errors have long been corrected, however i have tons where the problem is still existant.

Hopefully once we get past this backlog, the generating of these errors will be much more up to date.

MD
Image
NYC / Long Island Based US Country Manager
Iphone 4S - IOS 6.0.1 - AT&T
mdqueenz
 
Posts: 95
Joined: Tue Dec 01, 2009 1:53 pm
Has thanked: 0 time
Been thanked: 2 times

Re: Changes to Editor - New Automatic Detected Problem

Postby Mike-1323 » Wed Dec 19, 2012 6:44 pm

And how to handle when the users ignore the directions to make ridiculous u-turns and the problem is generated? I'm not even taking about the ones where it may actually be faster to take the u-turn route, but the ones that make no sense. Like when the routes that turn right into a cul-de-sac, u-turn and then turn right out of the cul-de-sac traveling in the same direction as going straight through the intersection. No stop light or turn restrictions causing it either. Is that a solved (the maps correct) or not identified (don't know why the routing server screwed up)?

Image Image
AM - Northern Virginia - Fairfax/Ft. Belvoir
CM - USA
Android 2.2.1, LG Optimus V
Mike-1323
Beta tester
Beta tester
 
Posts: 928
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 139 times

Re: Changes to Editor - New Automatic Detected Problem

Postby Mike-1323 » Tue Jan 15, 2013 10:05 pm

kentsmith9 wrote:Here is another with a similar config. Both this one and my last post had no problem on the straight through route. The route proposed is a single dead end street with no city or road name. It was edited by Staff on January 1 this year. Not the road next to it is untouched and still shows Portola Valley. Note sure why the script did not fix that road as well.


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.

Image Image
AM - Northern Virginia - Fairfax/Ft. Belvoir
CM - USA
Android 2.2.1, LG Optimus V
Mike-1323
Beta tester
Beta tester
 
Posts: 928
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 139 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:

Image Image
AM - Northern Virginia - Fairfax/Ft. Belvoir
CM - USA
Android 2.2.1, LG Optimus V
Mike-1323
Beta tester
Beta tester
 
Posts: 928
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 139 times

Re: Changes to Editor - New Automatic Detected Problem

Postby Nel101 » Wed Dec 19, 2012 3:53 pm

This new detection system is great! Solved at least a dozen in my area already this morning where otherwise it wasn't reported by any user. This should greatly improve the map overall in the next couple of weeks. There were several that was based on old data but no matter, I would suspect we should see less of those as time goes on.
Image

Area Manger: Central New Jersey
Nel101
 
Posts: 54
Joined: Sat Jun 16, 2012 1:43 am
Location: The Garden State
Has thanked: 10 times
Been thanked: 1 time

Re: Changes to Editor - New Automatic Detected Problem

Postby nnote » Wed Dec 19, 2012 3:20 pm

POINTS!! Hahaha! I like it, seems to catch alot of bad turn restrictions. Also finding waze tries to route people down uneeded side roads alot...
L6 Area Manager Arizona, : USA L6 CM, USA
Image
G+ Waze Arizona
nnote
Waze Mentor
Waze Mentor
 
Posts: 260
Joined: Sun Jun 19, 2011 6:25 pm
Location: Arizona USA
Has thanked: 8 times
Been thanked: 35 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..
L6 Area Manager Arizona, : USA L6 CM, USA
Image
G+ Waze Arizona
nnote
Waze Mentor
Waze Mentor
 
Posts: 260
Joined: Sun Jun 19, 2011 6:25 pm
Location: Arizona USA
Has thanked: 8 times
Been thanked: 35 times

Re: Changes to Editor - New Automatic Detected Problem

Postby outtolunch » Tue Jan 08, 2013 3:18 pm

[quote="shawndoc"]They didn't start showing up for me until I cleared my cache.[/quote]

How do you clear the cache? I was working on an area with quite a few problems, but they just disappeared when I fixed one of them.
outtolunch
 
Posts: 17
Joined: Mon Feb 13, 2012 1:53 pm
Location: North Carolina
Has thanked: 10 times
Been thanked: 0 time

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users

cron