Almost at destination, but Waze keeps routing me around

[jpborjas]

- While driving to work, at 3 or so miles out, I get an estimated 10 miles to go. I think this is related to the fact that I added a stop point to the trip, and that messes up the destination estimated time and distance.

IMG_0652.PNG (215.15 KiB) Viewed 230 times

- Also, at 3 miles away from my office, on a major highway, I only get 1 option when I hit Routes, actually the longest, when there are 2 other exits before the suggested one, and are clear of traffic, and shorter distance and time. When I took the first exit, Waze was trying to reroute me back to the highway to take the long way, and even after recalculating once or twice, and actually at just a few hundred yards of my destination, Waze was still suggesting to u-turn, and drive two miles around a mall, and then around my office building, when my destination was straight ahead.

IMG_0652.PNG (215.15 KiB) Viewed 230 times

[crazycaveman]

Have you checked the map editor to make sure everything looks good? If there are turns not allowed or disconnects between roads, that would explain this behavior. If everything looks good, it might have been fixed recently and the changes should be included in the next tile update (week - month away). Hopefully, this can be resolved easily!

If you want some tips for map editing, check the wiki.

[daknife]

Also with the suggested routes, is your app set to fastest route or shortest? If fastest, Waze's calculations may show that based on current information and historical traffic flow data, waiting until the third exit has the fastest average speed. Thus Waze chooses to remain on the freeway until that final exit option. Add in the possibility of a miss-configured turn restriction or three and Waze decides the route it's giving you is the fastest, though it may not be the shortest.