The routing went bad a few weeks ago, taking travelers through odd routes in order to avoid US 29 and Linton Hall Road. I see lots of user problems reported for that stretch. This is a construction zone but the path/detour has been the same for the past year or so. I looked at the maps via the editor and believe I’ve fixed most of the errors (missing segments, some turn arrows were incorrectly red/blocked, one instance of routing through construction zones, a couple of instances where the road level was incorrectly set to 2).
However, I just tried to have my route calculated through that part of US 29 and I’m still being rerouted through alternate routes that are much longer. Is there anyway to trace why things are being redirected. Nothing additional is obvious to me at this point. There is also one section of road where it has been named “Lee Hwee Hwy” whereas the rest of the road is “Lee Hwy.” That section is also locked by a level 5 editor and it had been routing Hwy 29 traffic through a blocked road. Is there anything that I’m missing in troubleshooting this stretch? For what it is worth, the aerial image is old and doesn’t show the temporary roads.
It can take several days before changes made in the editor get pushed out to the clients.
Watch http://status.waze.com/ to see when that happens.
You can open the area in livemap with the livemap navigation extension installed and navigate from one side of the area to the other and see what directions are given.
You can then examine the area ‘avoided’ to find prohibited turns, wrong street names, reverse connections, u-turn connections, etc. and fix them. You can use the color highlight extension to help you detect some of these problems. http://userscripts.org/scripts/show/141050.
caveat: live map uses the clients database so changes you make in the editor will NOT immediately take effect there.
Sounds like problems to me
the GPS tracks can help but your ‘on the ground experience’ is going to be the best source of information.