mNo edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
===Google Pin Bad Location=== | ===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 | 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 to a more correct position 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!. | ||
===Bad Apartment Location=== | |||
The "pin" for the address is in the middle of the apartment complex. I will adjust its position so it can be improved and work better for you next time. The problem with apartments is that they often have one address, cover a large area, and oftentimes we don't map the roads inside the complex. Waze does it's best trying to get you to the entrance of the apartment complex. Sometimes the pin is in the middle of the complex and Waze can direct you on an interesting route as you described. I will leave this open for a few days in case you have some additional comments. Otherwise, we will assume all is well and close this report. Please feel welcome to report problems with the map in the future. | |||
==Other Users== | ==Other Users== | ||
| Line 32: | Line 35: | ||
Red Roads -- | Red Roads -- | ||
Please review the following wiki page:https:// | Please review the following wiki page: https://wazeopedia.waze.com/wiki/USA/Creating_and_editing_road_segments#Confirm_the_road_by_updating_details | ||
URs -- | URs -- | ||
As a novice editor, you should probably leave the User Requests/Map Requests to when you have more experience. | As a novice editor, you should probably leave the User Requests/Map Requests to when you have more experience. | ||
Unconnected Roads -- | |||
<nowiki> </nowiki>The reason is because the road you are connecting to is locked at a higher editing level than you are. In this case, you should request assistance from a higher level editor. The *formal process* for requesting help from a higher-ranking editor is to start a dedicated thread on the US unlock/update forum https://www.waze.com/forum/viewforum.php?f=622. There is an *informal process* too, which involves asking a higher level editor to assist via Private Message or the California Editors Slack group (see below). | |||
| Line 52: | Line 58: | ||
If you intend to become a serious Waze editor, you should join the California Slack to learn, ask questions, and communicate with other editors. | If you intend to become a serious Waze editor, you should join the California Slack to learn, ask questions, and communicate with other editors. | ||
Please PM | Please PM one of the site administrators (Tonestertm, Dwarflord, or Citeman) to request an invite. Please provide the following: | ||
(1) your email address; | (1) your email address; | ||
(2) your Waze handle; | (2) your Waze handle; | ||
Latest revision as of 03:37, 24 August 2017
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? The satellites are travelling at approximately 17,000 MPH at an altitude of 20,200 km (12,550 miles). 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 to a more correct position 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!.
Bad Apartment Location
The "pin" for the address is in the middle of the apartment complex. I will adjust its position so it can be improved and work better for you next time. The problem with apartments is that they often have one address, cover a large area, and oftentimes we don't map the roads inside the complex. Waze does it's best trying to get you to the entrance of the apartment complex. Sometimes the pin is in the middle of the complex and Waze can direct you on an interesting route as you described. I will leave this open for a few days in case you have some additional comments. Otherwise, we will assume all is well and close this report. Please feel welcome to report problems with the map in the future.
Hello New Editor
I see you have edited the map recently in <location> . Welcome To Waze Map Editing.
Parking Lots -- Please review the wazeopedia on parking lots. https://wazeopedia.waze.com/wiki/USA/Places/Parking_lot
Red Roads -- Please review the following wiki page: https://wazeopedia.waze.com/wiki/USA/Creating_and_editing_road_segments#Confirm_the_road_by_updating_details
URs -- As a novice editor, you should probably leave the User Requests/Map Requests to when you have more experience.
Unconnected Roads -- The reason is because the road you are connecting to is locked at a higher editing level than you are. In this case, you should request assistance from a higher level editor. The *formal process* for requesting help from a higher-ranking editor is to start a dedicated thread on the US unlock/update forum https://www.waze.com/forum/viewforum.php?f=622. There is an *informal process* too, which involves asking a higher level editor to assist via Private Message or the California Editors Slack group (see below).
Have you viewed the Waze Map Academy videos on editing?
https://www.youtube.com/playlist?list=PL0C9FD01D87B5FD66
Additionally and most importantly, please review the following wiki page: Edits to Avoid https://wazeopedia.waze.com/wiki/USA/Edits_to_avoid
Pay close attend to the following sections:
6.1 Constructive work for new editors https://wazeopedia.waze.com/wiki/USA/Edits_to_avoid#Constructive_work_for_new_editors
6.2 Risky work for new editors https://wazeopedia.waze.com/wiki/USA/Edits_to_avoid#Risky_work_for_new_editors
If you intend to become a serious Waze editor, you should join the California Slack to learn, ask questions, and communicate with other editors.
Please PM one of the site administrators (Tonestertm, Dwarflord, or Citeman) to request an invite. Please provide the following: (1) your email address; (2) your Waze handle; (3) the part of California where they edit actively; and (4) your home region if it is different from where you actively edit.
Feel free to contact me with any questions, and to review your work.