Changes

From Wazeopedia

User:Karrows

6,557 bytes added, 2 years ago
m
no edit summary
== Update Requests with no immediately obvious issue ==
 
=== How to pave a road ===
 
To "pave a new road" in Waze open the report menu: Choose Map Issue and select the Pave tab: Click on Pave road to start paving. To stop paving click on the icon at the left of the screen:
 
After a new road is paved by a waze user, it will get added to the map after an editor edits it and cleans it up.
 
=== UR not near a road ===
 
Volunteer responding -
 
It appears that you are not near any drivable roads. Waze is specifically not intended for any other use than driving as walking/biking or other activities mess up the road speed data Waze uses to create routes.
 
Waze did not send us enough information to fix your request. Would you please let us know what went wrong?
 
=== speed limit not showing in app ===
 
We have had several reports of speed limits not showing in the app even when they are set. Unfortunately, in this situation, there is nothing wrong with the map that we can adjust to prevent issues with the app. Since speed limits are a new feature, I suggest being patient while Waze works out all the bugs. You can also report this to https://support.google.com/waze/answer/6276841
 
=== speed limit already correct ===
 
Volunteer responding - It looks like the speed limit is already set correctly here. We have heard that many of these reports were submitted inadvertently. Due to the large number of these reports which we've received since the release of speed limit reporting, we are closing this report at this time. Speed limits only display in the client when you are speeding, unless you set the speedometer settings to show them all the time. Waze is a bit slow with refreshing the screen when the speed limit changes, it can take several to seconds or longer. Mobile phone GPS signals typically have some delay, you may notice this as you drive past a street in real world while Waze shows that you are not quite past the street yet. Unfortunately, in this situation, there is nothing wrong with the map that we can adjust to prevent issues with the app. Since speed limits are a new feature, I suggest being patient while Waze works out all the bugs. This request will now be closed. Please feel free to report any other Speed limit signs or map issues you encounter on your drives. Thanks!
 
Please be aware that sending multiple reports for the same map issue over a short time taxes the volunteer map editors and prevents them from helping other reporters. Sending multiple, identical reports of any kind may be considered gaming, and can result in loss of reporting privileges.
 
PS Speed limits are for informational purposes only and do not affect routing or ETA calculations, those are based on average actual speeds of drivers on the roads.
 
=== missing invalid speed limit ===
 
Volunteer responding to your speed limit error report. What should the speed limit be? Any chance you could tell us where this speed limit begins and ends?
 
=== Speed Limit Lag ===
It looks like the speed limit change is already set correctly here. Mobile phone GPS signals typically have some delay. You may notice this as you drive past a street in real world while Waze shows that you are not quite past the street yet. Also Waze seems to be a bit slow with refreshing the screen on speed limit changes. So because of this, while it is nice to have the user request dropped right at the speed limit sign, I'd suggest waiting a few seconds to see if waze is just slow at refreshing the speed limit. If you think this is wrong or there is some other problem let us know. Otherwise well will close out this report in a few days. Thanks!
 
=== General Error ===
== Likely cause identified, give reporter opportunity to clarify ==
 
=== MN Basemap ===
 
Volunteer responding to your report of a map issue. This area is what we call "basemapped" in that it has not been edited since the start of Waze, and it is still the untouched original basemap import.
 
The Waze map is completely crowdsourced by volunteers. Sadly we do not have enough volunteer editors to cover the entire state and we have even fewer editors in rural areas. So honestly, I can't predict when anyone will be available to update this area.
 
The good news is you can help fix the map yourself! By logging into https://www.waze.com/editor/ you can fix the areas you have driven. If you are interested in mapping in MN, you can join our Google Hangout for MN editors where you can get help with mapping by going to this address https://hangouts.google.com/group/8gF0thNrKFjtkOTG3 Hopefully you can volenteer some time to help out with the map in this area. Thanks.
 
Open to any editor. Please close this report when the area is updated.
=== The "Waze 180" ===
Volunteer responding to your map-issue report in which you described the problem as an address. Did you mean to enter the address as a navigation destination? If there is a problem with the address please respond using the Waze app (emails don't work with the reporting system) and explain what went wrong. Otherwise we'll assume this was an accident and close out this report in a few days. Cheers! (Open to any editor)
 
== Lapsed conversations with other editor(s) ==
== Closing alerts ==
 
=== fixed speed limits ===
 
The missing/incorrect speed limit you reported has been updated. Please wait a few days for the map to be updated. Thank you!
 
=== No response, closure imminent ===
Volunteer responding to your report of a map issue. 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. Thanks.
 
=== Fixed location in Waze AND Google map maker ===
 
Volunteer responding to your report of a map issue. The good news is that we found your destination was incorrectly located on the Waze map and we have fixed it! We also went ahead and fixed it in Google Maps. The fix in Waze should be available within a week, but on rare occasions it can take longer. For Google Maps, no one can predict how long it takes for them to update anything, sometimes it can take many months. 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. Thanks.
(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.)
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. Waze tries really hard to find you the fastest route, and it does that very well. Sometimes though, the fastest route may not be the safest or smartest route. As drivers ourselves we know how frustrating this is. 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.
 
There are plans in the works to have an "avoid dangerous turns" option in waze in the future. But with Waze "coming soon" could mean it is still years away. So until then there's nothing we can do.
=== Verified temporary road closure ===
The great thing about Waze is that it tries really hard to find you the fastest route. Sometimes the bad thing about Waze is it tries a little too hard to find you the fastest route and creates strange routes like this.
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 a detour 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.
I've found that sometimes the best way to fix these problems is to follow Waze's suggestion a few times. If it is slower, Waze records your speed data and should eventually adjust future routes. Or, you may find the alternative is a faster route.
Volunteer responding. Based on this report's timestamp, location, and other data, it appears to be a duplicate of one or more other reports submitted nearby. A single report is usually sufficient, so we will close this as an accidental resubmission. No worries! However, please be aware that sending multiple reports for the same map issue over a short time taxes the volunteer map editors and prevents them from helping other reporters. Sending multiple, identical reports of any kind may be considered gaming, and can result in loss of reporting privileges.
 
== Other==
 
=== Response time ==
 
The Waze map is completely crowdsourced by volunteers. Sadly we do not have enough volunteer editors to cover the entire state and we have even fewer editors in rural areas. So if you are unhappy with the response times, we have GREAT NEWS! You can help fix the map yourself! By logging into https://www.waze.com/editor/ you can fix the areas you have driven. If you are interested in mapping in MN, you can join our Google Hangout for MN editors where you can get help with mapping and have access to higher level editors to help with restriced edits by going to this address https://hangouts.google.com/group/8gF0thNrKFjtkOTG3 Hopefully you can volenteer some time to help out with the map in this area. Thanks.
111
edits