|
|
| (13 intermediate revisions by one other user not shown) |
| Line 17: |
Line 17: |
|
| |
|
| == Wiki Development Activity / Interest == | | == Wiki Development Activity / Interest == |
| | These are pages upon which I was primary contributor. |
|
| |
|
| *Formal Mentoring | | *Formal Mentoring |
| Line 30: |
Line 31: |
| * Corrective Action for Troubled Editors | | * Corrective Action for Troubled Editors |
| ** Action Plan approach to retain good editors with bad approach | | ** Action Plan approach to retain good editors with bad approach |
| ** [[Corrective_Action/USA]] - An early attempt for standardization | | ** [[Corrective_Action]] - An early attempt for standardization |
|
| |
|
| == Initiatives == | | == Initiatives == |
| | These are pages I've tried to motivate others to be primary developer. |
|
| |
|
| | * Development of a WME Chat Wiki Page. |
| | ** https://www.waze.com/forum/viewtopic.php?f=276&t=89344 |
| | ** Result: [[Waze_Map_Editor/Chat]] |
| * Development of a User Report Canned Response Wiki Page | | * Development of a User Report Canned Response Wiki Page |
| ** [https://www.waze.com/forum/viewtopic.php?f=129&t=78759 Forum] | | ** [https://www.waze.com/forum/viewtopic.php?f=129&t=78759 Forum] |
| * Development if a Water Area Place Wiki Page | | * Development if a Water Area Place Wiki Page |
| ** [https://www.waze.com/forum/viewtopic.php?f=276&t=95745 Forum] | | ** [https://www.waze.com/forum/viewtopic.php?f=276&t=95745 Forum] |
| | ** Draft Wiki Page: [[User:Vectorspace/Water_Features]] |
| * Development of a UR Troubleshooting Guide leading to training lecture | | * Development of a UR Troubleshooting Guide leading to training lecture |
| | | ** Draft Page: [[User:Vectorspace/Diagnosing_Update_Request_%26_Map_Problems]] |
| == DRAFT:Troubleshooting Update Request & Map Problem ==
| |
| | |
| This is a draft set of ideas for a new Wiki page on this topic. Motivation for this page is that there has been a lot of knowledge developed by skilled editors about how to diagnose problems on the map but that has not been well documented. New and experiened editors could benefit from this knowledge.
| |
| | |
| === Existing knowledge ===
| |
| This information is for development and not to be included with this page.
| |
| | |
| * [[Update_request]]
| |
| ** This page is focused on the mechanics of the issue, but not troubleshooting. It should not be expanded in order to keep it on point and simple. This draft page should complement and link from/to this page.
| |
| | |
| === Introduction ===
| |
| | |
| Waze provides two forms of error reports within the editor. '''Update Requests (UR)''' are from drivers using the client. '''Map Problems (MP)''' are created by automated algorithms at Waze that find and point out anomalies. This page is focused on approaches and techniques to diagnose or solve these error reports.
| |
| | |
| Additional information can be found here. It is suggested that before you use techniques in this article that you gain requisite knowledge of URs and MPs by reading the first two items, Wiki pages on those subjects.
| |
| * [[Update_request | Update Requests Wiki Page]] | |
| * [[Map_Problems_in_Waze_Map_Editor | Map Problems Wiki Page]]
| |
| * [https://www.waze.com/forum/viewforum.php?f=8 Waze Map Editor Forum]
| |
| | |
| === Techniques & Tools ===
| |
| This section is currently an outline form of notes about the types of techniques and tools that can be used for troubleshooting and diagnosing URs and MPs. It will eventually be expanded into more detailed content.
| |
| | |
| '''Caveats'''
| |
| * You cannot diagnose every UR. Sometimes users just send in a report for no reason. Sometimes the clues you have are insufficient. Don't waste your time looking too hard. What can you do?
| |
| **You can ask help from another more experienced editor.
| |
| **For URs, you can send a note back to the reporter asking for more detail.
| |
| | |
| '''Observation: User Comment'''
| |
| * If you're lucky, a user will enter in a comment about their issue. This is displayed as "Problem:" in the map editor when you select a UR. For example, "Problem: misspelling: Paseo del Paisano." Here the user is clearly indicating the road name is misspelled. Other comments can be less clear.
| |
| | |
| '''Observation: UR / Map Issue type'''
| |
| | |
| Users submitting URs can choose a particular type when selecting "Map Issue." These listed below with suggested approaches:
| |
| * General map error
| |
| ** Unknown - Seek additional information from elsewhere in the UR.
| |
| ** Look for a map anomaly in the area of the UR, such as a missing road,
| |
| * Turn not allowed
| |
| ** Check the Waze Provided Route to see if Waze suggested an impossible or illegal turn. Add turn restrictions as needed.
| |
| ** ?
| |
| * Incorrect junction
| |
| ** Are two roads that should connect not connected by a node on the map? If so, add a node junction between these two roads.
| |
| ** ?
| |
| * Missing bridge or overpass
| |
| ** See Incorrect Junction
| |
| ** Are two roads that are not connected (e.g., with an underpass/overpass) connected on the map? If so, remove the junction and adjust levels of the segments.
| |
| ** ?
| |
| * Wrong Driving Directions
| |
| ** This is one of the most difficult URs to resolve because the directions being reported could be a long distance from the UR location and you do not have the whole path available to you.
| |
| ** Wrong driving directions may be the result of a faulty Point of Interest (POI) search, wrong search results, or an error by the user.
| |
| ** Check the Waze Provided Route and the User Drive paths.
| |
| ** ?
| |
| * Missing exit
| |
| ** Is there a missing road or ramp in the region of the UR? If so, correct it.
| |
| * Missing road
| |
| ** Is there a missing road or ramp in the region of the UR? If so, correct it.
| |
| | |
| | |
| '''Observation: UR Location'''
| |
| * UR location is the pin placement location
| |
| * UR location is usually where the user presses the "Map Problem" report button in the client. It may not be the exact GPS coordinates and may snap to the nearest existing map road nearby the user.
| |
| * Potential knowledge gained
| |
| **Is there an obvious map error at this point?
| |
| ***Road missing?
| |
| ***Potential routing error difference between the Waze Provided Route and the User Drive?
| |
| ***Road geometry wrong?
| |
| ***Place Area missing?
| |
| *** ?
| |
| | |
| '''Observation: User Drive & Waze provided Route'''
| |
| | |
| Waze attempts to record a partial path for both the User Drive and the Waze Provided Route around the region of the UR. If the user is not navigating to a location, no Waze Provided Route can exist. If the user is stationary or some other error occurs, you will not always see a User Drive.
| |
| | |
| * Comparing User Drive & Waze Provided Route
| |
| ** Are they the same?
| |
| *** If the two paths are the same, you will gain little information from this comparison. Consider the path itself as mentioned below.
| |
| ** Are they different?
| |
| ***This is a potential routing issue, at least in the mind of the user. Some differences are expected because Waze may have a different path in mind.
| |
| ***Look at the point of departure between the two paths to see if there is a map error.
| |
| | |
| | |
| * User Drive by itself.
| |
| * Waze Provided Route by itself.
| |
| | |
| '''Observation: Text To Speech (TTS) Commands'''
| |
| * A turn command on a straight road
| |
| | |
| '''Tool: Live Map'''
| |
| * Routing destination problems
| |
| * Mention that traffic can change answer
| |
| | |
| '''Tool: Validator'''
| |
| * Validator is a script tool that you may consider using. It is a fairly advanced tool that should not be used by new editors.
| |
