OpenStreetMap history    challenges – methods – reasons
Relevance of Historical Data    What did the map look     like two years ago?      Who was involved in     editing object ...
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 i...
in practicethis is morecomplicated
in practicethis is morecomplicated    ways and               relations               only have               references   ...
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          sp...
way version 11v1                               3                2                                 v1                v1    ...
way version 1                   2                   v21v1                               3                                 ...
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 versio...
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 ideall...
• 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...
History Hack Weekendhttp://bit.ly/osmhistoryhack        June 10-12        LinuxHotel      Essen, Germany
thanks  OSM > mvexeltwitter > @mvexelMartijn van Exelall photos from flickr commons
Dealing with historical data in OpenStreetMap
Upcoming SlideShare
Loading in...5
×

Dealing with historical data in OpenStreetMap

1,637

Published on

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

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,637
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \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

    1. 1. OpenStreetMap history challenges – methods – reasons
    2. 2. 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?
    3. 3. Relevance of Historical Data Historical visualization Retracing vandalism Data analysis
    4. 4. OpenStreetMap consists of • nodes • ways • relations
    5. 5. • nodes• ways• relations each of those have a version and a timestamp, among other things
    6. 6. 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
    7. 7. in practicethis is morecomplicated
    8. 8. in practicethis is morecomplicated ways and relations only have references to node IDs
    9. 9. in practicethis is morecomplicatedways andrelations this poses twoonly have problems.referencesto node IDs
    10. 10. 1. Moving a node does not cause a new way version
    11. 11. 1. Moving a node does not cause a new way version 2. References in ways and relations do not point to a specific version
    12. 12. way version 11v1 3 2 v1 v1 1. Moving a node does not cause a new way version
    13. 13. way version 1 2 v21v1 3 v1 1. Moving a node does not cause a new way version
    14. 14. 2. References in ways andrelations do not point to a specific version
    15. 15. 2. References in ways andrelations do not point to a specific version
    16. 16. 2. References in ways andrelations do not point to a specific version
    17. 17. 2. References in ways andrelations do not point to a specific version
    18. 18. Also, the data is not readily accessible
    19. 19. 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.
    20. 20. What is needed?
    21. 21. What is needed? • A suitable DB schema • PBF format support • importer (support)
    22. 22. What is needed? • A suitable DB schema • PBF format support • importer (support) .....and ideally, a history API
    23. 23. • A suitable DB schema• PBF format support• importer support (osmosis, imposm)
    24. 24. • A suitable DB schema• PBF format support• importer support (osmosis, imposm) History Hack Weekend http://bit.ly/osmhistoryhack
    25. 25. History Hack Weekendhttp://bit.ly/osmhistoryhack June 10-12 LinuxHotel Essen, Germany
    26. 26. thanks OSM > mvexeltwitter > @mvexelMartijn van Exelall photos from flickr commons
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×