Transcript CoxBottsOGC_SWE

The OGC Sensor Web Enablement
framework
Simon Cox
CSIRO Exploration & Mining
Perth, Western Australia
Mike Botts
National Space Science & Technology Center
University of Alabama, Huntsville
12 December 2006
© 2006, Open Geospatial Consortium, Inc.
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
2
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
3
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
4
Sensor Web Enablement (SWE) Framework
Providers—Heterogeneous
sensor network
Airborne
Satellite
In-Situ
monitors
Surveillance
- sparse
- disparate
Users—Decision Support Tools
Bio/Chem/Rad
Detectors
- mobile/in-situ
- extensible
Models and Simulations
Sensor Web Enablement
- discovery
- access
- tasking
- alert notification
web services and
encodings based on Open
Standards
(OGC, ISO, OASIS, IEEE)
- nested
- national, regional, urban
- adaptable
- data assimilation
- vendor neutral
- extensive
M. Botts -2004
© 2006, Open Geospatial Consortium, Inc.
- flexible
- adaptable
Helping the World to Communicate
Geographically
5
Integration Of Observations
From A Variety Of Sensors
We desire the ability to discover
and integrate observations
from any sensor that meets
our needs
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
6
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
7
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
8
A common pattern: the observation model
+precedingEvent 0..*
«FeatureType»
Event
«Union»
Procedure
+
+
+followingEvent 0..*
+
+
procedureType: ProcedureSystem
procedureUse: ProcedureEvent
+procedure
eventParameter: TypedValue [0..*]
time: TM_Object
«DataType»
TypedValue
+
+
property: ScopedName
value: Any
1
AnyDefinition
+generatedObservation
0..*
+
+
+
0..*
1
AnyIdentifiableObject
«FeatureType»
Observ ation
quality: DQ_Element [0..1]
responsible: CI_ResponsibleParty [0..1]
result: Any
«ObjectType»
Phenomenon
+observedProperty
1
{Definition must be of a
phenomenon that is a property
of the featureOfInterest}
+propertyValueProvider
+featureOfInterest
«FeatureType»
AnyIdentifiableFeature
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
9
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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
10
Sensor service
• 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
Helping the World to Communicate
© 2006, Open Geospatial Consortium, Inc.
Geographically
11
SOS vs WFS, WCS, CS/W?
getFeature,
type=Observation
WFS/
Obs
getObservation
getCoverage
getResult
describeSensor
getCoverage
(result)
WCS
SOS
getFeatureOfInterest
getRecord
SOS interface is effectively a composition of
(specialised) WFS+WCS+CS/W operations
Sensor
Registry
getFeature
WFS
e.g. SOS::getResult == “convenience” interface for WCS
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
12
Applications
• 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 …
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
13
OGC SWE Status
• Specification documents
– O&M
• OGC Web Services testbeds
– OWS 4 SWE thread
• RFC Dec 2006, v1 June 2007
• ISO/TC 211 NWIP July 2007
– SensorML
• RFC June 2006, v1 March 2007
• June 2006 to December 2006
(demo last week)
– OWS 5 SWE thread
• Planning now for 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
© 2006, Open Geospatial Consortium, Inc.
Helping the World to Communicate
Geographically
14
Links + 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.
Helping the World to Communicate
Geographically
15