Dr Ingo Simonis gave this presentation at the European Geosciences Union General Assembly 13th April 2015, Vienna.

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

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

3. Open Geospatial Consortium (OGC)
© 2014 Open Geospatial Consortium3
Not for profit
35+ Standards
500+ Members
1994
Consensus driven
3

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

5. 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

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

7. Sensors and Actuators
Copyright © 2015 Open Geospatial Consortium

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

9. SensorML Profile for Citizen Science
• SensorML is generic
• Profile required to ensure interoperability
– minimum set of SensorML 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?
who
device
connected
sensors

10. 10
O&M Design patterns

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

12. 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)

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

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

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

16. 16

17. © 2015 Open Geospatial Consortium17
slide based on
work by Alex
Robin
© 2015 Open Geospatial Consortium

18. Next Steps
• Geopackage & GSS
• SWE, SWE4IoT and
SWE solutions closer
to programming code
• JSON-LD & GeoJSON
© 2015 Open Geospatial Consortium18
ReportExperiment Produce

19. © 2015 Open Geospatial Consortium19
Ingo Simonis
isimonis @ opengeospatial.org