Your SlideShare is downloading. ×
Using OpenStreetMap data for Location Based Service Apps
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Using OpenStreetMap data for Location Based Service Apps

3,171
views

Published on

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,171
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
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. 1
    Using OpenStreetMap data for Location Based Service Apps
    Philipp Kandal
    17th June 2011
  • 2. 2
    About skobbler
  • 3. 3
    skobbler is all about Maps!
    Creative Commons Attribution-ShareAlike 2.0 licence (CC-BY-SA).
  • 4. 4
    skobbler has been a resounding success with over 1 Mio. Customers on OpenStreetMap data!
    The skobbler Market Performance.
    One of the the 10 most successful paid iPhone apps in Germany in 2009
    Top selling paid iPhone app in Germany for several weeks
    18 months top selling iPhone navigation app in Germany since its market launch
    Top grossing iPhone app in
    Germany for several days
  • 5. 5
    OpenStreetMap in a Nutshell
  • 6. 6
    OSM isthe Wikipedia ofMapsand will makeothermaps obsolete
    Creative Commons Attribution-ShareAlike 2.0 licence (CC-BY-SA).
  • 7. OSM shows impressive growth
    7
  • 8. Growth of Nodes, Ways and Relations
    8
  • 9. OSM is fully flexible and not a hierarchical map. Anybody can map anything
    9
    Streets
    Locations
    Public transport
    Creative Commons Attribution-ShareAlike 2.0 licence (CC-BY-SA).
  • 10. 10
    Key benefits and risks of OpenStreetMap
  • 11. 11
    The map is free
    • No license costs
    • 12. Usage in all formats mobile / web / automotive, etc.
    • 13. Proprietary tech can be used (not data!)
  • 12
    The map is very feature rich
    Creative Commons Attribution-ShareAlike 2.0 licence (CC-BY-SA).
  • 14. 13
    OSM is flexible – it was never targeted for only one single use-case
    • Tag based structure vs. hierarchy based
    • 15. Full OpenSource tool chain available
    • 16. Advantage and issue at the same time
  • 14
    Community driven project
    • Over 400k contributors
    • 17. Open Structures and organization (OSMF)
    • 18. Issue: No (formal) quality assurance of map
  • 15
    Viral nature of license
    • The OSM license current (CC-BY-SA) and the new license (ODBL) don’t allow mixing with commercial data (layered rendering is possible)
    • 19. Linking of data is fine (e.g. writing reviews for a POI)
    15
  • 20. 16
    Legal risks
    • OSM community watches carefully over Copy-and-Paste from other maps
    • 21. Nobody can guarantee that it’s free of copyrighted data
    • 22. Mixing your data in makes it OpenSource as well
    • 23. OSM data can have significant issues (e.g. broken highways) which for navigation could cause safety issues (theoretical risk)
    16
  • 24. 17
    Use-cases for OpenStreetMap data
  • 25. 18
    Navigation / Maps (GoogleMaps alternative)
  • 26. 19
    Customized routing for groups which traditionally can not navigate with commercial maps
    Wheelchair
    Bicycle
    Pedestrian
    19
  • 27. 20
    Open: Points of Interest / Locations database
    • Could become core location database for services like 4sq, GoWalla, Facebook places
    • 28. Local search services
    • 29. Note: Any changes to the data itself are also open-source. Linked data (e.g. reviews) is possible
    20
  • 30. 21
    GeoCoding
    • Searching for addresses (e.g. Berlin, Unter den Linden 3)
    • 31. Location search (e.g. Berlin, Brandenburg Gate)
    • 32. Searching for cities (e.g. Berlin)
    • 33. Quick reference:
    • 34. Cities are mapped excellent in OSM
    • 35. Streets are mapped very well in most countries
    • 36. House-Numbers are serious issues
    21
  • 37. 22
    Business intelligence
    • Very feature rich map incl. pedestrian path ways, public transport and many other transportation options
  • 23
    OpenStreetMap APIs
  • 38. 24
    Note: OSM API <> Google Maps API
    OSM APIs are not built for businesses!
    • OSM APIs provide no level of service
    • 39. They are not targeted for end-consumer use
    • 40. They provide limited customization options
    • 41. OSM APIs are mostly for editing the map not for consuming it
    24
  • 42. For commercial use: Build your own stack or use 3rd parties
    • Calculate if build or buy is cheaper
    • 43. Full stack is build on top of OpenSource software for standard solution
    • 44. Use a pay-as-you go stack for quick start-up and if no extensive customization is needed (free basic usage)
  • 26
    Rest based XML APIs
    Full access in real-time
    Interface for both exporting and importing data
    Very slow
    Limited to smaller areas
    Not 100% stable
    26
  • 45. Fast
    Global
    Very stable
    Big data size
    Only weekly available (deltas are available)
    27
    Weekly database extracts
    27
  • 46. 28
    Third Party APIs
  • 47. 29
    Open.MapQuest.com
    Free for developers
    Based on standard tool-chain (Mapnik, etc.)
    No styling options of map
    No commercial service levels
    29
  • 48. Great MapStyle tools
    Great WebMaps API
    Relatively expensive (alternative ad-based solution possible)
    Based on proprietary solution (which makes transition harder)
    30
    Cloudmade
    30
  • 49. Cross map supplier libraries
    Powerful customizations possible
    Very expensive
    Difficult to integrate
    Proprietary technology
    31
    DeCarta
    31
  • 50. 32
    Bing
    Free
    Powerful libraries (especially for web)
    Alternative Navteq Map available
    Restriction in use-cases (e.g. no navigation)
    No OSM style editing tools
    32
  • 51. 33
    Related OpenSource projects
  • 52. 34
    MapNik
    Best Open MapRenderer
    Lots of standard styles available
    Very actively maintained
    No vector maps
    Performance intensive for big applications
    34
  • 53. 35
    OpenLayers
    Best Open Web-Maps API
    Powerful plugin system
    Quite big codebase
    Sluggish performance compared to Google Maps
    35
  • 54. 36
    Routeme
    iOS- Client side rendering library (Note: Not routing library)
    Can be used with any tile provider
    Only tile based maps and no vector map support
    36
  • 55. 37
    Tilemill
    Map editing toolkit
    Optimized for big production load
    Hosted solution for easy setup available
    Complex installation with lots of dependencies
    37
  • 56. Full server side routing
    High performance
    Extendable for different routing types
    Only basic routing concepts implemented
    Doesn’t work on client side routing
    38
    OpenSourceRouting Machine
    38
  • 57. 39
    OSM license requirements
  • 58. 40
    Attribution
    • Creative Commons license (new: ODBL)
    • 59. Every displayed map needs to display OSM attribution
    • 60. Play nice with the community as the put a lot of effort in creating the map
  • 41
    OpenSource
    • Viral issues with map
    • 61. Mixing with 3rd party data can be very hard
    • 62. Respect the community and plan to share back
  • Good further readings on this topic
    • Abalakov’s thoughts on OSM: www.abalakov.com
    • 63. OpenGeoData Blog: http://opengeodata.org/
    • 64. OpenStreetMapMailing Lists: http://lists.openstreetmap.org
    • 65. OSM Wiki: http://wiki.openstreetmap.org
    • 66. MapQuest dev blog: http://devblog.mapquest.com
  • THANK YOUfor your kind attention!Get in touch: Philipp Kandal, philipp.kandal@skobbler.com Mobile: +49 172 4597015
    Follow me on
    .com/apphil