© 2006, open geospatial consortium, inc. the ogc sensor web enablement framework simon coxmike...

© 2006, Open Geospatial Consortium, Inc.© 2006, Open Geospatial Consortium, Inc.

The OGC Sensor Web Enablement The OGC Sensor Web Enablement framework framework

Simon Cox Mike Botts

CSIRO Exploration & Mining National Space Science & Technology Center

Perth, Western Australia University of Alabama, Huntsville

12 December 2006

© 2006, Open Geospatial Consortium, Inc. 2

Helping the World to CommunicateGeographically



Sensor Web Vision -1-Sensor Web Vision -1-

• Sensors will be web accessible

• Sensors and sensor data will be discoverable

• Sensor descriptions will use a standard encoding

• Sensor observations will be delivered using standard

encodings

• Sensor observations will be accessible in real time or

from archives, to any legitimate user, over the web

with a standard request syntax



Sensor Web Vision -2-Sensor Web Vision -2-

• Sensors will be tasked in a standard way

• Sensors will be capable of issuing alerts based on observations, as well as be able to respond to alerts issued by other sensors

• Sensor services will be capable of real-time mining of observations to find phenomena of immediate interest

• Sensors and sensor nets will be able to act on their own (i.e. be autonomous)

• Software will immediately be capable of geolocating and processing observations from a newly-discovered sensor



Users—Decision Support Tools

- vendor neutral- extensive

- flexible- adaptable

Providers—Heterogeneous sensor network

In-Situ monitors

Bio/Chem/RadDetectorsSurveillance

AirborneSatellite

- sparse- disparate

- mobile/in-situ- extensible

Models and Simulations

- nested- national, regional, urban- adaptable- data assimilation

M. Botts -2004

Sensor Web Enablement

- discovery- access- tasking- alert notification

web services and encodings based on Open

Standards(OGC, ISO, OASIS, IEEE)

Sensor Web Enablement (SWE) FrameworkSensor Web Enablement (SWE) Framework



Integration Of ObservationsIntegration Of ObservationsFrom A Variety Of SensorsFrom A Variety Of Sensors

We desire the ability to discover

and integrate observations

from any sensor that meets

our needs



OGC Web Services (OWS)OGC Web Services (OWS)

• HTTP access to Geospatial informational & computational services – Web services - not web-pages!

– Web Map Service• Standard syntax for requesting a portrayed map – GetMap, GetFeatureInfo

– Web Feature Service• Fine-grained data access (XML) – GetFeature, DescribeFeatureType

– Web Coverage Service• Gridded data subsets, etc. – GetCoverage

– Catalogue Service• Structured metadata discovery and access – GetRecord

– Web Processing Service, Web Terrain Service, Coordinate Transformation Service …

• Supported by Geography Markup Language (GML) based XML data encodings– i.e. community-based content standards + interface protocols



OGC Sensor Web Enablement -1-OGC Sensor Web Enablement -1-

• Information Models & Schemas – Observations & Measurements (O&M)

• Generic observation data model, including in-situ, time-series, imagery

• “Metadata for value estimates”

– Sensor Model Language (SensorML)• Detailed description of sensors and processing chains, including

georegistration, response models

– Transducer Markup Language• Low level sensor data streaming and actuator control

• Standard GML-based encodings



«FeatureType»Observ ation

+ quality: DQ_Element [0..1]+ responsible: CI_ResponsibleParty [0..1]+ result: Any

«FeatureType»Event

+ eventParameter: TypedValue [0..*]+ time: TM_Object

«DataType»TypedValue

+ property: ScopedName+ value: Any

«Union»Procedure

+ procedureType: ProcedureSystem+ procedureUse: ProcedureEvent

AnyIdentifiableObject

«FeatureType»AnyIdentifiableFeature

AnyDefinition

«ObjectType»Phenomenon

+followingEvent 0..*+precedingEvent 0..*

+generatedObservation

0..*

+procedure 1

+observedProperty1{Definition must be of aphenomenon that is a propertyof the featureOfInterest}

+propertyValueProvider

0..*

+featureOfInterest

1

A common pattern: the observation modelA common pattern: the observation model

An Observation is an Event whose result is an estimate of the value of some Property of the Feature-of-interest, obtained using a specified Procedure

The Feature-of-interest concept reconciles remote and in-situ observations



OGC Sensor Web Enablement -2-OGC Sensor Web Enablement -2-

• Every component exposes a http interface– Supports service chain composition

– Sensor Observation Service (SOS)• Fine-grained access to sensor observation results• GetObservation( ), GetFeatureOfInterest( ), GetResult( ), DescribeSensor(id), …• XML document response

– Sensor Alert Service (SAS)• Subscription to notifications

– Sensor Planning Service (SPS)• Observation feasibility and tasking

– Sensor registries• Catalogue service profiles for sensors and services

• Hide the low-level protocols– e.g. IEEE 1451



• premises: • O&M is the high-level information model• SOS is the primary information-access interface

• SOS can serve: • an Observation (Feature)

– getObservation == “getFeature” (WFS/Obs) operation

• a feature of interest (Feature)– getFeatureOfInterest == getFeature (WFS) operation

• or Observation/result (often a time-series == discrete Coverage)– getResult == “getCoverage” (WCS) operation

• or Sensor == Observation/procedure (SensorML document)– describeSensor == “getFeature” (WFS) or “getRecord” (CSW)

operation

Sensor serviceSensor service



SOS vs WFS, WCS, CS/W?SOS vs WFS, WCS, CS/W?

WFS/Obs

getFeature, type=Observation

WCS

getCoverage

getCoverage(result)

Sensor Registry

getRecord

SOS

getObservation

getResult

describeSensor

getFeatureOfInterest

WFSgetFeature

SOS interface is effectively a composition of (specialised) WFS+WCS+CS/W operations

e.g. SOS::getResult == “convenience” interface for WCS



ApplicationsApplications

• Environmental & emergency-response scenarios– 4 × OGC interoperability testbeds 2001-2006

• Wildfire detection and reporting– NASA Ames– CSIR South Africa

• Geoscience data archives – Geochemistry (assay) & Geochronology data – Australia– Geology field observations – IUGS collaboration

• Water resources monitoring & simulation– Australia, Germany

• Oceans, Atmospheres– UK NERC

• Geophysics– Upcoming …



OGC SWE StatusOGC SWE Status

• Specification documents– O&M

• RFC Dec 2006, v1 June 2007• ISO/TC 211 NWIP July 2007

– SensorML • RFC June 2006, v1 March 2007

– TransducerML • RFC June 2006, v1 March 2007

– SOS • RFC June 2006, v1 March 2007

– SPS • RFC June 2006, v1 March 2007

– SAS • Best Practices paper

– WNS • Discussion paper

• OGC Web Services testbeds– OWS 4 SWE thread

• June 2006 to December 2006 (demo last week)

– OWS 5 SWE thread• Planning now for 2007



Links + answersLinks + answers

• SWE Updates– http://www.opengeospatial.org

• SensorML updates – – http://vast.uah.edu/SensorML

• TransducerML updates –– http://www.tml.org

• O&M updates – – http://www.seegrid.csiro.au

[email protected]

[email protected]

© 2006, open geospatial consortium, inc. the ogc sensor web enablement framework simon coxmike...

Documents

open geospatial consortium

web accessiblesensors

web terrain service

web map servicestandard

processing observations

open standardsogc

discovered sensor

sensor nets