ows-4 swe overview 28 november 2006 @nist mark reichardt / george percivall / john davidson

23
OWS-4 SWE Overview OWS-4 SWE Overview 28 November 2006 28 November 2006 @NIST @NIST Mark Reichardt / George Percivall / John Davidson

Upload: sydney-green

Post on 13-Jan-2016

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

OWS-4 SWE Overview OWS-4 SWE Overview

28 November 200628 November 2006@NIST@NIST

Mark Reichardt / George Percivall / John Davidson

Page 2: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

TopicsTopics

• OGC Process• OWS-4 SWE Project Participants• OWS-4 CONOPS and Use Cases• SWE Specification Baseline • SWE Information Model• SWE Service Model• OWS-4 SWE Demo Overview

Page 3: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OGC Process – Iterative DevelopmentOGC Process – Iterative DevelopmentYielding Tested SpecificationsYielding Tested Specifications

Page 4: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OWS-4 SWE Participants and StakeholdersOWS-4 SWE Participants and Stakeholders

• POP: – 6months (May -> December 2006)

• Participants– 3eTI– CSIRO-EM– CSIRO-ICT– Ecosystems Associates– EUSC– IFGI (Uni. Muenster)– IRIS– UAH (Uni. Alabama Huntsville)– Vightel – Washington University

• Sponsors, Additional Participants and Observers– LMCO, NGA, NASA, ORNL– IEEE 1451

Page 5: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE ConceptSWE Concept

Page 6: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

Enabling Sensor Webs with SWE FrameworkEnabling Sensor Webs with SWE Framework

Page 7: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OWS-4 Scenario: Alert-driven Processing of Sensor OWS-4 Scenario: Alert-driven Processing of Sensor DataData

• Seek to automate and shorten the decision-action loop.

• Focus on:– automated sensor

management and sensor data processing to produce actionable information for decision makers.

Obs DB

SAS

SPS

WPS

Controller

subscribe

alert!

submitRequest

getObservation

execute

SOSobservation

result

!

display

task

put

2 3

1

4

56

7 8

10

11

9

get

12

get

13

14

change

Viewer

Decision Support System

Sensor Data Systems

• The approach must be modular, extensible and standards-based (i.e., not a “point solution”)

Page 8: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

A SOA Workflow for Sensor Data (1)A SOA Workflow for Sensor Data (1)

Raw Sensor Data (e.g., IEE1451)

ANSI 42.42 GML Feature

Radiation Event Feature

IEEE 1451 TEDS + Sensor Channel

Data

WFS(Rad Feature)

Client

SWE O&M – ANSI 42.42 Schema Mapping

WPS(transform +

fusion)

SOS(IEEE1451 –SensorML)

IEEE 1451NCAP

Composite map

Observation Object

(e.g., measurement of temperature, rad.

spectrum, velocity, etc + metadata)

Algorithm

Page 9: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

A SOA Workflow for Sensor Data (2)A SOA Workflow for Sensor Data (2)

Raw Sensor Alert (e.g., IEE1451, TML, proprietary)

GeoRSS | CAP Message

Notification / Warning message

Sensor-Triggered Alert (e.g., location,

status, measured results)

GeoRSS | (CAP +

EDXL-DE)Server

Client

Schema Mapping

WPS(transform +

fusion)

SAS

Composite map

Algorithm

SOS

Page 10: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE Use CasesSWE Use Cases

• OWS1.2 Use Cases– UCArch1_FindData.doc– UCArch2_FindServices.doc– UCArch3_BindData2Service.doc– UCReg10_PublishAssociation.doc– UCReg1_FindExtrObject.doc– UCReg2_FindQueryExtrObject.doc– UCReg3_FindQueryClassExtrObject.doc– UCReg4_PublishClassObject.doc– UCReg5_PublishData.doc– UCReg6_PublishService.doc– UCReg7_PublishServiceType.doc– UCReg8_PublishDataType.doc– UCReg9_PublishTaxonomy.doc– UCSW1_FindTerrorist.doc– UCSW2_FindBorderEvent.doc– UCSW3_FindSports.doc– UCSW4_FindSensor.doc– UCSW5_RequestObservation.doc

Page 11: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

More SWE Use CasesMore SWE Use Cases

• DraftORNLSensorNetSWEUseCases.doc– UC1.1: Steady-State (all nodes and sensors are

known)– UC1.2: New Sensor Plugged In– UC1.3: Sensor “alerts” (threshold exceeded)

• GeoVideo_Use-cases_draft.doc– UC2.1: Sensor In Area– UC2.2: Track Sensor Feed– UC2.3: Change Sensor Target– UC2.4: Stop, Rewind, Play

• NASA_Ames_SPS_UseCases-20050508.doc– UC3.1: UAV1 Sensor Planning and Tasking in R-

T with Remote Manual Intervention– UC3.2: UAV2 Sensor System Planning and

Tasking in R-T w/o Manual Intervention– UC3.3: UAV3 SPS Feasibility Req/Resp Detail

• OWS-3 Use Cases-ACTM.ppt– UC4.1: Need Imagery Quick– UC4.2: Multi-spectral Imagery On Point Target– UC4.3: HiRes Optical/Full-Motion Video on Point

Target– UC4.4: Optical Area Target w/ Time Constraint &

Multiple Looks– UC4.5: Optical Point Target w/ Viewing Constraint– UC4.6: Dual Tasking w/ Optical & SAR LOC

Target w/ Time, Multiple Looks

• OWS-3-RFQ-UseCases.doc– UC5.1: Airborne Collection (discovery, tasking,

notification and access of sensor data)– UC5.2: Airborne Collection Federated Context

(sensors and platforms can be shared across organizational boundaries)

– UC5.3: Tasking Airborne Collection (need information from sensor not currently available)

– UC5.3.1: Tasking Airborne Collection with Bids– UC5.3.2: Tasking Airborne Collection with

Federation– UC5.4: Airborne Processing Chain (task, process,

exploit)• UseCasesfor1451Sensors.pdf

– UC6.1: Register new sensor/TIM– UC6.2: System unregisters TIM– UC6.3: Plugin 1451.2 Sensor with TIM– UC6.4: Plugin 802.11-based SensorML with TIM– UC6.5: Plugin 1451.4 Sensor with TIM– UC6.6: Applicatioin Selects a Transducer Channel

from the NCAP– UC6.7: Request Discrete Sensor Measurement– UC6.8: Request Steaming Sensor Measurements

Page 12: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OWS-4 SWE Specification Baseline Identifier Title URL

06-021r1 SWE Architecture DP http://portal.opengeospatial.org/files/?artifact_id=14140

05-087r4 O&M DP http://portal.opengeospatial.org/files/?artifact_id=14034

05-086r2 SensorML BP / RFC http://portal.opengeospatial.org/files/?artifact_id=12606

http://portal.opengeospatial.org/files/?artifact_id=13879&version=2&format=doc

06-010r3 TML RFC http://portal.opengeospatial.org/files/?artifact_id=14282&version=2&format=doc

05-089r3 SPS DP / RFC http://portal.opengeospatial.org/files/?artifact_id=12971 /

http://portal.opengeospatial.org/files/?artifact_id=13922&version=2&format=doc

06-009r1 SOS DP / RFC http://portal.opengeospatial.org/files/?artifact_id=12846 /

http://portal.opengeospatial.org/files/?artifact_id=13928&version=2&format=doc

06-028r3 SAS DP / updates http://portal.opengeospatial.org/files/?artifact_id=13921

http://portal.opengeospatial.org/files/?artifact_id=15588&version=1

06-095 WNS DP http://portal.opengeospatial.org/files/?artifact_id=1367

05-007r4 WPS DP / RFC http://portal.opengeospatial.org/files/?artifact_id=12184 /

http://portal.opengeospatial.org/files/?artifact_id=13149

Page 13: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OWS-4 SWE Baseline OWS-4 SWE Baseline (external specifications)(external specifications)

• ISO– ISO 19101-2 - Reference model - Part 2: Imagery – ISO 19123 - Schema for Coverage Geometry and Functions – ISO 19130 - Sensor and data models for imagery and gridded data– ISO 19136 - Geography Markup Language (GML 3.2.0 – OGC 05-108r1)– ISO/IEC JTC1/SC29/WG11 N4668, Coding of Moving Pictures and Audio (MPEG 4).

http://www.chiariglione.org/mpeg/standards/mpeg-4/mpeg-4.htm • IEEE-1451 (http://www.motion.aptd.nist.gov/)

– IEEE Std 1451.1-1999, Network Capable Application Processor (NCAP) Information Model for smart transducers

– IEEE P1451.0, Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats

– IEEE Std 1451.2-1997, Transducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats

– IEEE Std 1451.3-2003, Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems d

– IEEE Std 1451.4-2004, Mixed-mode Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats

– IEEE P1451.5, Wireless Communication and Transducer Electronic Data Sheet (TEDS) Formats –

– IEEE P1451.6, A High-speed CANopen-based Transducer Network Interface• OASIS (http://www.oasis-open.org)

– Common Alerting Protocol (CAP)– Emergency Data Exchange Language (EDXL) Distribution Element, (EDXL-DE)

Page 14: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE Information Model ViewsSWE Information Model Views

cd Logical Model

O&M

GML

SensorML TMLiso.tc211.19139

sweCommon

owsCommon

SPS SAS

SOS

WNS

Filter

xmlsoap.org.ws.addressing

us.gov .ic.ism

SWE Information Model Packages

«Sensor Registry»CSW

SPSWNS SAS

SOS

TMLSensorML

SWECommon

O&M

Page 15: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

O&M Observation ModelO&M Observation Model

<<ObsProcedure>> Procedure• General• Sensor

<<gml:Event>> om:Observation

An om:Observation instance is a gml:FeatureType::Event generated by a Procedure

TypedValue• name• value

<<Phenomenon>> observedProperty

<<AbstractFeature>> featureOfInterest

“Measured” results• Result (the data value)• resultDefinition (data encoding desc.)

Properties• event parameters• time• quality• responsible party

SensorSystemDescription• SensorML Document• TML Document

Kinds of Observations include:• Measurement• Category• Count• Truth• Coverage

Page 16: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE “Common” SWE “Common” (Commonly used data encodings)(Commonly used data encodings)

cd SweCommon

Phenomenon

+ CompositePhenomenon

+ CompoundPhenomenon

+ ConstrainedPhenomenon

+ constraintLists

+ Phenomenon

+ PhenomenonPropertyType

+ PhenomenonSeries

+ singleConstraint

RecordSchema

- Boolean

+ count

+ GridDefinition

+ GridDefinitionPropertyType

+ IndexArray

+ ItemArray

+ ItemArrayPropertyType

+ ItemDefinition

+ ItemDefinitionPropertyType

+ ItemSeriesDefinition

+ ItemSeriesDefinitionPropertyType

+ ModelGroup2

- Number

+ ObjectArray

+ positiveInteger

+ RecordDefinition

+ RecordDefinitionPropertyType

+ RepresentationType

- restriction

- restriction

- restriction

+ scale

- SimpleType

+ SWE_RecordSchema

+ SWE_RecordSchemaPropertyType

- Word

PositionData

+ _PositionType

- altitude

- ComplexTypeClass1

- ComplexTypeClass2

- ComplexTypeClass3

- ComplexTypeClass4

- coordinate

- coordinate

+ GeoLocation

- latitude

+ Location

- location

+ LocationData

- longitude

- order

- orientation

+ Orientation

+ OrientationData

+ Position

+ PositionData

- time

SWE_basicTypes

+ doubleList

+ nonNegativeIntegerList

+ refList

+ RelativeMeasureCode

+ RelativeMeasureType

+ ScopedNameListType

+ ScopedNameType

+ stringList

+ SWE_CompactNumericRecordType

+ SWE_CompactRecordType

+ TypedCategoryIntervalType

+ TypedCategoryListType

+ TypedCategoryType

+ TypedCountIntervalType

+ TypedCountListType

+ TypedCountType

+ TypedMeasureIntervalType

+ TypedMeasureListType

+ TypedMeasureType

+ UomIdentifier

+ UomSymbol

+ UomURI

Record

+ Array

- ComplexTypeClass1

- ComplexTypeClass2

+ item

+ ModelGroup1

+ Record

TemporalAggregates

+ ModelGroup3

+ ModelGroup4

+ ModelGroup5

- SeriesEnvelope

+ TimeAggregate

+ TimeAggregatePropertyType

+ TimeGeometricComplex

+ TimeGeometricComplexPropertyType

+ TimeGrid

+ TimeGridExtentType

+ TimeGridPropertyType

+ TimeInstantGrid

+ TimeInstantGridPropertyType

+ TimeIntervalGrid

+ TimeIntervalGridPropertyType

+ TimeObjectPropertyType

+ TimePositionListType

+ TimeValueList

cd SweCommon

Data

+ _BinaryType

+ _Data

+ _Encoding

+ _MultiplexEncoding

+ anyType

+ AsciiBlock

+ BinaryBlock

+ ByteEncodingType

+ ByteOrderType

- ComplexTypeClass1

- ComplexTypeClass2

- ComplexTypeClass3

- Component

+ DataComponentsPropertyType

+ DataDefinition

+ DataDefinitionPropertyType

+ DataValueType

+ EncodingPropertyType

- member

+ MultiplexEncodingPropertyType

+ SimpleDataPropertyType

+ StandardFormat

cd SweCommon

Parameters

+ _ArrayBaseType

+ _DataArray

+ _DataGroup

+ _GroupBaseType

+ AnyData

+ AnyNumerical

+ AnyScalar

+ arraySizeSimpleType

+ AssociationAttributes

- axis

+ axisCodeSimpleType

+ Boolean

+ booleanOrEmpty

+ Category

- ComplexTypeClass1

- ComplexTypeClass2

- ComplexTypeClass3

- component

- component

- condition

+ ConditionalValue

- Coordinates

+ Count

+ countList

+ countOrEmpty

+ countPair

+ CountRange

+ Curve

+ Curves

+ CurveType

+ DataArray

+ DataGroup

+ decimalList

+ decimalOrEmpty

+ decimalPair

- definition

+ definitionType

+ Discussion

+ emptyType

- extrapolationMethod

- function

- inputBias

- inputGain

- interpolationMethod

+ nameSimpleType

+ NormalizedCurve

- outputBias

- outputGain

+ Quantity

+ QuantityRange

- SimpleTypeClass2

+ TextType

+ Time

+ Time

+ timeIso8601SimpleType

+ timeList

+ timePair

+ TimeRange

+ timeReferenceSimpleType

+ timeSimpleType

+ timeString

+ token

+ tupleType

+ tupleValues

+ uomIdentifier

+ uomSymbol

+ uomType

+ uomURI

- value

cd Sw eCommon

Parameters

+ _ArrayBaseType

+ _DataArray

+ _DataGroup

+ _GroupBaseType

+ AnyData

+ AnyNumerical

+ AnyScalar

+ arraySizeSimpleType

+ AssociationAttributes

- axis

+ axisCodeSimpleType

+ Boolean

+ booleanOrEmpty

+ Category

- ComplexTypeClass1

- ComplexTypeClass2

- ComplexTypeClass3

- component

- component

- condition

+ ConditionalValue

- Coordinates

+ Count

+ countList

+ countOrEmpty

+ countPair

+ CountRange

+ Curve

+ Curves

+ CurveType

+ DataArray

+ DataGroup

+ decimalList

+ decimalOrEmpty

+ decimalPair

- definition

+ definitionType

+ Discussion

+ emptyType

- extrapolationMethod

- function

- inputBias

- inputGain

- interpolationMethod

+ nameSimpleType

+ NormalizedCurve

- outputBias

- outputGain

+ Quantity

+ QuantityRange

- SimpleTypeClass2

+ TextType

+ Time

+ Time

+ timeIso8601SimpleType

+ timeList

+ timePair

+ TimeRange

+ timeReferenceSimpleType

+ timeSimpleType

+ timeString

+ token

+ tupleType

+ tupleValues

+ uomIdentifier

+ uomSymbol

+ uomType

+ uomURI

- value

Data Definition

Data Components

Data Group

Component

Encoding

Value

Data

Component

•Basic Types•Temporal Aggregates•Phenomenon•Position Data•Record•RecordSchema•Data•Parameters

Page 17: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE Service Model (A Data Center View) SWE Service Model (A Data Center View)

• SWE Services– SOS = Sensor Observation Service– SAS = Sensor Alert Service– SPS = Sensor Planning Service– CSW = Catalog Service (for Sensor

Resources)

• SWE Data Center– Composition of integrated SOS, SPS

and SAS service implementations – Tasking of sensors, access to sensor

system observation data and alerting of sensor system state changes and measurements.

– Support the requirements for sensor systems and protocols (IEEE1451, MPEG4, ANSI 42.42, XMPP, OASIS CAP/EDXML)

– Descriptions of the sensors systems, observation offerings and services must be published to CSW implementations

SPSSOS

Data Center

SAS

ObservationDatabase

ProcessingCapabilities

SOS-T

Public Client Side

Private Network Side

WNS

SAS Client

SPS Client

SOS Client

LocalUser

CSW

Data Center

SD

SD

SD

Node

SD SD

SD

Node

SD

SD

SD

Node

PublicUser

Page 18: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

SWE Demo Site: NYNJ Port AuthoritySWE Demo Site: NYNJ Port Authority

Page 19: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

Hospital Site at AirportHospital Site at Airport

Page 20: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

Sensors Integrated in the SWE Demo NetworkSensors Integrated in the SWE Demo Network

• ORNL Rad Sensor – ORNL-SAS, 3eTI-SOS

• IRIS and IFGI Video Sensors/Actuators – IFGI-SPS, 3eTI-SOS

• Smart Sensor Systems Light Sensor (TinyTIM™ 1451 Bluetooth)

– 3eTI-SOS • NASA EO1 Hyperion Imagery Sensor

– Vightel-SOS, Vightel-SAS, Vightel-SPS• Environment Sensors (Moisture, AmbTemp,

SoilTemp, Solar Voltage/Current)– CSIRO-ICTC SAS and SOS

• NWS Weather Sensors – IFGI-SOS

• Doppler Radar Sensors – UAH-SOS

• GOES Imagery Sensor – UAH-WCS

Page 21: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

OWS-4 Sensor Network @ PANYNJ OWS-4 Sensor Network @ PANYNJ

Page 22: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

Tasking TML Camera in Warehouse Tasking TML Camera in Warehouse

Page 23: OWS-4 SWE Overview 28 November 2006 @NIST Mark Reichardt / George Percivall / John Davidson

Helping the World to CommunicateGeographically

EO-1 User StoryEO-1 User Story

• DHS analyst requests satellite imagery in disaster area to validate potential site. Catalog returns EO-1 as possible source.[via CSW service].

• Access to high resolution EO-1 data is granted based on user/role permission

• No data is available, so satellite tasking is required and achieved (at no cost to DHS) [via SPS service].

• Analyst is notified via IM that Hyperion/ALI data products are available. High resolution imagery is retrieved [via SOS and WCS and WFS services].