OWS-4 SWE Overview 28 November Mark Reichardt / George Percivall / John Davidson

Helping the World to Communicate Geographically Topics 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

Helping the World to Communicate Geographically OGC Process – Iterative Development Yielding Tested Specifications

Helping the World to Communicate Geographically OWS-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

Helping the World to Communicate Geographically SWE Concept

Helping the World to Communicate Geographically Enabling Sensor Webs with SWE Framework

Helping the World to Communicate Geographically OWS-4 Scenario: Alert-driven Processing of Sensor Data 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 SOS observation result  ! display task put get 12 get change Viewer Decision Support System Sensor Data Systems The approach must be modular, extensible and standards-based (i.e., not a “point solution”)

Helping the World to Communicate Geographically A SOA Workflow for Sensor Data (1) Raw Sensor Data (e.g., IEE1451) ANSI GML Feature Radiation Event Feature IEEE 1451 TEDS + Sensor Channel Data WFS (Rad Feature) Client SWE O&M – ANSI Schema Mapping WPS (transform + fusion) SOS (IEEE1451 – SensorML) IEEE 1451 NCAP Composite map Observation Object (e.g., measurement of temperature, rad. spectrum, velocity, etc + metadata) Algorithm

Helping the World to Communicate Geographically 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

Helping the World to Communicate Geographically SWE 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

Helping the World to Communicate Geographically More 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 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 Sensor with TIM –UC6.4: Plugin based SensorML with TIM –UC6.5: Plugin 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

Helping the World to Communicate Geographically OWS-4 SWE Specification Baseline IdentifierTitleURL r1SWE Architecture DPhttp://portal.opengeospatial.org/files/?artifact_id= r4O&M DPhttp://portal.opengeospatial.org/files/?artifact_id= r2SensorML BP / RFChttp://portal.opengeospatial.org/files/?artifact_id= version=2&format=doc r3TML RFChttp://portal.opengeospatial.org/files/?artifact_id=14282& version=2&format=doc r3SPS DP / RFChttp://portal.opengeospatial.org/files/?artifact_id=12971http://portal.opengeospatial.org/files/?artifact_id=12971 / version=2&format=doc r1SOS DP / RFChttp://portal.opengeospatial.org/files/?artifact_id=12846http://portal.opengeospatial.org/files/?artifact_id=12846 / version=2&format=doc r3SAS DP / updateshttp://portal.opengeospatial.org/files/?artifact_id= version= WNS DPhttp://portal.opengeospatial.org/files/?artifact_id= r4WPS DP / RFChttp://portal.opengeospatial.org/files/?artifact_id=12184http://portal.opengeospatial.org/files/?artifact_id=12184 /

Helping the World to Communicate Geographically OWS-4 SWE Baseline (external specifications) ISO –ISO Reference model - Part 2: Imagery –ISO Schema for Coverage Geometry and Functions –ISO Sensor and data models for imagery and gridded data –ISO Geography Markup Language (GML – OGC r1) –ISO/IEC JTC1/SC29/WG11 N4668, Coding of Moving Pictures and Audio (MPEG 4). IEEE-1451 ( –IEEE Std , 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 , Transducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheet (TEDS) Formats –IEEE Std , Digital Communication and Transducer Electronic Data Sheet (TEDS) Formats for Distributed Multidrop Systems d –IEEE Std , 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 ( –Common Alerting Protocol (CAP) –Emergency Data Exchange Language (EDXL) Distribution Element, (EDXL-DE)

Helping the World to Communicate Geographically SWE Information Model Views SPS WNS SAS SOS TML SensorML SWE Common O&M

Helping the World to Communicate Geographically O&M Observation Model > Procedure General Sensor > om:Observation An om:Observation instance is a gml:FeatureType::Event generated by a Procedure TypedValue name value > observedProperty > 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

Helping the World to Communicate Geographically SWE “Common” (Commonly used data encodings) Basic Types Temporal Aggregates Phenomenon Position Data Record RecordSchema Data Parameters

Helping the World to Communicate Geographically 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 CSW

Helping the World to Communicate Geographically SWE Demo Site: NYNJ Port Authority

Helping the World to Communicate Geographically Hospital Site at Airport

Helping the World to Communicate Geographically Sensors 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

Helping the World to Communicate Geographically OWS-4 Sensor PANYNJ

Helping the World to Communicate Geographically Tasking TML Camera in Warehouse

Helping the World to Communicate Geographically EO-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].