User:Vectorspace

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

Wiki Development Activity / Interest

• Formal Mentoring
  • Mentoring/USA
  • Mentoring/USA/Guidelines
  • Mentoring/USA/Training
• Private_Installations
• Special Use Road Systems
  • Indian_Reservation_Roads
  • Forest_Service_Roads
  • Bureau_of_Land_Management_(BLM)
  • National_Park_Service
• Corrective Action for Troubled Editors
  • Action Plan approach to retain good editors with bad approach
  • Corrective_Action/USA - An early attempt for standardization

Initiatives

• Development of a User Report Canned Response Wiki Page
  • Forum
• Development if a Water Area Place Wiki Page
  • Forum
• 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:

• Update Requests Wiki Page
• Map Problems Wiki Page
• 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 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 a

• 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