User:Mudge42

Mudge42's Links I Like

DwarfLord's Boilerplate UR Responses

Community Plugins, Extensions and Tools

USA Road Functional classification

MA Road Inventory

Massachusetts Information

Road closures

Editing manual

The infamous route 9 thread: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

And my own boilerplate:

No response on UR

As there's been no response for some time, I'm closing this one. If there is still a problem, please submit a new map issue report.

There's been no activity on this report for some time, so I'm taking the liberty of closing it. If there is still a problem, please submit a new map issue report.

More info needed

Volunteer map editor responding. You reported a "general error". Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what was your route, and what was the error?

Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please let us know what went wrong? Would you tell us your destination as you entered it into Waze? Thanks!

Volunteer map editor responding. You reported a "turn not allowed" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - which turn wasn't allowed? Was this a temporary restriction (due to construction)?

Volunteer map editor responding. You reported a "wrong driving direction" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what were your start and end points, and where was the routing wrong?

Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please let us know what went wrong with the route Waze gave you? Would you tell us your destination as you entered it into Waze? Thanks!

Volunteer map editor responding. You reported a "missing road" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what road is missing?

Volunteer map editor responding. You reported an "incorrect junction" issue. Waze didn't provide enough information to determine the problem, so please provide as much detail as possible - what is wrong with the junction?

Volunteer map editor responding. Waze doesn't provide enough information to determine the problem. Which address/location was incorrect?

Volunteer responding. The Waze app doesn't necessarily display overpasses correctly, but this should not affect routing. Was this the issue, or is there another problem?

Fixes

The problem is that Waze was getting the location of that address from Google Maps, where it is wrong. I've added the address to Waze; it will take 1-2 days for the map to update. Delete any saved searches you have in the Waze app for that address before trying again.

I have moved the navigation point for that address to the correct spot. It normally takes Waze's map and routing 1-2 days to update. Delete any favorites or saved searches you have in the Waze app for that address before trying again.

OK, I can see the problem. Waze is getting the location (map coordinates) of that place from Google Maps. Waze then directs you to the road closest to Google's location pin, which is <>. To fix this, I've added a parking lot road in front of the building, so Waze will route using that. Please allow 1-2 days for the map and routing to update.

(Route 9) There's a known problem with the way Waze treats roads such as route 9 in that area, where there is a barrier but the road doesn't fit Waze's definition of a divided highway. In short, you'll be told to take turns through the barrier. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

It's a common problem with the way Waze treats roads where there is a barrier, but the road doesn't fit Waze's definition of a divided highway. You will often be directed to the wrong side. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

Unfortunately, it's an ongoing problem with the way Waze treats roads where there is a barrier, but the road doesn't fit Waze's definition of a divided highway. You will often be directed to take turns through the barrier. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

Were you directed to take a turn through a barrier? Unfortunately, it's an ongoing problem with the way Waze treats route 9. You can read more about the issue here, if interested: https://www.waze.com/forum/viewtopic.php?f=618&t=89218

Thanks for that detailed information. Unfortunately, the Live Map is providing only the more direct route on (fill in) today. This looks like one of those cases where the Waze routing engine, possibly due to reported traffic conditions and average speeds, decided to send you the roundabout way. Nothing that map editing would fix, I'm sorry to say.

Thanks for that additional information.The Waze Live Map currently estimates a 3 minute difference between the more direct route and the roundabout route suggested by the app. This is one of those cases where the Waze routing engine, possibly due to reported traffic conditions and average speeds on the direct route at the time, decided that the roundabout way would be faster. Nothing that map editing would fix, I'm sorry to say, but please continue to report any map issues you encounter!

For temporary road closures, use the "Closure" button in the Waze app. That will provide a more timely alert to other drivers. A "map issue" report may not be looked at by a map editor until a few days have passed. (And map editors can't really do anything unless the closure will be a month or more.)

Judging by your GPS trace, you lost signal and Waze really didn't know where you were. Unfortunately, that's a problem with the GPS in your phone and not something that can be fixed by editing the map.