Changes

From Wazeopedia

User:DwarfLord/UR

6,773 bytes added, 3 years ago
URs with no conversation yet
[[Category:Sample responses]]
:''This is a collection of boilerplate responses for most typically encountered UR issues. Permission is gladly given to link to this page and to adapt and use these responses worldwide. All are welcome to create new boilerplate response collections using ideas and text found here. Attribution where feasible is always appreciated, but not necessary. Please, however, do NOT edit this page directly. Instead send me a PM. If something here is wrong I want to {{nowrap|know. --DwarfLord}}'' == Generic, highly automated responses for UR-overwhelmed areas == === URs with no conversation yet === This is an automated response to alert you that your report has been received in the volunteer map database. Depending on many factors, it can take some time for volunteer editors to process your report. Please consider adding details to your report by responding to this message using the app, or by using the Waze editor web site linked in the e-mail version of this message (but do not reply to the e-mail, as e-mails do not work with the reporting system). If your issue involved reaching a specific address or place, please say what it was, as Waze does not give the volunteers that information. Anything you can offer will help the volunteer editors investigate the map issue more quickly and effectively. (Open to any editor) ''Comment: This suggested automated response addresses four key points: (1) allows editors to open the conversation quickly on an automated or near automated basis without claiming any inspection of the UR; (2) informs the recipient that it's an automated response, so if the report languishes after this response the recipient does not feel that a human being has let them down; (3) prepares the reporter that it might take awhile; and (4) gives the reporter a means to improve the chances of a speedy and positive outcome.''
== 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)
 
=== Description is generic rant with no details ===
 
Volunteer responding to your concern. Waze is definitely not perfect, and never will be, but I've been volunteering my time to make it better in this area. If you would be willing to provide some details about your experience maybe I can help, or at least tell you a bit about how Waze works (or doesn't work). What exactly went wrong? Where did you start, where were you going, and what app behavior would have been better? (Open to any editor)
== Likely cause identified, give reporter opportunity to clarify ==
 
=== Google position wrong ===
 
Volunteer responding to your report of routing to a nearby street instead of to your destination. This is, sadly, a common problem. Waze relies on Google to get a destination position and then does whatever it takes to get you as close as possible to that position. But, Google's position markers are often placed closer to undesired streets than to the correct access street. So, probably the Google position for your destination is the problem. The good news is that we can usually override the Google position, if we know what to fix. Can you tell us the destination address? Please respond using the Waze app, emails don't work with the reporting system. (Open to any editor)
=== 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)
 
=== Mistook earlier turn for later turn ===
 
Volunteer responding to your report of being routed through an illegal turn. It looks like Waze intended for you to take the turn *just before* the one you thought it meant. This is a common experience when driving in close quarters: Waze may suggest turning within parking lots close to the exits, for example, or on smaller, less noticeable roads close to major intersections. Sadly we volunteers can't do much about this! You can get the most out of the Waze app by (1) placing the Waze display where you can see it easily, and (2) using a standard voice that speaks the street names, rather than a celebrity or parody voice. If you are sure this wasn't the problem, please respond using the Waze app (emails don't work with the reporting system) and provide details! Otherwise we'll close out this report in a few days. Cheers! (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)
 
=== Failed route, user rants at Waze regarding road closure ===
 
Dear reporter, I'm a volunteer responding to your report. Sorry for your experience. Please note that Waze employees never see "Map Issue" reports. The reports simply appear on the volunteer editing screen. The idea is that volunteers working on their own time will see them and will do something. Unfortunately we have few volunteers watching this area, meanwhile the number of "map issue" reports keeps increasing. Sadly, most reports these days end up unactionable, but they still take volunteer effort to handle. As a result, even the few volunteers we have sometimes lose heart. With the map covered in unactionable but labor-intensive reports, important issues can go unnoticed. All I can suggest is that you make use of the Report->Closure feature. This feature allows you to mark closures in real time, unlike Report->Map Issue. The good news is, Waze developers are aware of the map-issue overload problem and are planning to improve the interface so that important map issues may be detected sooner. Cheers!
=== 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 the wrong way, but only on the OTHER side. The side Waze wanted to take 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 . But we definitely want the map to be correct! Did you see any other signs prohibiting the turn, such as "No TurnTurns" 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 may have asked Waze for a route while you were located within a complexarea, dense areawith multiple, closely-spaced lanes dedicated to different directions. GPS position information isn't perfect, so when you request a route from such an area -- for example, while waiting in traffic at a place where multiple roads, ramps, and/complex intersection or turn lanes are in close proximity, within a multilevel viaduct -- Waze can guess your starting road or lane wrong. As a result Waze may believe you are committed to a different direction than you actually are, and offer a nonsensical you an unusable route. We'll see if we can simplify this location things here to make the this 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 assume all is well and 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 assume all is well and 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 comment on the map issue you reported . We will assume all is well 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 (wait for map update) ===
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 Fixed Places and/or House Numbers (update already in effect) === 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 bad news is, your Waze app has remembered the old, wrong position from your last drive and will not automatically update it. Please 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! === Slightly incorrect position === Volunteer responding to your map-issue report of an incorrect position. The map looks OK here, so apparently this was an issue with the Waze app, not the map. We volunteer map editors can't modify the app's positioning system, but we know it isn't always perfect among dense roadways or in areas of poor GPS reception such as valleys, forests, and urban canyons. Position accuracy can improve a lot when you are moving, and especially when you are following Waze's route. You can also ensure your mobile device has a clear view of the sky to get the best GPS position. That's the best we can offer -- sorry not to be more help! === Bad route due to 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 Routed into traffic (calm report) === Volunteer responding to your report of being routed into traffic. Sadly, we volunteers don't have access to the traffic history and have no way to analyze what happened. Sometimes Waze may not know of fresh accidents or bogus slowdowns because it hasn't yet received enough data from other Wazers. Or, there may be a temporary closure on alternate routes that forced Waze to route you into traffic. Finally there is the possibility that the traffic is just really bad everywhere and there is no faster route. Without access to the traffic history all we can do is speculate. We hate traffic as much as you do and I wish we could be more help! === Routed into traffic (angry rant) === Volunteer responding to your report that Waze took you into very slow, heavy traffic. I wish I knew what to tell you. I get mad at Waze too when it routes me into heavy traffic indications/routing , but when I think about it later, the alternatives were probably no better at that time on that day. In any event we poor volunteer editors can't do anything about the app functionality, we can only make sure the map itself is correct and then hope Waze does the rest. Usually it does (otherwise I wouldn't volunteer!). But when everything nearby is gridlocked I don't know how well any app can work. Sorry for your experience, and sorry not to be more help! === Closed for occasional event ===
Volunteer responding. Authorities briefly close roads in this area during occasional events. These events do not repeat on a daily or weekly schedule, so each one would need to be programmed manually into Waze. Unfortunately we volunteers don't have the resources to do that. But you can help! You can use the Report->Closure feature in the app. It takes effect immediately, and the more people use it, the greater confidence Waze assigns the closure. This will work much better than submitting a "Map Issue" report like this one, since Map-Issue reports depend completely on volunteers for processing and can take some time. Cheers! === Stale or bogus traffic indications === Volunteer responding to your report of a map issue involving wrong traffic indications. We Sadly, we volunteers don't have access to the traffic history and have no way to figure out analyze what happened here that led to your report. Typical causes include: (1) Sometimes Waze may not have data on fresh accidents or slowdowns from other Wazers and may route you into them simply because can say there's traffic when it doesn't know yet; (2) after Waze has detected traffics still remembering an old situation, or if it can remember it for awhile, sometimes well after the situation changes; (3) 's been confused by someone improperly using Waze may route you into traffic to avoid on a temporary closure elsewhere that was flagged by other Wazers; and (4) sometimes slow-moving Wazers vehicle like a bicycle. And, sometimes Waze can confuse Waze into incorrectly detecting heavy say there isn't traffic (this is why one should never run Waze while walking when it hasn't yet received enough data on fresh accidents or biking along roads)slowdowns from other Wazers. 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 make a judgement as to what level of risk different drivers will accept. The only thing it can do is measure how hard it may be long a maneuver takes to change lanes complete at any given timedifferent times of day and factor that into its suggested route. We could simply prohibit maneuvers that may be difficult in trafficthis maneuver, but then other drivers would complain when Waze avoided those routes at other timesit, especially when traffic is light. We sure hate this when it happens to usdon't like dangerous maneuvers any more than you do, and wish we could do something about it, but sadly there's no good solution to this problemwith the tools we have. CheersSorry not to be more help!
=== 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 upor a temporary closure has ended, 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!
 
=== Pronunciation ===
 
Volunteer responding to your report of poor pronunciation by Waze text-to-speech (TTS). Unfortunately even the most senior volunteers have little influence on the TTS system, and none of us can alter how any one street name is pronounced. I understand the frustration and I sympathize. Sorry not to be more help. 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!
 
=== Possible routing bug ===
 
Volunteer responding. The snippet of data Waze provided us along with your report does suggest inexplicable routing. I've checked everywhere I can think of and unfortunately I can't find anything wrong with the map. But, Waze is currently working on an issue with speed detection for different turns out of an intersection. In rare instances this issue can lead Waze to suggest non-ideal routes, usually involving one or more U-turns or loops. We volunteers have no way to know if your experience resulted from this issue, but as there's nothing I can find on the map I'll close this report as "not identified". I sure wish I could be more help but that's what's going on.
 
=== We can't do U-turns ===
 
(As of app version 3.9.4 U-turns are supported. The "we can't do U-turns" response is no longer appropriate.)
=== We can't do "continue straight" (usually a followup response) ===
1,097
edits