Resolving Incorrect Directions

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

Resolving Incorrect Directions

Postby imfrog2002 » Sat Jan 05, 2013 5:40 pm

Hey everyone, I'm having some issues with the maps in my area, and I don't know how to fix them.

https://www.waze.com/editor/?lon=-111.5 ... TTTTTTTTFT

That seems to be a problem area. It's always routing people to take Germann instead of Ironwood, when Germann/Schnepf are 35/45, and Ironwood/Ocotillo are 50/35. Same number of stop signs on each route, no other differences I can see while driving them. Is there any way to change a suggested route? I've also had issues here:

https://www.waze.com/editor/?lon=-111.5 ... TTTTTTTTFT

Where I'm heading to Gilbert, and the fastest way is to take Ocotillo to Rittenhouse and up, not Ironwood to the 60 (which is 10 miles out of the way...) then right back down on the 202. Any ideas for fixing majorly messed up routing directions like this? (I've tried just driving them. It just keeps giving me the same routes for 3 months now. I just keep ignoring the prompts, but it still doesn't get through to Waze that I don't want that route...)
imfrog2002
 
Posts: 13
Joined: Tue Aug 18, 2009 10:11 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Resolving Incorrect Directions

Postby imfrog2002 » Sat Jan 05, 2013 11:50 pm

Thank you! That should resolve the issue on Ironwood. For the other issue, let's say you're coming from this intersection:

https://www.waze.com/editor/?lon=-111.5 ... TTTFTTTTFT

Heading to this mall:

https://www.waze.com/editor/?lon=-111.7 ... TTTFTTTTFT

At the following intersection:

https://www.waze.com/editor/?lon=-111.5 ... TTTFTTTTFT

It routes you North on Ironwood, up to the 60, then back down on the 202. (Estimated Time: 38 minutes)

The fastest (and shortest, by 12 miles) way is to take Ocotillo to Rittenhouse, then up to Power, then to Pecos to SanTan Village Parkway. (Confusing, but true...) Estimated time is only 35 minutes. While there isn't a huge difference in time, the distance can really guzzle gas. Is it due to the fact that it's primary roads instead of regular streets?
imfrog2002
 
Posts: 13
Joined: Tue Aug 18, 2009 10:11 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Resolving Incorrect Directions

Postby shawndoc » Sat Jan 05, 2013 9:01 pm

It would be helpful if you could give us a location to/from to route to on the Live map, so we can see exactly what Waze is doing so we can try to nail down the problem.

However, just a quick glance shows that at this intersection of Ironwood and Pima, South Bound Ironwood has turn restrictions preventing Waze from routing anyone through the junction.
https://www.waze.com/editor/?zoom=6&lat=33.2634&lon=-111.56355&layers=BFTFFTTTFTTFTTTTFTTTTFT&segments=66048882

This will mess up any routes that need to go through that junction, forcing Waze to find another way.
California, USA - OC/LA/SB/Riverside L5 Country Editor
shawndoc
Beta tester
Beta tester
 
Posts: 1490
Joined: Mon Apr 16, 2012 7:44 am
Location: Californialand, USA
Has thanked: 3 times
Been thanked: 249 times

Re: Resolving Incorrect Directions

Postby shawndoc » Sun Jan 06, 2013 2:12 am

I've got a couple guesses, and maybe one of the Champs will chime in with a better explanation.

For reference I searched on Google for the directions from those to locations, and the route Waze uses was one of the 3 options that Google gave, and Google gave all 3 about the same amount of travel time.

So it may be, with the speed data that Waze has, it feels taking the highways is the quicker route.

Do you have "shortest route" selected in the client under navigation? Not sure how well that works, I know I've seen UR's complaining that Waze isn't actually giving shortest route directions.

Another issue may be the distance between those locations. Waze prefers highways for long distance travel, so since all those roads are streets or primary streets, Waze might be ignoring them.

It also might be a good idea to go over the route manually in the editor, and see if you can find any disconnections or improper turn restrictions which might be keeping Waze from routing over them.
California, USA - OC/LA/SB/Riverside L5 Country Editor
shawndoc
Beta tester
Beta tester
 
Posts: 1490
Joined: Mon Apr 16, 2012 7:44 am
Location: Californialand, USA
Has thanked: 3 times
Been thanked: 249 times


Return to Waze Map Editor

Who is online

Users browsing this forum: Google Feedfetcher, iainhouse