Fosdem 2010 GT.M and OpenStreetMap

  • 3,912 views
Uploaded on

Geodata in a schemafree database. Using GT.M to implement XAPI for OpenStreetMap.

Geodata in a schemafree database. Using GT.M to implement XAPI for OpenStreetMap.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,912
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
21
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. GT.M and OpenStreetMap Geodata in a schema-free database FOSDEM 2010 :: Brussels :: February 7th, 2010
  • 2. OpenStreetMap
      • A free map of the planet
        • Free geospatial data
        • Licensed under CC-BY-SA
      • Created from
        • Crowd-sourced contributions
        • 200,000 registered users
        • 1,000+ contributors per day
      • Used for:
        • Maps
        • Navigation / routing
        • OpenCycleMap.org
        • OpenPisteMap.org
        • iPhone apps
        • Android apps
        • Crisis mapping
    © Constantin Litvak
  • 3. Coverage CC-BY-SA 2.0 © OpenStreetMap
  • 4. Earthquake!
  • 5. Haiti – January 12 th 2010
  • 6. Haiti – January 14 th 2010
  • 7. What's GT.M?
      • Schemaless database
      • Key/value pairs
      • Mature
      • Mission critical - banking
      • Mission critical - healthcare
      • Layered SQL, OODB, M/DB, etc
  • 8. The OpenStreetMap database
      • Nodes: 0.5 billion
      • Ways: 25 million
      • Relations: 100,000
      • Tags
      • highway=motorway
      • name=Brussels
      • amenity=zoo
      • foo=bar
      • REST based API
  • 9. Data Schema
  • 10. The Main OpenStreetMap Database Server
      • 2 x Intel Xeon Quad Core 2.5Ghz
      • 10 x 450Gb 15k rpm
      • 32 GB ram
      • PostgreSQL 8.3
      • One capability:
      • Query by area
    • 0.25 ² degrees
  • 11. The OpenStreetMap XAPI Server
      • XAPI = Extended API
      • 1 x Athlon 64 3000+
      • 2 x 300Gb 10k rpm
      • 4 GB ram
      • GT.M 4.3
      • Capabilities:
      • Query by area
      • Query by tag
  • 12. Quadstrings
      • Geospatial Index
    adaabcdcabaadab
  • 13. GT.M Data
    • ^way(27016525)="adaabcdcabaadab"
    • ^way(27016525,1)=296138118
    • ^way(27016525,2)=296138119
    • ^way(27016525,3)=296138120
    • ^way(27016525,4)=296138121
    • ^way(27016525,5)=296138118
    • ^waytag(27016525,"addr:housenumber")=2
    • ^waytag(27016525,"building")="yes"
    • ^wayx("building","*","adaabcdcabaadab",27016525)=""
    • ^wayx("building","*","adaabcdcabaadab",27028298)=""
    • ^wayx("building","*","adaabcdcabaadab",27028299)=""
    • ^wayx("building","*","adaabcdcabaadab",27028326)=""
    • ^wayx("building","*","adaabcdcabaadab",27028327)=""
    • ^wayx("building","*","adaabcdcabaadab",27035972)=""
    • ^wayx("building","*","adaabcdcabaadab",27035973)=""
    • ^wayx("building","*","adaabcdcabaadab",27035974)=""
    • ^wayx("building","*","adaabcdcabaadab",27035975)=""
    • ^wayx("building","*","adaabcdcabaadab",27035984)="“
    <way id='27016525'> <nd ref='296138118'/> <nd ref='296138119'/> <nd ref='296138120'/> <nd ref='296138121'/> <nd ref='296138118'/> <tag k='addr:housenumber' v='2'/> <tag k='building' v='yes'/> </way>
  • 14. Conclusion
      • GT.M is good for:
      • Massive datasets
      • High performance on low end hardware
      • Robust and mature
      • Highly adapatable
      • NoSQL
  • 15. Thank you
    • openstreetmap.org
    • fis-gtm.com
    • georgejames.com
    • Questions?
    CC-BY-SA 2.0 Image © ITO! Data © OpenStreetMap