User:Herrchin/Basemap editing practices

From Wazeopedia

< User:Herrchin

Revision as of 19:41, 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.

Common basemap issues

  • Roads with unknown direction
  • Two-way roads incorrectly marked as one-way (one-way roads are rare outside urban areas)
  • Reverse connections
  • Unconfirmed turns
  • Incorrect u-turns
  • Unnecessary junctions
  • Private roads with the State field set as Iowa
  • Self-connected loops (often at the end of rural driveways)
  • 2-segment loops that should be 3-segment (multi-entry rural driveways)
  • Missing, outdated, or incorrect road names, or they do not match the NE road naming standards or USA abbreviations.
  • 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.
  • Driveways to buildings that no longer exist, or other superfluous roads.
  • "Spaghetti": A mess of private roads added from a previous visual analysis of satellite imagery.


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

Other improvements to make

  • Update the FC to the appropriate road type
  • Update lock level to match
  • Add Speed Limits
  • Correct elevation and add bridges/tunnels where appropriate per the Seagull guidelines