User:Vectorspace View history

VisualWikitext
m (Fixed link)
 
(18 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: UR Type
* Users submitting URs can choose a particular type.  These are more clearly outlined in the
 
* '''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.
 
* '''Observation: User Drive & Waze provided Route'''
** User Drive
** Waze Provided Route
 
* '''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'''

Latest revision as of 08:23, 19 April 2017

 Vectorspace can be reached by private message.
 As of 23 August 2022 (2022-08-23), the forum Private Message system is being replaced by a new Forum Chat feature. This template will need to be updated once that new Forum Chat feature is finalized. Details covered in this forum thread.

Vectorspace is a Global Champ, U.S. country manager, based in New Mexico.

Profile

Waze Forum 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

These are pages upon which I was primary contributor.

Initiatives

These are pages I've tried to motivate others to be primary developer.

Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=User:Vectorspace&oldid=153412"