1<br />Using OpenStreetMap data for Location Based Service Apps<br />Philipp Kandal<br />17th June 2011<br />
2<br />About skobbler<br />
3<br />skobbler is all about Maps!<br />Creative Commons Attribution-ShareAlike 2.0 licence (CC-BY-SA).<br />
4<br />skobbler has been a resounding success with over 1 Mio. Customers on OpenStreetMap data!<br />The skobbler Market P...
5<br />OpenStreetMap in a Nutshell<br />
6<br />OSM isthe Wikipedia ofMapsand will makeothermaps obsolete<br />Creative Commons Attribution-ShareAlike 2.0 licence ...
OSM shows impressive growth<br />7<br />
Growth of Nodes, Ways and Relations<br />8<br />
OSM is fully flexible and not a hierarchical map. Anybody can map anything<br />9<br />Streets<br />Locations<br />Public ...
10<br />Key benefits and risks of OpenStreetMap<br />
11<br />The map is free<br /><ul><li>No license costs
Usage in all formats mobile / web / automotive, etc.
Proprietary tech can be used (not data!)</li></li></ul><li>12<br />The map is very feature rich<br />Creative Commons Attr...
13<br />OSM is flexible – it was never targeted for only one single use-case<br /><ul><li>Tag based structure vs. hierarch...
Full OpenSource tool chain available
Advantage and issue at the same time</li></li></ul><li>14<br />Community driven project<br /><ul><li>Over 400k contributors
Open Structures and organization (OSMF)
Issue: No (formal) quality assurance of map</li></li></ul><li>15<br />Viral nature of license<br /><ul><li>The OSM license...
Linking of data is fine (e.g. writing reviews for a POI)</li></ul>15<br />
16<br />Legal risks<br /><ul><li>OSM community watches carefully over Copy-and-Paste from other maps
Nobody can guarantee that it’s free of copyrighted data
Mixing your data in makes it OpenSource as well
OSM data can have significant issues (e.g. broken highways) which for navigation could cause safety issues (theoretical ri...
17<br />Use-cases for OpenStreetMap data<br />
18<br />Navigation / Maps (GoogleMaps alternative)<br />
19<br />Customized routing for groups which traditionally can not navigate with commercial maps<br />Wheelchair<br />Bicyc...
20<br />Open: Points of Interest / Locations database<br /><ul><li>Could become core location database for services like 4...
Local search services
Note: Any changes to the data itself are also open-source. Linked data (e.g. reviews) is possible</li></ul>20<br />
21<br />GeoCoding<br /><ul><li>Searching for addresses (e.g. Berlin, Unter den Linden 3)
Location search (e.g. Berlin, Brandenburg Gate)
Searching for cities (e.g. Berlin)
Quick reference:
Cities are mapped excellent in OSM
Streets are mapped very well in most countries
House-Numbers are serious issues</li></ul>21<br />
22<br />Business intelligence<br /><ul><li>Very feature rich map incl. pedestrian path ways, public transport and many oth...
24<br />Note: OSM API <> Google Maps API<br />OSM APIs are not built for businesses!<br /><ul><li>OSM APIs provide no leve...
They are not targeted for end-consumer use
They provide limited customization options
OSM APIs are mostly for editing the map not for consuming it</li></ul>24<br />
For commercial use: Build your own stack or use 3rd parties<br /><ul><li>Calculate if build or buy is cheaper
Full stack is build on top of OpenSource software for standard solution
Upcoming SlideShare
Loading in …5
×

Using OpenStreetMap data for Location Based Service Apps

4,201 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,201
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Using OpenStreetMap data for Location Based Service Apps

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

×