citizen science architecture: a standards based approach

®

OGC

Citizen Observatories:A Standards Based

Architecture

Dr. Ingo SimonisDirector, Interoperability Programs & Science, OGC

May 2015

© 2015 Open Geospatial Consortium

OGC®

Considerations

© 2015 Open Geospatial Consortium 2

Cost efficient

OGC®

Considerations

3

Research efficient

OGC®

4

State of the Art

OGC®


OGC®


Geonovum HeronViewer showing components with time series values

OGC®


52North JS-SensorWeb-Client

OGC®


app made with SOS-JS by British Antarctic Survey (Map)

OGC®


OGC®

14

State of the Art

OGC®


citizen

scientist

consumer

COBWEB

OGC®


Hypermedia

HTTP

URI

OGC®


citizen COBWEB

OGC®


COBWEBcitizen

Hypermedia

HTTP

URI

OGC®


citizen COBWEB

POX over HTTP

OGC®


citizen COBWEB

<Observation> <id>Citizen1</ID> <val>23.2</val></Observation>

OGC®


citizen COBWEB

POST /Insert HTTP/1.1Content-Type: application/xmlHost: ingos-server.comContent-Length: 48


HTTP/1.1 200 OKContent-Type: application/xml

Content-Length: 28Server: Microsoft-HTTPAPI/2.0

Date: Sun, 10 May 2015 17:13:45

<ObservationConfirmation> <id>obs23764523</id>

</ObservationConfirmation>

OGC®


citizen COBWEB

POX tunneling over HTTP

+ Lightweight+ Easy to implement+ Universally

interoperable+ Firewall friendly+ Single URI

- Ignores the Web platform

- HTTP verbs barely used- Reliability and

scalability?- Extend to many

receivers?

OGC®


COBWEBcitizen

Hypermedia

HTTP

URI

OGC®


citizen COBWEB

resources

CRUDservices

OGC®


citizen COBWEB

Think in resourcesUse proper HTTP verbs

POST

GET

PUT

DELETE

/obs

/obs/{id}

/obs/{id}

/obs/{id}

create new observation

request current state

update observation

delete observation

OGC®


citizen COBWEB

POST /obs HTTP/1.1Host: ingos-server.comContent-Type: application/xmlContent-Length: 48



Content-Length: 28Date: Sun, 10 May 2015 17:34:11

<Observation> <id>obs237</ID></Observation>

OGC®


citizen COBWEB

GET /obs/obs237 HTTP/1.1Host: ingos-server.com


Content-Length: 28Date: Sun, 10 May 2015 17:13:45


OGC®


citizen COBWEB

PUT /obs/obs237 HTTP/1.1Host: ingos-server.comContent-Type: application/xmlContent-Length: 48


HTTP/1.1 204 No ContentDate: Sun, 10 May 2015 17:56:45

OGC®


citizen COBWEB

DELETE /obs/obs237 HTTP/1.1Host: ingos-server.com

HTTP/1.1 204 No ContentDate: Sun, 10 May 2015 17:58:45

OGC®


Hypermedia

HTTP

URI

OGC®


citizen

scientist

consumer

COBWEB

OGC®


citizen

scientist

consumer

COBWEB

POST /obs HTTP1.1…

HTTP1.1200 OK

OGC®


citizen

scientist

consumer

COBWEB


HTTP1.1 200 OK…

OGC®


citizen

scientist

consumer

COBWEB


Link t

oHTTP1.1 200 OK…

OGC®


Hypermedia

HTTP

URI

OGC®


citizen

scientist

consumer

COBWEB


Link t

o Link to

GET/obs/3 HTTP1.1…

HTTP1.1 200 OK…

Link toHTTP1.1 200 OK…

OGC®


Hypermedia

HTTP

URI

OGC®


Hypermedia with semantic mark up

HTTP

URI

OGC®


Hypermedia with semantic mark up:

Raw observation

<Observation> <id>Citizen1</ID> <val>18.6</val></Observation><Campaign>…

Corrected observation

<Observation> <id>Citizen1</ID> <cp>fgr7</cp> <val>18.2</val></Observation><RawObservation>…Sampling campaign

<CampaignID>c2<..> <observation> … </..> <observation> … </..> …</CampaignID>c2<..>

Link to

Link to

Link to

OGC®


Hypermedia with semantic mark up: DAP

Raw observation





Link to

Link to

Link to

OGC®


DAP: Domain Application Protocol

Raw observation





Link to

Link to

Link to

• URI structure becomes irrelevant

• Links from one resources to the

other are part of the resources;

decreases coupling

• Protocol information just-in-time

OGC®


OGC®


Human Web

• embedded links

• href=“http://…”

Cart

Computer-to-Computer

• annotations

(hypermedia

controls)

• micro formats or

Semantic Web

technologies

OGC®

Forms as hypermedia controls


Value: 25.7Unit: deg Celsius

Submit


<Observation> <id>ingo</ID> <val>25.7</val> <uom>degCelsius</uom></Observation>

Plain XML

OGC®


<Observation> <id>ingo</ID> <val>25.7</val> <uom>degCelsius</uom></Observation>

Forms as hypermedia controls


Value: 25.7Unit: deg Celsius

Submit

GET /obs/o237 HTTP/1.1Host: ingos-server.com

<Observation> <id>o237</ID> <citizen>ingo</citizen> <val>25.7</val> <uom>degCelsius</uom> <status>raw</status> <link rel=“http://cobweb.org/campaign” campaign>http://i.org/campaigns/c2</campaign> <link rel=“http://cobweb.org/citizen” citizen>http://i.org/citizens/ingo</citizen></Observation>

XML with hypermedia link

OGC®

Media Types and Domain Application Protocols


HTTP/1.1 200 OKContent-Type: application/vnd.cobweb+xml

<Observation> <id>o237</ID> <citizen>ingo</citizen> <val>25.7</val> <uom>degCelsius</uom> <status>raw</status> <link rel=“http://cobweb.org/campaign” campaign>http://i.org/campaigns/c2</campaign> <link rel=“http://cobweb.org/citizen” citizen>http://i.org/citizens/ingo</citizen></Observation> XML with

hypermedia link and media type

OGC®

Media Types and Domain Application Protocols


HTTP/1.1 200 OKContent-Type: application/vnd.cobweb+xml

<Observation> <id>o237</ID> <citizen>ingo</citizen> <val>25.7</val> <uom>degCelsius</uom> <status>raw</status> <link rel=“http://cobweb.org/campaign” campaign>http://i.org/campaigns/c2</campaign> <link rel=“http://cobweb.org/citizen” citizen>http://i.org/citizens/ingo</citizen></Observation>

how to process this data

(needs to be developed)

XML with hypermedia link and media type

OGC®


citizen

scientist

consumer

COBWEB

OGC®


citizen

scientist

consumer

COBWEB

Syndication

OGC®

Citizen Science: A Syndication Model

Atom: Feeds (lists) with time-stamped entries


OGC®

Citizen Science: A Syndication Model

• Atom Publishing Protocol: – Syndication content: observations

to consumers– Representing document-like

structures: observation model– Meta-data rich lists of resources:

observation provenance– Adding metadata to existing

resource representations• incl. attach hypermedia links

– Creating directories of non-hypermedia content• e.g. binary data


OGC®


citizen

scientist

consumer

COBWEB

OGC®


citizen

scientist

consumer

COBWEB

raw QA log

OGC®


OGC®

GeoSynchronization Service (GSS)

Replication

Channel

Change Channel

Resolution

Channel

GSS IN ACTION

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

4Approved 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 Reviewer

Subscriber

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.

59slide by Peter Vretanos

OGC®


OGC®


Geopackage

creation

Geopackage

usage

GSS

SOSWFS

SOSWFS

SOS, WFS, WCS, WMS

OGC®


JaxB, Jersey, Rome

Observation profile

Sensor profile

OGC®


Ingo [email protected]

OGC®

ARCHITECTURE DETAILSCOBWEB Standards Based


OGC®


citizen science architecture: a standards based approach

Software

open geospatial consortium

ogc considerations

ogc citizen observatories

citizen cobweb citizen123

citizen cobweb pox

citizen cobweb post

content date

applicationxml contentlength