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

12. Usage in all formats mobile / web / automotive, etc.

15. Full OpenSource tool chain available

17. Open Structures and organization (OSMF)

19. Linking of data is fine (e.g. writing reviews for a POI)15

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

28. Local search services

29. Note: Any changes to the data itself are also open-source. Linked data (e.g. reviews) is possible20

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 issues21

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 it24

43. Full stack is build on top of OpenSource software for standard solution

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

59. Every displayed map needs to display OSM attribution

61. Mixing with 3rd party data can be very hard

63. OpenGeoData Blog: http://opengeodata.org/

64. OpenStreetMapMailing Lists: http://lists.openstreetmap.org

65. OSM Wiki: http://wiki.openstreetmap.org