(→Fixes) |
(→Fixes) |
||
| Line 134: | Line 134: | ||
Volunteer responding. Waze just changed their text-to-speech voice - I've noticed this too, although it's been inconsistent. Unfortunately, we map editors have absolutely no control over Waze's voices, so can't be of any help. Sorry! | Volunteer responding. Waze just changed their text-to-speech voice - I've noticed this too, although it's been inconsistent. Unfortunately, we map editors have absolutely no control over Waze's voices, so can't be of any help. Sorry! | ||
Problems with the Waze app can often be fixed by turning your phone off, and then on again. | |||
As this isn't a problem with the map itself, I'm closing this report. | |||
Revision as of 16:39, 27 October 2015
Mudge42's Compendium of Mostly Useful Information
Technical Info
Priority of house number searches (info from a forum post by taco909 and also here)
In order of preference by the routing server/search engine:
- Waze Private Residential Place Points (Private Residential only, not "public")
- Waze House Number if and only if it has been "confirmed" (moved, even one pixel, by an editor in WME)
- Google database
The distinction between Private and non-private Waze places is important.
Non-Private Waze places search ONLY on the name (or alt-name) of the place. The address is simply there for the user to confirm
Private Residential Places search only on the address, EXCEPT that the person who added the place, and possibly his "friends" (unconfirmed) may search on the name.
Links I Like
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
General Error/Wrong Driving Direction:
Volunteer map editor responding. Waze did not provide enough information to determine the problem. Would you please describe what went wrong, and tell us your destination as you entered it into Waze? Thanks!
Turn Not Allowed:
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)? Thanks!
Missing Road:
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? Thanks!
Incorrect Junction:
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 are the street names at the junction, and what is wrong? Thanks!
Other:
Volunteer map editor responding. Waze doesn't provide enough information to determine the problem. Which address/location was incorrect?
Volunteer map editor 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? Thanks!
Volunteer map editor responding. The route trace provided by Waze indicates that your GPS signal was off and Waze did not know where you were. Does this explain the problem? Thanks!
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 2-3 days for the map to update. Delete any favorites or 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 2-3 days to update. Delete any favorites or saved searches you have in the Waze app for that address before trying again.
Waze was getting the location (map coordinates) of that address from Google Maps. Waze then directed you to the road closest to Google's location pin, which is <>. This has been fixed in Waze's map. Please allow 2-3 days for the map and routing to update, and delete any favorites or saved searches you have in the Waze app for that address before trying again.
I've made some changes to improve navigation to that address. Please allow 2-3 days for the map and routing to update, and then delete any favorites or saved searches you have in the Waze app for that address before trying again.
I've made some changes to improve directions at that intersection. Please allow 2-3 days for the map and routing to update. Thanks for reporting!
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 2-3 days for the map and routing to update.
The partial route trace shows a "turn right" instruction. There have been sporadic reports of Waze's text-to-speech giving the wrong turn direction (opposite of turn shown on screen). Nothing we map editors can do, I'm sorry to say.
I can't reproduce the problem, and get routings direct to the correct location of <>. Please try: 1) Delete any favorites or saved searches you have in the Waze app for that address and try again with a fresh search. 2) Tap the Wazer icon > Settings > Advanced > Data transfer > Refresh Map Of My Area. This forces a reload of maps to your device. 3) Clear Waze's app cache in your phone’s app manager. 4) As an absolute last resort (this will blow away ALL settings): reset the app by going to the navigation screen, typing ##@resetapp in the search field, and tapping search. Let us know if any of these help!
Undivided Highway:
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
Were you directed to take a turn through a barrier? 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
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.
Volunteer map editor responding. It appears that Waze was trying to route you via a detour. Waze may route detours to save a small amount of time. We map editors have no control over this. Sorry!
Thanks for the additional information. I can't find any map errors that would cause this. Waze is fairly averse to u-turns, and if the app believed that you were already pointed <direction> on <street> at the start, it could have routed you as described to get you back to <location> without a u-turn. Not anything that we map editors can fix, I'm sorry to say.
My guess is this: Waze tends to avoid u-turns, so if it thinks you are starting pointed away from the destination, it will route you into a loop instead of telling you to turn the other way. As it's not a problem with the map itself, nothing we map editors can fix. Sorry!
When you first request a route, Waze guesses at the direction you'll be travelling, and there's a good chance it will guess wrong. Waze also tends to avoid u-turns, and so will route you into a loop rather than telling you to turn around (some call this the "Waze 180"). As it's not a problem with the map itself, nothing we map editors can fix. Sorry!
Thanks for that additional information.The Waze Live Map currently estimates a <> 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!
By default, the Waze routing engine tries to find the fastest route to your destination based on average speeds and current conditions, even if the route is longer and the time difference is less than a minute. If you always want the shortest route, you can change the Navigation settings in the app (Settings > Navigation > Routing styles) from "Fastest" to "Shortest", and see if this works better for you. As this isn't an issue with the map itself, I'm closing this report, but please continue to report any map issues you encounter.
Volunteer responding. I can't find anything on the map to explain the route Waze gave you. Waze will sometimes route odd detours to save a few seconds, and map editors can't do anything to fix this. Sorry!
Volunteer responding. There are no map issues that would explain the route Waze gave you, but historical speed data suggests occasional long waits to turn at that intersection. Waze will sometimes route detours to save a few seconds. Unfortunately, there is nothing that map editing would fix. Sorry!
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 some time has passed. (And map editors can't really do anything unless we have advance notice of the closure.)
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 device or your satellite reception. Nothing that map editing would fix, I'm sorry to say, but please continue to report any map issues you encounter!
Volunteer map editor responding. I've reviewed the issue and did not find any map errors. It looks like Waze provided you with a valid route. By default (unless you've changed settings in the app), Waze will pick the fastest route - even if the difference vs. the shortest route is minimal.
Volunteer responding. Waze just changed their text-to-speech voice - I've noticed this too, although it's been inconsistent. Unfortunately, we map editors have absolutely no control over Waze's voices, so can't be of any help. Sorry!
Problems with the Waze app can often be fixed by turning your phone off, and then on again. As this isn't a problem with the map itself, I'm closing this report.