1. SDI 4.0 Crowd-sourcing, Gov-sourcing Geographic Data via Open Geosynchronization Raj R. Singh Director, Interoperability Programs Open Geospatial Consortium

2. Agenda Who is OGC, and why do I care? SDIs and their problems Geosynchronization: good SDI medicine

3. OPEN GEOSPATIAL CONSORTIUM

4. What is the OGC? Not-for-profit, international standards development consortium Not-for-profit, international standards development consortium 375+ industry, government, and university members 375+ industry, government, and university members Specification Development Program (since 1994) Specification Development Program (since 1994) – Class A liaison with ISO/TC211 – 18 Implementation Standards, with additional standards profiles, and best practice documents… – 20+ candidate Implementation Standards in progress – OGC Reference Model defines interoperable geo architecture 4 Mission To advance the development and market adoption of open standards for geospatial interoperability.Mission Interoperability Program (since 1999)Interoperability Program (since 1999) –A global, innovative, hands-on engineering and testing program designed to accelerate interface development and bring interoperability to the market Outreach and Community Adoption Program (since 2002)Outreach and Community Adoption Program (since 2002) –Awareness raising, education and training, encourage take up of OpenGIS® specifications, business development

5. OGC Standards Database – Simple Feature Access – OLE, SQL, CORBA {ISO} Web Services  Web Map Service (WMS) {ISO}  Web Feature Service (WFS) {ISO}  Web Coverage Service (WCS)  Catalog Services for the Web (CS/W)  Sensor Observation Service (SOS) XML Encodings  Geography Markup Language (GML) {ISO}  KML  Web Map Context  SensorML 5 Available free of charge at http://opengeospatial.org/standards

6. OGC-based Policy Positions USGS Framework Features served with WFS and WMS Canada Geospatial Data Infrastructure (CGDI) Implements OGC Web Service Specifications UK Ordnance Survey using GML format to distribute its MasterMap product European Union INSPIRE technical architecture built around OGC specifications Numerous OGC standards on the DISR with NGA adoption CIA and DHS have adopted OGC as part of their Geospatial Enterprise Architectures 6

7. A FRAMEWORK FOR UNDERSTANDING (S)DIS 7

8. Characteristics of an (S)DI Group of loosely affiliated organizations coming together to pursue a shared interest Benefits and costs are spread unevenly across parties No central point of control or authority The infrastructure has little value without broad, sustained participation 8

9. Why don’t (S)DI work better Too much sustained human involvement required Sharing takes (high cost) labor every time something changes Cost, cost, cost! 9

10. An (S)DI Maturity Path 10

11. GEO-SYNCHRONIZATION

12. Two-Party Synchronization Two parties synchronize layer A is shared then make edits layer A changes in both systems then synchronize again layer A is the same again uses: neighboring states, counties or municipalities

13. Hierarchical Synchronization Copyright © 2009 Carbon Project Inc. uses: closest-to-source updates, SDIs

14. Field Worker Synchronization Field workers leave HQ with a copy of layer A layer A is shared Field workers make edits in the field layer A changes in both field systems Some sync in the field military/disaster use case—some devices don’t make it back to HQ Some field workers might make more edits Everyone returns to HQ and syncs seamlessly layer A is the same again uses: resilient systems, crowdsourcing

15. spatial database “Big” data requests vs. update requests WFS adapter WFS client WFS request: give me all the parcels in town X spatial database GeoSync adapter GeoSync client GeoSync request: give me all changes to the parcels in town X since time T new data change log

16. How GeoSync works A Server publishes 2 things: o a Web Feature Service (the latest data set) o a “change feed” A Client: o queries the WFS once for the data it wants o then queries the change feed for updates

17. Atom Publication Protocol …for publishing and editing Web resources belonging to periodically updated websites. The protocol at its core is the HTTP transport of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format (draft-ietf-atompub-format-06.txt).

18. Feature Layers on Remote Servers are registered for synchronization Publisher Submits Change Request Reviewer Approves or Rejects the Change 4 4 Inform Publisher of Approved or Rejected Changes Update Approved Changes on Registered Layers using generated WFS Transactions 6 6 Inform Followers of Changes Inform Reviewer of Change Request 2 2 Publisher creates or changes features on a registered layer CloudSync Services Registered Layers Layer A A0A0 A1A1 AnAn Schema transposition templates 5 5 1 1 3 3 Copyright © 2009 Carbon Project Inc.

19. Geosynchronization Next Steps Public comment on version 1.0 Get your vendors to implement it In procurements…ask for it by name! learn more “OWS 7 Engineering Report - Geosynchronization service” OGC 10-069r2 on http://www.opengeospatial.org/standards/per or direct download: http://portal.opengeospatial.org/files/?artifact_id=39476 http://www.opengeospatial.org/standards/perhttp://portal.opengeospatial.org/files/?artifact_id=39476 Geosync videos: http://www.opengeospatial.org/pub/www/ows7/index.htmlhttp://www.opengeospatial.org/pub/www/ows7/index.html WFS & WFS-T: http://www.opengeospatial.org/standards/wfshttp://www.opengeospatial.org/standards/wfs ask me anything: o rsingh@myogc.org rsingh@myogc.org o +1 (617) 642 9372