Vectorspace (talk | contribs) |
Vectorspace (talk | contribs) |
||
| Line 40: | Line 40: | ||
* Development of a UR Troubleshooting Guide leading to training lecture | * Development of a UR Troubleshooting Guide leading to training lecture | ||
== DRAFT: Update Request | == 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. | 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: | |||
* [[Update_request | Update Requests Wiki Page]] | |||
* [https://www.waze.com/forum/viewforum.php?f=8 Waze Map Editor Forum] | |||
Revision as of 20:02, 26 June 2014
 |
Vectorspace can be reached by private message. |
Vectorspace is a Global Champ, U.S. country manager, based in New Mexico.
Profile
Existing/Ongoing Waze Projects
- Formal Mentoring
- Leading Waze Formal Mentoring along with OrbitC
- Training Materials for Editors / Self-Management
- Development of a training curriculum
- Development of lecture presentations
- Webinar development/hosting
Wiki Development Activity / Interest
- Formal Mentoring
- Private_Installations
- Special Use Road Systems
- Corrective Action for Troubled Editors
- Action Plan approach to retain good editors with bad approach
- Corrective_Action/USA - An early attempt for standardization
Initiatives
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: