Dealing with historical data in OpenStreetMap
Upcoming SlideShare
Loading in...5
×
 

Dealing with historical data in OpenStreetMap

on

  • 2,012 views

A talk at WhereCampEU, Berlin about how we can improve dealing with historical data in OpenStreetMap, and why this is important.

A talk at WhereCampEU, Berlin about how we can improve dealing with historical data in OpenStreetMap, and why this is important.

Statistics

Views

Total Views
2,012
Views on SlideShare
2,012
Embed Views
0

Actions

Likes
1
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Dealing with historical data in OpenStreetMap Dealing with historical data in OpenStreetMap Presentation Transcript

  • OpenStreetMap history challenges – methods – reasons
  • Relevance of Historical Data What did the map look like two years ago? Who was involved in editing object X / region Y? What exactly happened in changeset Z?
  • Relevance of Historical Data Historical visualization Retracing vandalism Data analysis
  • OpenStreetMap consists of • nodes • ways • relations
  • • nodes• ways• relations each of those have a version and a timestamp, among other things
  • each of those have a version and a• nodes timestamp, among other things• ways• relations So in theory it’s possible to recreate the full history of all objects in OpenStreetMap
  • in practicethis is morecomplicated
  • in practicethis is morecomplicated ways and relations only have references to node IDs
  • in practicethis is morecomplicatedways andrelations this poses twoonly have problems.referencesto node IDs
  • 1. Moving a node does not cause a new way version
  • 1. Moving a node does not cause a new way version 2. References in ways and relations do not point to a specific version
  • way version 11v1 3 2 v1 v1 1. Moving a node does not cause a new way version
  • way version 1 2 v21v1 3 v1 1. Moving a node does not cause a new way version
  • 2. References in ways andrelations do not point to a specific version
  • 2. References in ways andrelations do not point to a specific version
  • 2. References in ways andrelations do not point to a specific version
  • 2. References in ways andrelations do not point to a specific version
  • Also, the data is not readily accessible
  • Also, the data is not readily accessible Full history dump is 451GB of XML, containing 1.7 billion node versions, 170 million way versions, and 4.5 million relation versions.
  • What is needed?
  • What is needed? • A suitable DB schema • PBF format support • importer (support)
  • What is needed? • A suitable DB schema • PBF format support • importer (support) .....and ideally, a history API
  • • A suitable DB schema• PBF format support• importer support (osmosis, imposm)
  • • A suitable DB schema• PBF format support• importer support (osmosis, imposm) History Hack Weekend http://bit.ly/osmhistoryhack
  • History Hack Weekendhttp://bit.ly/osmhistoryhack June 10-12 LinuxHotel Essen, Germany
  • thanks OSM > mvexeltwitter > @mvexelMartijn van Exelall photos from flickr commons