Skip to content

Instantly share code, notes, and snippets.

@tmcw

tmcw/things_that_could_improve_osm.md

Created May 31, 2013 15:00
Show Gist options
  • Save tmcw/5685578 to your computer and use it in GitHub Desktop.
Save tmcw/5685578 to your computer and use it in GitHub Desktop.
Download ZIP
3 Things That Could Improve OSM Data Quality
Raw
things_that_could_improve_osm.md

On the geowanking mailing list, Frederic Julien asked what can potentially improve OSM Data. Here are my three:

  1. Strong conflation tools, so that OSM data can be easily cross-referenced with 'authoritative' or pre-existing sources and basic improvements like way accuracy, importing missing data, and adding new tags can be done in bulk. In the US, especially, there is plenty of data which overlaps with existing imported, traced, or GPS-mapped OSM data, but could be very useful as a reference, like the new TIGER data.
  2. Addressing and routing with a 'report an error' process. Additional services with the necessary feedback to OSM itself essentially provide Quality Assurance as a side-effect.
  3. With respect to #1 and #2, either improvement or replacement of the license to permit new data sources to push and pull OSM data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment