1. 1. Blossoms, Weeds, and blades of grass Growing the map Photo CC BY-SA 2.0 Katy Walters: http://www.geograph.org.uk/photo/231339
2. 3. Photo: Frhlingsblumen Krokus by Benjamin Gimmel CCBYSA 2 etc on wikimedia commons: http://commons.wikimedia.org/wiki/File:Fr%C3%BChlingsblumen_Krokus.jpg
3. 4. Cambridge
4. 5. Photo: CC BY 2.0 psd on flickr: http://flic.kr/p/2uUoQ
5. 7. Photo CC BY-SA 2.0 mariosp on flickr: http://flic.kr/p/8A1DsY
6. 9. Photo GFDL/CCBYSA3 Quadell on wikimedia commons: http://commons.wikimedia.org/wiki/File:Wald_Vergissmeinnicht.jpg
7. 10. Keeping an eye on the map
8. 13. Photo CC BY 2.0Slideshow Bruce on flickr: http://flic.kr/p/7YGuns
9. 14. Image by Kamikaze Stoat CC BY 2.0 on flickr http://flic.kr/p/rMHgf
10. 17. Imports & U.S.
11. 18. Even coverage Photo CC BY-SA 2.0 AdamKR on flickrhttp://flic.kr/p/7SkGUP
12. 20. Even coverage. More detail CC BY-SA 2.0 Lilli2de on flickr http://flic.kr/p/8jGXZC
13. 21. Blossoming Denverand the U.S.
14. 22. Before TIGER ...waiting for TIGER
15. 23. After TIGER Still slow Negative effects of imports?
16. 24.
    • The best imports are those we avoid. Frederik Ramm Imports bad.Surveying good
    Matt Amos
17. 25. Do imports stifle community?
    • Matt's simulation
    • 26. Knowing the data is available
18. 27. Landuse in rural France
19. 28. Active community in rural Austria
20. 29. Why would it stifle the community?
    • Blank slate entices contribution and exploration
    • 30. Existing data and existings mappers more exciting than just existing data.
    • 31. Imported data is not beginner friendly
21. 32. Atlanta example
22. 33. A field of corn ...or thorny brambles Photo CC BY SA 2Richard Webb on geograph http://www.geograph.org.uk/photo/640790
23. 34. It's not enough to just make sure you'releaving themap in a better state ... You should make sure you are you're leaving thecommunity in a better shape Frederik Ramm
24. 35. Users editing some POI types, normalised to urban population
25. 36. Fixup vs Community engangement
    • New imports should involve planned fixup
    • 37. Leave the community in a better state
    • 38. Engage, discuss and plan before, during and after
26. 39. Facing facts... facing fixup Imports are done. Move on....Fix up!
    • Progress reports motivate
    • 40. Gamification
    • 41. Documentation.
      • Spell it out. Video tutorials
27. 42. 250 cities
28. 43. Duplicate nodes
29. 44. TIGER alignment
30. 45. TIGER alignment
31. 46. Cleveland example
32. 47. Important. Improvements
33. 48. Keep Right
34. 49. A bit of weeding to do... CCBYSA2 Gordon Joly :http://flic.kr/p/aoj2ij
35. 50. Trouble in the garden
    • Wonderful blossoms of details ... Uneven coverage Bad for map users
36. 51. Uneven coverage problems for users
    • Jigsaw puzzle example
    • Blossoms of
    • 52. building coverage
    • 53. Ugly map!
37. 54. A deeper problem. Levels of details
    • Blossoms of mega-detail near home
    • 55. More details
      • new ideas for types of features (& tags)
38. 56. Progressively more insane
    • POI types. Map every shop
    • 57. Building outlines and addresses
    • 58. Walls and fences (Pedestrian routing)
    • 59. Sidewalks on every road
    • 60. Roads as areas
    • 61. Every tree
    • 62. Every plant
    • 63. Every blade of grass
39. 64. Every blade of grass Crazy example ...but where to draw the line? Problem?
    • Even coverage
    • 65. Wasted time of mappers
    • 66. (new mappers)
    CCBY2 meddygarnet:http://flic.kr/p/7YZzim
40. 67. Solution?
    • Encourage sensible tagging proposals
    • 68. Config default/prominent renderers and toolchains
    • 69. Efforts to even out coverage
    • 70. A new message? :
    • 71. Consider the levels of detail around you
    ...more like a field of corn
41. 72. Need more blossoms Need more even coverage
42. 73. CCBY2 gardenvisit.com : http://flic.kr/p/6zbGiw
43. 74. Harry Wood has been an OpenStreetMap enthusiast, and contributor since 2006. He works as a senior software engineer athttp://placr.co.ukon projects relating to transport and GPS data analysis. Previously he worked in a technical and OpenStreetMap community development role at CloudMade. In 2011 he has continued to volunteer for the project in several roles, as mapper, developer, documenter, community coordinator, promoter, and the chief London event organiser. http://harrywood.co.uk These slides are freely re-usable under theCreative Commons Attribution-ShareAlike 2.0 License , Note that open licenses on some of the images are similar but not the same as this. Please retain all credits Map images cc-by-sa2 OpenStreetMap.org contributors