User:Herrchin/Basemap editing practices

From Wazeopedia

< User:Herrchin

Revision as of 20:30, 24 January 2016 by Herrchin (talk | contribs)

The "basemap" is the original road data that Waze imported in 2009. It needs to be updated by map editors to function optimally.

Recommended scripts/plugins

Common basemap issues

  1. Roads with unknown direction
  2. Two-way roads incorrectly marked as one-way (one-way roads are rare outside urban areas)
  3. Unconfirmed turns.
  4. Unnecessary junctions.
  5. Incorrect u-turns.
  6. Reverse connections.
  7. One-segment loops (often at the end of rural driveways). Fix: You can try to repair the loop, but often these are best simply deleted and the preceding driveway adjusted extended some.
  8. 2-segment loops that should be 3-segment (multi-entry rural driveways). Fix" First ensure the correct Road Type and Direction, then select one of the endpoint junctions and press "Q" to have WME Toolbox automatically add an additional junction node for you.
  9. Private farming paths that probably should not be mapped at all in Waze (to irrigation pivots, grain silos, other private building that no Wazer would route to.)
  10. Driveways to buildings that no longer exist, or other superfluous roads.
  11. "Spaghetti": A mess of private roads, paths, tracks added from a previous visual analysis of satellite imagery.
  12. Missing, outdated, or incorrect road names, or they do not match the NE road naming standards or USA abbreviations.
  13. Private roads with the State field set as Iowa.

Other improvements to make

Additional editing tips

  • Zoom in to level 4 or closer so that Validator highlights problems on segments of type Street and Private Road, and so that you can see the road characteristics (one-way/two-way/unknown, etc.).
  • Consider preserving private roads that parallel a public road, so that a Wazer on the private road isn't associated by Waze with the public road and potentially polluting the speed data.