Upgrade to Pro — share decks privately, control downloads, hide ads and more …

OpenGeoData: What, Where and Why?

OpenGeoData: What, Where and Why?

Lecture given to students of Spatial Information Science, Dublin Institute of Technology, on 23rd November 2012

Richard Cantwell

December 01, 2012

More Decks by Richard Cantwell

Other Decks in Education


  1. Open GeoData: Why, What and Where is it? Richard Cantwell

    Senior GIS Consultant / Technical Manager www.gamma.ie [email protected] @ManAboutCouch
  2. Pre rendered tiles – Range of data sources AJAX (Asynchronous

    JavaScript and XML) Open API's - Mashups Rapid development – releases every 7-10 days Google Earth Google Maps - Key Innovations http://berglondon.com/projects/hat/
  3. Restrictions: (there are many, these are just a few) Advertising

    – Google reserves the right to advertise on the map Access – APIs can only be accessed via a Google Map Content – No access to raw vector data Transaction Limits – 25,000 Map loads per day Derivative work – No copying, tracing or other modification Offline – Very limited offline use (Android phones only)
  4. Open Knowledge: “A piece of content or data is open

    if you are free to use, reuse, and redistribute it - subject only, at most, to the requirement to attribute and share-alike.” www.opendefinition.org What is Open? http://flic.kr/p/7Aqgs5
  5. opendatahandbook.org • Transparency and democratic control • Participation • Self-empowerment

    • Improved or new private products and services • Innovation • Improved efficiency & effectiveness of government services • Impact measurement of policies • New knowledge from combined data sources and patterns in large data volumes
  6. * SLA’s available from 3rd parties (€€). Self-hosting is cheap

    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) • 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) • Pricing
  7. Formats and Metadata are important.. but.. Vs A 'do-ocracy': “Build

    it and get out of the way” Top-down approach.
  8. OpenStreetMap – Tile Usage wiki.openstreetmap.org/wiki/Tile_Disk_Usage OSM does NOT pre-render every

    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 (the sea, for example) 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)
  9. OSM Wiki: wiki.openstreetmap.org OSM Help Forums: help.openstreetmap.org OSM-F Blog: blog.osmfoundation.org

    OpenGeoData Blog (OSM News): opengeodata.org Contacting Irish Mappers: Mailing List: [email protected] IRC: irc://irc.oftc.net #osm-ie or #osm (Twitter: @osm_ie) Contacting OSM