Importing into OSM

Ben Ritter
github.com/BudgieInWA
osm.org/user/BudgieInWA

The data processing

• Download and explore the data
• Extract the needed feautures
• Format the data for OSM editing tools
• Coordinate the grunt-work
• Incorporate the data into OSM
• Validate the results

Exploring and formatting the data

Simple POI data: conflation in JOSM

Creating a tilemap in QGIS

Tiles on a server

Data in OSM tools

Coordinating the grunt work

Incorporate the data into OSM (editing in JOSM)

Validate the result

• The HOT Tasking Manager has a validation step built-in
• Ensure the community is happy...

wait, the community!

What should we import into OSM?

• OSM standard: each feature verified by locals
  • preferably "on the ground"
• Imports are treated carefully (we'll look into this)
• Users are encouraged to merge OSM with their datasets themselves
• OSM data is "messy", but avoids large-scale consistent errors

OSM import process

• Licencing and attribution
• Documentation: Create an Import Plan wiki page
• Community buy-in: Publish the plan
• Upload the new data
• Validate

Licencing: obtain a waiver

• The ODbL Licence is very open
• A waiver is required for data under CC-BY, etc.
• The data source should be added to the Import/Catalogue and Contributors

Document the import

• Read Import/Guidelines
• Create an Import Plan page on the wiki
  • https://wiki.openstreetmap.org/wiki/Australian_Import_Catalogue/City_of_Canning_Open_Data_Imports

Publish the plan

• The community wants right of refusal
• Post on the Community Forum (community.openstreetmap.org) and local channels
• Incorporate feedback before importing

Upload the new data

• As we saw...
• Add tags to import changesets to identify them

Validate

• Verify some of the data on the ground
• Keep an ear out for feedback

breath in ...

Questions