→URs with no conversation yet
:''This is a collection of boilerplate responses for
most typically encountered UR issues .''
== Update Requests with no immediately obvious issue ==
Volunteer responding to your "turn not allowed" map-issue report. Waze gives us volunteers very little to go on. What turn was not allowed? At what intersection? Please respond using the Waze app, emails don't work with the reporting system. (Open to any editor)
== Likely cause identified, give reporter opportunity to clarify ==
=== The "Waze 180" ===
Volunteer responding to your report. The little bit of data Waze gave us suggests that it was trying to take you back the way you came, but you continued forward. This can happen when Waze (1) doesn't know about a legal turn or U-turn; (2) has a badly incorrect position for your destination; (3) was given an erroneous destination; or, (4) is still trying to take you to an old destination. Unfortunately we don't know what your destination was! Where did you ask Waze to take you? Were you expecting Waze to offer you a turn or U-turn somewhere? If so, where? Please respond using the app, emails don't work with the reporting system. (Open to any editor)
=== Bogus missing road, exit, and bridge overpass reports ===
Volunteer responding to your report of a road closure. Do you know how long the closure will last? If it is only for a few days or less, we volunteer map editors can't help. It takes at least that long for our edits to make it to handheld devices! The best way to report short-term road closures is with the Report->Closure feature in the Waze app (you used Report->Map Issue to file this report). However, if this is a long-term closure or time-based or vehicle-type-based restriction, please respond using the app (emails don't work with the reporting system) and let us know as much detail as you can. Cheers! (Open to any editor)
=== Unexplained alternate route, surely traffic-related ===
=== Confused by "One Way" sign on ''opposite'' side from turn ===
Volunteer responding to your report regarding a prohibited turn. Unfortunately the "One Way" signage here is confusing
-- the street you were asked to turn on is indeed one way, but only on the OTHER side. The side Waze wanted you to go appears to be two-way and legal to turn into. Because of the confusing signage we often see reports like this , but we definitely want the map to be correct! Did you see any other signs prohibiting the turn, such as "No Turn" or "Do Not Enter" signs? If you are certain the turn is prohibited, please respond using the app (emails don't work with the reporting system) and let us know as much detail as you can. Otherwise we'll close this report in a few days. Cheers! (Open to any editor)
=== Construction zones (followup response) ===
=== Snapped to wrong road/lane when asking for route in dense area ===
Volunteer responding to your report of an unexpected or impossible route. It appears that you asked Waze for a route while you were located within a complex,
dense area. When you ask for a route, Waze estimates your current location based on your GPS position . But GPS isn't perfect . When you request a route while located in a dense area, Waze can guess your road or lane wrong. As a result Waze may offer a nonsensical route. We'll see if we can simplify this location to make the effect less likely for future Wazers, but generally there's little we can do. The good news is that, if you continue driving, Waze will recalculate as always once it realizes where you really are. Sorry not to be more help ! === Late June 2015 routing-server bug for timed turn/segment restrictions === Volunteer responding to your report of being routed through a turn or road prohibited by time restrictions. The time restriction for this location has actually been in the Waze map for some time. Unfortunately, around 26 June 2015, a bug seems to have appeared that causes Waze to disregard some timed turn and road restrictions between Thursday evening and Saturday morning. Our tests indicate that the bug was fixed as of July 24, so all should be well now. Sorry for your experience!
== Lapsed conversations with other editor(s) ==
=== No response, closure imminent ===
Hi, we haven't heard back regarding our last comment on the map issue you reported. In a few days we'll close the report. Cheers!
=== No response to another editor, closure imminent ===
Hi, we haven't heard back regarding our last comment on the map issue you reported. In a few days we'll close the report. Cheers! (To the editor who initially responded: please feel welcome to close this report, or say something in a few days if it should be left open.)
=== No response, closing now (unnecessary if imminent-closure already sent) ===
Hi, we haven't heard back regarding our last
question on the map issue you reported and will close this report. Please feel welcome to report problems with the map in the future. Cheers!
=== Fixed Roads ===
Volunteer responding to your report of a map issue. Thanks to your report we've found and fixed a problem with the map. The fix should reach handheld devices within a week, but on rare occasions it can take longer. Cheers!
=== Fixed Places and/or House Numbers ===
Volunteer responding to your report of a map issue. I have good news and bad news. The good news is that we found your destination was incorrectly located on the Waze map and we have fixed it! The fix should be available within a week, but on rare occasions it can take longer. The bad news is, your Waze app has remembered the old, wrong position from your last drive and will not automatically update it. Please wait at least a few days, preferably a week, then remove all instances of this destination from your recents, favorites, home, and/or work lists. That will force the app to obtain the new position the next time you navigate there. Cheers!
(NOTE TO EDITORS, DO NOT INCLUDE IN RESPONSE: Remember when changing House Numbers to make some kind of road edit close by to trigger a tile update. It could be as simple as selecting a segment drag handle to create a new geometry node, then deleting the node and saving.)
Bogus GPS ===
Volunteer responding to your report of a map issue. It looks like your GPS position information was awfully inaccurate. Bad GPS can cause all sorts of problems. For example, Waze may think you are on some other road and give you bogus directions to get you back to the road you're already on. There's nothing we volunteer map editors can do about this, but in the future, please try ensuring that your handheld device has as clear a view of the sky as possible so it will get the most accuracy out of the GPS satellite signals. Even this may not be enough in deep valleys, thick forests, or urban canyons, but it will help. Cheers!
Volunteer responding to your report of a map issue. It looks like you departed from Waze's recommended route and instead followed a path that happened to parallel the recommended route. Under these circumstances, Waze can't be sure if you really left its route or if your GPS position data are just a little off. GPS data are never perfect, so Waze assumed the GPS was to blame and continued to give you driving instructions for its original route; it's no wonder the instructions didn't make sense. Sorry to say there's nothing we volunteer map editors can do about this, I wish we could be more help. Cheers!
Stale or bogus traffic indications/routing ===
Volunteer responding to your report of
a map issue involving wrong traffic indications. We volunteers don't have access to the traffic history and have no way to figure out what happened here that led to your report. Typical causes include: (1) Waze may not have data on fresh accidents or slowdowns from other Wazers and may route you into them simply because it doesn' t know yet; (2) after Waze has detected traffic, it can remember it for awhile, sometimes well after the situation changes; (3) Waze may route you into traffic to avoid a temporary closure elsewhere that was flagged by other Wazers; and (4) sometimes slow-moving Wazers can confuse Waze into incorrectly detecting heavy traffic (this is why one should never run Waze while walking or biking along roads). Without access to the traffic history all we can do is speculate. I wish we could be more help!
=== Waited forever to make Waze's recommended maneuver (usually unprotected left turns) ===
=== Legal route but dangerous or impossible in heavy traffic ===
Volunteer responding. Sorry to hear of your experience! The volunteer editing community has wrestled with this issue many times, and every time we conclude that the Waze map must support legally-possible routes, even if some are dangerous or impossible in heavy traffic. As drivers ourselves we know how frustrating this is. But Waze, like other navigation apps, can't
monitor or account for how hard it may be to change lanes at any given time. We could prohibit maneuvers that may be difficult in traffic, but drivers would complain when Waze avoided those routes at other times. We sure hate this when it happens to us, and wish we could do something about it, but there's no good solution to this problem. Cheers!
=== Verified temporary road closure ===
=== Unexpected route (small scale / detour) ===
Volunteer responding. I can't find anything in the map to explain the unexpected route Waze gave you. Traffic, a daily pattern of traffic, a temporary road closure, a bicyclist or very slow vehicle inappropriately using Waze, or just a slow stoplight that routinely backs up cars can all cause Waze to suggest surprising alternatives. Sometimes Waze may recommend an unexpected route even after traffic has cleared up, because it doesn't know yet. Also, if Waze hasn't yet collected enough data in the area, it may overestimate the speeds of side roads, turns, and U-turns. It definitely does help for drivers to try Waze's suggestions, as it gives Waze more speed data on those alternate routes. At any rate we'll close this report as the map itself appears to be OK. Cheers!
=== Unexpected route (large scale) ===
Volunteer responding. Waze is indeed aware of the alternate route to bypass traffic. It routed you on a more typical path at that time because it thought, at that moment, that it would be faster to go that way. We volunteer map editors can't do anything about Waze's traffic detection and routing algorithms, but we have checked that the map itself does look OK. Cheers!
=== No hablo muy bien el Español ===
Volunteer responding. Confusingly, the "private road" Waze type does not mean it is a private road. It is just a flag that Waze should prohibit thru traffic. This is indeed a public road, but legally-valid street signs mark it NO THRU TRAFFIC. For better or worse Waze, like most folks, "can't fight city hall" and must respect these signs. The good news is that, if you choose to drive on this street, Waze will automatically recalculate your route without complaint. Cheers!
=== We can't do "continue straight" (usually a followup response) ===