The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

User:D39andrew/UR Responses

From waze
< User:D39andrew
Revision as of 21:01, 25 January 2017 by PesachZ (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Mine

User reports bad location (early arrival notice, directed near destination)

Volunteer responding to your report of a map issue. It looks like your GPS position information was inadequate to perform your desired activity. Sometimes Waze does not have adequate GPS location information, and makes a best estimate as to where you are in relation to the destination. GPS resolution, in perfect conditions, is about 4 meters (that’s about 13 feet). When perfect conditions do not exist, then that “circle of resolution” is much larger.
That is why Waze said you were at your destination, but were a block away
That is why Waze took you on a circuitous route and directed you near your destination, but in the side streets behind your destination.
Since the map looks correct, all I can recommend is that you ensure your handheld device has a clear view of the sky from wherever you have it mounted in your car 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. Safe Travels!

User wants lane resolution (Geek-out return rant)

Volunteer responding to your report of a map issue. It looks like your GPS position information was inadequate to perform your desired activity. Bad GPS information can cause all sorts of problems. GPS resolution, in perfect conditions, is about 4 meters (that’s about 13 feet). In the USA, a standard lane of traffic is 3.7m (12 ft.). So you want lane determination or other high resolution location information from your GPS, that is also a phone and many other things, stuck somewhere in a metal box, behind glass, with an internal antenna to figure out which 3.7 meter lane you are in with a minimum of 4 meter resolution? Maybe it could do that if you were out in the middle of a flat plain, with good view of the sky and at least 4-6 GPS satellites in view by your device.

In Airplanes, with huge antennas and thousands of dollars of equipment, only get 2.168 meters (8.6 feet) accuracy. The military may get better resolution (classified), but they are spending megabucks. The good news is that accuracy of GPS is improving over time, and you can find out more here: http://www.gps.gov/systems/gps/performance/accuracy/

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. Safe Travels!

Google Pin Bad Location

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. I confirmed the Google position for your destination is the problem. I have made a suggestion to Google to move the location pin further away from Oxburough Dr, which should help. But alas, it it only a suggestion, and Google may or may not accept the change request, and if accepted, when it will be applied. At any rate we'll close this report as the Waze map itself appears to be OK. Safe Travels!.

Other Users