Difference between revisions of "User:DwarfLord/UR"

From Wazeopedia
(General Error with no descriptive text)
(Update Requests with common solutions)
Line 19: Line 19:
 
=== Fixed ===
 
=== Fixed ===
  
Volunteer responding to your map-issue report.  Thanks to your report we've found and fixed a problem with the map.  The fix should reach handheld devices within a week or so.  Cheers!
+
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 or so.  Cheers!
  
 
=== The "Waze 180" ===
 
=== The "Waze 180" ===
  
Volunteer responding to your map-issue report.  When you ask for a route immediately after waking up Waze, it has to guess what direction you are pointed.  If it guesses wrong, it may give you an awkward route to avoid any illegal U-turns (I call this the "Waze 180").  When Waze offers you a route that starts off the wrong way, please drive a little in the direction you are pointed and then ask for the route again.  This gives Waze a chance to know which way you are pointed and offer you a more suitable route.  If you are sure this was not the problem, please respond, otherwise we'll close out this report in a few days.  Cheers!
+
Volunteer responding to your report of a map issue.  When you ask for a route immediately after waking up Waze, it has to guess what direction you are pointed.  If it guesses wrong, it may give you an awkward route to avoid any illegal U-turns (I call this the "Waze 180").  When Waze offers you a route that starts off the wrong way, please drive a little in the direction you are pointed and then ask for the route again.  This gives Waze a chance to know which way you are pointed and offer you a more suitable route.  If you are sure this was not the problem, please respond, otherwise we'll close out this report in a few days.  Cheers!
  
 
=== Google fu ===
 
=== Google fu ===
  
Volunteer responding to your map-issue report.  The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google).  We have asked Google to fix its database but we have no control over how fast Google will respond.  It is usually days, but it can be weeks or even months.  We'll leave this report open in the meantime.  Cheers!
+
Volunteer responding to your report of a map issue.  The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google).  We have asked Google to fix its database but we have no control over how fast Google will respond.  It is usually days, but it can be weeks or even months.  We'll leave this report open in the meantime.  Cheers!
  
 
=== Bogus GPS ===
 
=== Bogus GPS ===
  
Volunteer responding to your map-issue report.  It looks like your GPS position information was awfully inaccurate.  Bad GPS position data can cause all sorts of problems.  Waze may think you are on some other road and give you bogus directions to get you back to the road you're really 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.  Cheers!
+
Volunteer responding to your report of a map issue.  It looks like your GPS position information was awfully inaccurate.  Bad GPS position data can cause all sorts of problems.  Waze may think you are on some other road and give you bogus directions to get you back to the road you're really 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.  Cheers!
 +
 
 +
=== Stale or bogus heavy-traffic indications/routing ===
 +
 
 +
Volunteer responding to your report of a map issue involving wrong traffic indications.  We volunteer map editors can't do anything about Waze's traffic reporting, but I can explain what may have happened.  When Waze thinks it has detected a traffic situation it can remember it for awhile, sometimes long after the situation changes.  Also, slow-moving Wazers can confuse Waze into incorrectly declaring heavy traffic (this is why one should never run Waze while walking or biking along roads).  We'll close out this report.  Cheers!

Revision as of 19:23, 14 June 2014

This is a collection of boilerplate responses for most typically encountered UR issues.

Update Requests with no immediately obvious issue

General Error with no descriptive text

Volunteer responding to your "general error" map-issue report. Waze gives us volunteers very little to go on and we're stumped. What was wrong with the map? Can you provide any detail? (Open to any editor)

Wrong Driving Direction with no descriptive text

Volunteer responding to your "wrong driving direction" map-issue report. Waze gives us volunteers very little to go on; we do not even know where you were going! What went wrong with the route Waze gave you? Can you tell us your destination address as you entered it into Waze? (Open to any editor)

Incorrect Junction with no descriptive text

Volunteer responding to your "incorrect junction" map-issue report. Waze gives us volunteers very little to go on. What junction was incorrect? What was incorrect about it? (Open to any editor)

Update Requests with common solutions

Fixed

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 or so. Cheers!

The "Waze 180"

Volunteer responding to your report of a map issue. When you ask for a route immediately after waking up Waze, it has to guess what direction you are pointed. If it guesses wrong, it may give you an awkward route to avoid any illegal U-turns (I call this the "Waze 180"). When Waze offers you a route that starts off the wrong way, please drive a little in the direction you are pointed and then ask for the route again. This gives Waze a chance to know which way you are pointed and offer you a more suitable route. If you are sure this was not the problem, please respond, otherwise we'll close out this report in a few days. Cheers!

Google fu

Volunteer responding to your report of a map issue. The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google). We have asked Google to fix its database but we have no control over how fast Google will respond. It is usually days, but it can be weeks or even months. We'll leave this report open in the meantime. Cheers!

Bogus GPS

Volunteer responding to your report of a map issue. It looks like your GPS position information was awfully inaccurate. Bad GPS position data can cause all sorts of problems. Waze may think you are on some other road and give you bogus directions to get you back to the road you're really 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. Cheers!

Stale or bogus heavy-traffic indications/routing

Volunteer responding to your report of a map issue involving wrong traffic indications. We volunteer map editors can't do anything about Waze's traffic reporting, but I can explain what may have happened. When Waze thinks it has detected a traffic situation it can remember it for awhile, sometimes long after the situation changes. Also, slow-moving Wazers can confuse Waze into incorrectly declaring heavy traffic (this is why one should never run Waze while walking or biking along roads). We'll close out this report. Cheers!