Difference between revisions of "User:Vectorspace"

From Wazeopedia
Line 62: Line 62:
 
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.
 
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'''
+
'''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 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.
+
**You can ask help from another more experienced editor.
***For URs, you can send a note back to the reporter asking for more detail.
+
**For URs, you can send a note back to the reporter asking for more detail.
  
* Observation: UR Type
+
'''Observation: UR / Map Issue type'''
* Users submitting URs can choose a particular type.  These are more clearly outlined in the
+
Users submitting URs can choose a particular type when selecting "Map Issue." These are:
 +
* General map error
 +
* Turn not allowed
 +
* Incorrect junction
 +
* Missing bridge or overpass
 +
* Wrong Driving Directions
 +
* Missing exit
 +
* Missing road
  
* '''Observation: UR Location'''
+
You may gain additional insight from the type submitted; however, most users will not likely select a type and when they do, it may not be related to the issue they have.  Consider the following when considering the Map Issue type.
** 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'''
+
* General map error
** User Drive
+
* Turn not allowed
** Waze Provided Route
+
* Incorrect junction
 +
* Missing bridge or overpass
 +
* Wrong Driving Directions
 +
* Missing exit
 +
* Missing road
  
* '''Observation: Text To Speech (TTS) Commands'''
+
'''Observation: User Comment'''
** A turn command on a straight road
+
* 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.
  
* '''Tool: Live Map'''
 
** Routing destination problems
 
** Mention that traffic can change answer
 
  
* '''Tool: Validator'''
+
'''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'''
 +
* Validator is a script tool that you may consider using. It is a fairly advanced tool that should not be used by new editors.

Revision as of 20:28, 26 June 2014

Vectorspace can be reached by private message.

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

Initiatives

  • Development of a User Report Canned Response Wiki Page
  • Development if a Water Area Place Wiki Page
  • Development of a UR Troubleshooting Guide leading to training lecture

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.

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 / Map Issue type Users submitting URs can choose a particular type when selecting "Map Issue." These are:

  • General map error
  • Turn not allowed
  • Incorrect junction
  • Missing bridge or overpass
  • Wrong Driving Directions
  • Missing exit
  • Missing road

You may gain additional insight from the type submitted; however, most users will not likely select a type and when they do, it may not be related to the issue they have. Consider the following when considering the Map Issue type.

  • General map error
  • Turn not allowed
  • Incorrect junction
  • Missing bridge or overpass
  • Wrong Driving Directions
  • Missing exit
  • Missing road

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

  • Validator is a script tool that you may consider using. It is a fairly advanced tool that should not be used by new editors.