Citizen Observatories A Standards Based Architecture EGU 2015

Citizen Observatories: A Standards Based Architecture EGU 2015 Dr. Ingo Simonis Open Geospatial Consortium Europe http: //cobwebproject. eu/

Open Geospatial Consortium (OGC) 2 © 2014 Open Geospatial Consortium

Open Geospatial Consortium (OGC) 1994 Not for profit 35+ Standards 500+ Members Consensus driven

Citizens Observatories 4 © 2015 Open Geospatial Consortium slide based on work by Alex

OGC Sensor Web Enablement • Quickly discover sensors and sensor data (secure or public) that can meet my needs – location, observables, quality, ability to task • Obtain sensor information in a standard encoding that is understandable by me and my software • Readily access sensor observations in a common manner, and in a form specific to my needs • Task sensors, when possible, to meet my specific needs • Subscribe to and receive alerts when a sensor measures a particular phenomenon © 2015 Open Geospatial Consortium 5

task citizens & sensors describe citizens discover & access data describe sensors common formats describe observations

Sensors and Actuators Copyright © 2015 Open Geospatial Consortium

Sensor. ML Profile for Citizen Science • Sensor. ML is generic • Profile required to ensure interoperability – minimum set of Sensor. ML elements – structure on how to provide this minimum set of elements device who connected sensors

Sensor. ML Profile for Citizen Science • Sensor. ML is generic • Profile required to ensure interoperability – minimum set of Sensor. ML elements – structure on how to provide this minimum set of elements • Formal definition with Schematron? • Best practices without formal testing? • Simplify even more and go with JSON-LD contexts? device who connected sensors

O&M Design patterns 10

O&M Profile for Citizens Science • O&M Result is generic • Most devices are used in default settings • Profile required to enhance interoperability observation who • Formal definition with Schematron? • Best practices without formal testing? • Simplify even more and go with JSON-LD contexts? connected sensors

How Much Profile is Enough? • Often, results are first class citizens!. . . but metadata matters! • How much observation specific information do we need? • Avoid redundant information (observation centric vs. sensor centric)

Collector reads features from a WFS and proposes changes to those features. This may include proposing creation of new features. Also known as a “Data Publisher” or “The Crowd” Collector 1 5 Collector Submits Change Request 2 Reviewe r Reviewer Approves or Rejects the proposed changes Collector Reviewer is notified of notified disposition of pending of proposed Change change(s) proposals Geo. Synchronization Change Channel 3 Subscrib er 6 GSS notifies Subscribers of changes to features (i. e. Transactions) Service (GSS) Resolutio n Channel Replicati on Channel ALTERNATIVE SOLUTION 4 OGC WFS-T Approved changes are applied to features via OGC WFS-T slide by Peter Vretanos Geographic features accessible via WFS 13

Geo. Package service A Geo. Package accesses WFS’s and service (GPS) exists WMTS’s to create that creates Geo. Package. geopackages (WPS? ). Geo. Package Service WFS GSS WFS WMTS Package is created and sent to client. Client Changes client posts that makes the are be The Geo. Package A “geopackage GSS processes can makes request geopackage accepted modifications after to modified refreshed enabled” GSS from exists GPS in to servicefeatures to with get athe modified validation features in features are theposted toit the to get mediate geopackage latest Tx to as the geopackage. the to geopackage their GSS. source WFS. would accepted WFS’s. any revisions. feature. slide by Peter Vretanos

50 billions Internet-connected things by 2020 Sensors Everywhere (Things or Devices) OGC SWE-Io. T Focus

16