17
Sensor Observation Service for the GeoEvent Extension Benjamin Proß, Matthes Rieke, Sebastian Drost (52°North GmbH, Münster, Germany) Marten Hogeweg (ESRI Inc.) ESRI UC 2017 Making sensor data come alive

Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

  • Upload
    lamminh

  • View
    222

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for

the GeoEvent Extension

Benjamin Proß, Matthes Rieke, Sebastian Drost(52°North GmbH, Münster, Germany)

Marten Hogeweg(ESRI Inc.)

ESRI UC 2017

Making sensor data come alive

Page 2: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 2

Motivation

Page 3: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 3

Intentions

• Sensor Web technologies are increasingly used

– Several sensor data providers and SOS instances

• NOAA, IOOS, NANOOS

• USGS

• German Federal Waterways Administration

• Air quality measurements in Europe

• Accessibility of near real-time sensor data for the ArcGIS

platform is required

Page 4: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 4

Sensor Web Background

Page 5: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 5

Observations & Measurements

• Used for encoding data observed by sensors

• Observation comprises– Timestamp

– Value (if applicable including unit of measurement)

– Observed property

– Feature of interest

• O&M 2.0 data model approved as an ISO standard

• O&M 2.0 XML encoding approved as an OGC standard

Page 6: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 6

Sensor Observation Service

• Pull-based access to observations

• Mediator between:

– client data archive / simulation / real-time

sensor system

• Hides the heterogeneous structure of proprietary

sensor data formats and protocols

• Data formats: O&M and SensorML

• Versions: 1.0 and 2.0

Page 7: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 7

Approach

• Use of the ArcGIS GeoEvent Extension for Server

– Requesting sensor data from an OGC Sensor Observation

Service (SOS)

– Processing and filtering sensor data

– Transfer sensor data to different endpoints (e.g. Feature-

Service, Stream-Service)

• Requirements:

– Development of an Input Connector for requesting a SOS

Page 8: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 8

Architecture

SOS

Feature-

Service

Output

Adapters

GeoEvent Extension

Filters

Processors

SOS Input

Connector

SOS Transport

SOS Adapter

HTTP

Stream-

Service

Page 9: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 9

SOS Input Connector

SOS Inbound

Transport

SOS Inbound

Adapter

Byte [ ]

Observation

Parameters:

● SOS URL

● Offering

● Observed Property

● Procedure

Request Parameters:

● Request Interval

● Initial Request GeoEvent

JAXB

GeoEvent

Definition

Byte [ ]

deserializing

XML parsing

GeoEvent

creation

Page 10: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 10

SOS Input Connector

Page 11: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 11

SOS Inbound Transport

• Use of a polling mechanism to request and receive

sensor data from an SOS server

– Request interval as a parameter

• Requests only new data that was available since the last

request

• Time filter as a request parameter

http://www.pegelonline.wsv.de/webservices/gis/sos?request=GetObservation&observedProperty=Wasserstand&(...)&eventTime=2017-02-13T12:30:00.000/2017-02-13T12:45:00.000&(...)

Page 12: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 12

SOS Inbound Transport

• Process flow of the SOS Inbound Transport

2nd request:

Start: T1

End: current time

SOS Adapter

latestsampling Time

T1

latestsampling Time

T2

latestsampling Time

T2

3rd request:

Start: T2

End: current time

initial request:

Start: n days ago

End: current time

current time

- n days ago

Page 13: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 13

SOS Inbound Transport

• Time filter very important for retrieving data– Observations consist of two timestamps:

• resultTime and phenomenonTime

1. Data could arrive later in the database resultTime > phenomenonTime

2. If data is requested periodically,observations can be missed

Connector considers the phenomenonTimeof previously retrieved data to create thetime filter for the next period

1

2

3

Page 14: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 14

Visualization

• Water level observation with the Operations Dashboard

Page 15: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 15

Demonstration

• Demo video

Page 16: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Sensor Observation Service for the GeoEvent Extension 16

Next Steps

• Integration with additional SOS instances available for

public use

– NOAA Oceanology data

– IOOS Oceanology data

– European Air Quality data

• Making the SOS Adapters Open Source

– requires additional testing

Page 17: Sensor Observation Service for the GeoEvent Extension - Esriproceedings.esri.com/library/userconf/proc17/papers/1853_168.pdf · Sensor Observation Service for the GeoEvent Extension

Thanks for your attention!

Benjamin Proß ([email protected])

Matthes Rieke ([email protected])

Sebastian Drost ([email protected])

Marten Hogeweg ([email protected])

Any Questions?