NYS Wazeopedia UR Guidelines
UR closure procedure came up on a Discord channel and we couldn't find a good resource for the timeline/procedure we use for responding/reminding/closing URs in NYS. Wazeopedia seems like a logical home for it, as well as perhaps a sticky post here in the NYS Forum. I'd like to propose something like the following for the NYS Wazeopedia page:
viewtopic.php?p=1778710#p1778710
To grab some of the verbiage from there, maybe in addition to the above items we could also add:
https://wazeopedia.waze.com/wiki/USA/Us ... Guidelines
Let me know if words should tweaked, added, removed, etc and hopefully we can come to a consensus on what to add to our NYS Wazeopedia page to eliminate any UR closure confusion and give some good advice on how to get the best end result (a solved UR).
Thanks for the consideration!
This would go under a new section rather than shoehorning into an existing section. It would also be useful I think to incorporate some of the great advice given here:- When finding a UR, first look for anything obviously wrong either given the area reported, user trace/Waze route or user comments on the UR.
- If the problem can not be identified, a comment should be added asking the reporter for more information.
- If no further information is received within 7 days, follow up with the reporter politely reminding them that we need more information to identify the problem.
- If, after another 7 days there is still no correspondence, leave a final note indicating that the problem was unclear and that we'll need to close the issue as 'Not Identified'. This final notice should mention following up with more information by sending an email to WazeNewYork@gmail.com with the subject 'Attn: <Waze username>'.
viewtopic.php?p=1778710#p1778710
To grab some of the verbiage from there, maybe in addition to the above items we could also add:
I rearranged some things, did some wordsmithing and mocked up a sample page in my Wazeopedia name space:Update Requests (URs) represent the customer service that we, the Waze Map Editors, are giving to the end user. The higher the solve rate, the better customer service we deliver and a better end user experience. In the end the goal should be to Solve a UR and not close it.
Factors that improve UR solving rate
- Quick response to new URs while the issue is fresh in the drivers mind
- Customize your responses based off information seen in the UR, reference the comments if they wrote one, indicate where the report was, identify differences in the "Waze provided route" and the actual "User Drive"
- Make sure you have done a quick Waze Street View search
- Do a Google search for the road name and town to see if anything comes up
Closing a UR as Not Identified
- If there is a cluster of URs and you can not figure out the root of the problem, consider leaving the URs open a little longer to see if another UR comes along to provide more information. This may allow you to solve them all or leave a map comment to track.
- Fix another issue in the area. While you may not have solved this issue, make sure we are always improving the map. A good practice is to make at least one improvement in the area (Fix a place, update HN, add missing speed limits, etc) when marking a UR as Not Identified - this will help future proof the area.
https://wazeopedia.waze.com/wiki/USA/Us ... Guidelines
Let me know if words should tweaked, added, removed, etc and hopefully we can come to a consensus on what to add to our NYS Wazeopedia page to eliminate any UR closure confusion and give some good advice on how to get the best end result (a solved UR).
Thanks for the consideration!
Re: NYS Wazeopedia UR Guidelines