Directions Changed (for the worse)

by **AndyPoms** » Fri Jun 01, 2012 11:19 pm

Since this just cropped up, it sounds like someone edited something along your preferred route in the map editor & it was part of the map update that was pushed out early last week.

Take a look at the map editor (and read the Wiki) to see if you can find the problem. A good indicator to drive your preferred route and when the app stops giving you wrong directions and puts you back on your preferred path. The error is usually close to that point.

(This is a slightly modified copy and paste of my post in this thread, which you also may find useful: http://www.waze.com/forum/viewtopic.php?f=144&t=19628)

by **AndyPoms** » Mon Jun 04, 2012 5:34 pm

bigbear3764 wrote:Map update go thru this am?

Live map is dated 5/27/2012, so I'm going to guess yes... But it wasn't like that a few hours ago...

by **bigbear3764** » Mon Jun 04, 2012 5:12 pm

Map update go thru this am?

Sent from my iPhone using Tapatalk

by **cfountain72** » Fri Jun 01, 2012 10:58 pm

I use Waze everyday to drive from Tampa to my job in St. Petersburg. I go S on I-275 to St Pete, which is always a speed limit+ ride once I get across the bridge. However, for the past week or so, Waze tells me to exit I-275 S at 54th Street near St. Petersburg, go down a few blocks and then get back on I-275 on at 22nd St. I ignored it the first time, thinking it might be a temporary issue, and continued on I-275, driving at 70MPH. However, it has been suggesting this exit every day since, even though there are no accidents or hazards to justify getting off the interstate. Can you look into this? You can replicate it yourself by requesting directions from Tampa to St Petersburg on waze.com or in the iPhone app. The route worked worked fine for the better part of a year, but for the past two weeks, it's been giving me this errant suggestion.

Thanks in advance,
Chris

ps. Otherwise, Waze pretty much rocks!

by **cfountain72** » Mon Jun 04, 2012 3:48 pm

UPDATE: Driving to work today, I noticed that, for the first time in weeks, I wasn't redirected off the Interstate. I looked at the map myself in the effected area, but didn't see anything that would cause the error. In any case, thanks to whomever fixed it. Peace be with you.