Presentation at #OpenDataIRL by Richard Cantwell (@ManAboutCouch)
OpenStreetMap is rapidly gaining traction in the Geo space. What is it? How does it compare to other sources of GeoData? How can you use it, and how can you help make it even better?
but can be complex. OpenStreetMap • API’s aimed at data editors • Limited API functionality • No ‘Service Level Agreements’* • ‘Viral’ nature of data licence • Focus on map data • ‘Warm Geography’ • Instant data updates, Sporadic • ‘Depth’ Issues (coverage, completeness) • Weak Metadata Other Data Providers: • API’s aimed at data consumers • Extensive API functionality • SLA’s available (but €€) • Derived data issues • Focus on services • ‘Cold Geography’ • Moderated update process, Consistent • ‘Width’ issues (limited featureset) • Expensive
tile. Pre-rendering all tiles would use around 54,000 GB of storage. The majority of tiles are never viewed. In fact just 1.79% have ever been viewed. This is because the majority of tiles are at zoom level 18 and the vast majority of those contain nothing of interest (they're entirely blue) By following an on-the-fly rendering approach we can avoid rendering these tiles unnecessarily. The tile view count column shows how many tiles have been produced on the OSM Tile server. Tile server disk usage: 1,272 GB used. (6 Jan 2012). (z0 to z15: 252 GB, z16 to z18: 1,020 GB)