Day1-1610-Validating OpenStreetMap

Friday 4:10pm, Main hall
Arun Ganesh

http://2017.stateofthemap.org/2017/validating-openstreetmap/

Transcript

1. Validating the map State of the Map 2017, Japan user:PlaneMad | Arun Ganesh
2. Crowdsourced data projects
3. Cities can become shops
4. Or an office
5. Or just get a bad name
6. Why does it happen?
7. My mouse moved
8. It’s time to rename my city
9. This looks prettier
10. The virus has caught on
11. This description tag looks useful
12. Need PokeStop now
13. This is a nice place to draw
14. From where? Contributors or Software
15. 60% of harmful changes are from New contributors Source: OSMCha
16. New contributors Naturally make mistakes Not aware of OpenStreetMap Not aware of contribution guidelines Not familiar with editing tools Not familiar with tagging system Not aware of community
17. Experienced contributors Make large scale edits Use powerful tools Edit important and very complex features Not scared of making a mistake But mistakes happen
18. More new and active contributors than ever before
19. Software Simple tools attracts new users Power tools allows large scale editing Don’t give powerful tools to new users
20. Everything breaks
21. Protecting the map No single strategy can be foolproof We need as many eyes on the data as possible
22. We need to see the data, not the map
23. Foolproof data validation requires local context
24. We need accessible tools for community to peer review data Over 30 tools listed on OSM Wiki None on the OSM Homepage
25. 30,000 changesets by 4,000 users everyday. 2000 new users/day
26. OSMChangesetAnalyzer
27. Filter changesets by location, date, category..
28. Visualize a changeset like Achavi
29. Peer review and tag changesets
30. 103,680 changesets reviewed 14,133 found with bad quality Use for machine learning?
31. Contribute Source code https://github.com/mapbox/osmcha-frontend/issues Write detectors https://github.com/mapbox/osm-compare
32. Get in touch arun@mapbox.com Join the OSMCha Workshop on Sunday 1.30pm