OpenStreetMap: Key Issues Lightning Talk (CSCW 2015)

Transcript

1. OpenStreetMap: Key Issues Alan McConchie Design Technologist, Stamen Design PhD

   Candidate, University of British Columbia alan@stamen.com @mappingmashups CSCW Workshop: Advancing an Industry/Academic Partnership Model for Open Collaboration Research March 14, 2015

2. Origins of OpenStreetMap “The Wikipedia of Maps” Started in 2004

   in the UK Map originally based on nothing but volunteers’ GPS traces and notes

3. Image: Tom Carden and Steve Coast, 2005

4. None

5. OpenStreetMap today On-the-ground mapping still important Tracing from permitted satellite

   imagery Mass imports of data Automobile Navigation Data (Netherlands) TIGER/Line (U.S. Census Bureau) OpenStreetMap Other Imports

6. License CC-BY-SA until 12 September 2012 Now: ODbL CC-derived Open

   Database License Main difference: produced works (such as rendered maps) require attribution, but not share-alike only adapted databases trigger share-alike wiki.osm.org/wiki/Open_Database_License
7. None
8. None
9. None

10. Industry ecosystem built on OpenStreetMap Mapbox Mapzen Telenav Stamen ...and

    more

11. maps.stamen.com/toner

12. maps.stamen.com/watercolor

13. None
14. None

15. The question of imports

16. OSM TIGER Import Stands for “Topologically Integrated Geographic Encoding and

    Referencing” TIGER is a product of the United States Census Bureau, therefore in the Public Domain OpenStreetMap imported TIGER’s 2005 data starting in late 2007: animation: wiki.osm.org/wiki/Tiger

17. wiki.osm.org/wiki/Stats

18. Imports beyond TIGER

19. 19 Buildings without addresses

20. Addresses without buildings

21. Landcover

22. Incomplete landcover import

23. Critiques of imported data: Low data quality Destroys volunteer contributions

    Discourages new contributors

24. Current best practice wiki.osm.org / wiki / Import / Guidelines

25. Community Imports • Divide data into chunks • Community members

    manually upload each chunk NOTE: The term "Import" is highly loaded in the OSM community. "A distributed and curated merge," is a more accurate description of what Seattle OSM planning to do. — wiki.osm.org/wiki/Seattle_Import

26. Building community through imports Four training events and editathons Five

    events out walking around 20+ active participants slideshare.net/gwhathistory/osm-sotm-us-2013-imports4community-002

27. NYC community building import • Estimated 1500 hours of work

    • Volunteers + Mapbox employees • Coordination with NYC GIS Dept animation: mapbox.com/blog/nyc-buildings-openstreetmap

28. LA County building import (still in planning stage) 3,141,244 building

    footprints 6,423 block groups github.com/osmlab/labuildings

29. 29

30. 30

31. @mappingmashups alan@stamen.com