52north.org

52north.org

SWE Components

Core

SOS

SAS/SES

SPS

WNS

Clients

SWEcurity

Incubation

Sensor Instance Registry

Sensor Observable Registry

Home Weather Station System

Sensor World

52north.org

SOS

52north.org

SOS

SOS

SOS-Feeder

SOS Insert Application

Video On Demand SOS

52north.org

SOS

Implements OGC implementation specification v1.0:

– Core Profile

– Transactional Profile for numerical and spatial observations

– GetFeatureOfInterest, GetFeatureOfInterestTime, GetResult

Based upon JAVA, PostgreSQL+PostGIS, Apache Tomcat, Apache Ant

Based upon robust libraries and technologies:

– Java Servlet API, Apache XMLBeans, Java Topology Suite (JTS)

Extension for mobile sensors

52north.org

SOS

Future Steps:

– New release (3.1.0) planned

– Maven migration

– Support additional DBMS (Oracle, MySQL), modular DBMS integration

– Test Suite

– Extension of Transactional Profile (support additional observation types)

– Paging Mechanism

– Delegation of feature handling to external WFS

– KML-Encoding of responses

– SOAP-Binding

Start of the SOS SWG

52north.org

SOS-Feeder

Web service for feeding data into the SOS data base

Supports the current SOS version including the mobile extension

Future steps:

– Synchronization with new SOS release

– Decide about the future: Feeder vs. SOS-T

52north.org

SOS Insert Application

Web based form for entering data that shall be inserted into a SOS instance

Based on the Transactional Profile of the SOS

Currently in the development process

– Stationary sensors already supported

– Mobile extension not yet integrated

Future steps:

– Synchronization with new SOS release

– Integrate security mechanisms

52north.org

Video On Demand SOS

Special SOS implementation for delivering video data

Allows retrieving video for certain time periods

Video is streamed to the client

Developed as a prototype within the OSIRIS project

Future steps:

– Advance to a release

– Flexible video format support

52north.org

SAS/SES

52north.org

SAS/SES

SAS

– Subscription to user defined alert conditions

– Dispatch alerts via XMPP (extensible messaging and presence protocol)

– Support of other communication protocols though gateway services like WNS

– Compliant to OGC SAS specification 0.9.0 RFC

– Future steps see SES (Sensor Event Service)

52north.org

SAS/SES

SES

– OGC Discussion Paper (document number 08-133)

– Based upon OASIS WS-Notification

– Topic and content based filtering

– Three filter levels:

• XPath (mandatory)

• OGC Filter Encoding (optional)

• EML (optional)

– Not restricted to specific transport protocol

– Default binding: SOAP via HTTP

– Unit conversion

52north.org

SAS/SES

SAS vs. SES

SAS SES

Filtering:– spatial () – temporal – comparing () – aggregation

CEP / ESP Topics Unit conversion

52north.org

SPS

52north.org

SPS

Allows to task sensors and simulation models

Compliant to OGC SPS 1.0 specification

Release version 1.0 available

Modular plug-in architecture allows the easy integration of new sensor types

Exemplary plug-in available for Axis network camera

52north.org

SPS

Practical demo: MSP

Future steps

– For the OSIRIS project development of plug-ins for

• controlling a manually flown airplane (send task messages to the pilot)

• Controlling an UAV

52north.org

WNS

52north.org

WNS

Functionality for supporting asynchronous communication processes between services and clients (e.g. between SPS and user)

Based on OGC best practice paper (OGC 06-095) version 0.0.9

Supports

– SMTP (E-Mail)

– XMPP

– SMS

– Fax

– Phone

Future steps:

– Follow OGC developments (e.g. within OWS-6)

52north.org

Clients

52north.org

Clients

OX-F Rich Client

Thin-Clients

ArcGIS Adapter

uDig Plug-In

Google Maps Display

52north.org

OX-F Rich Client

Java based stand alone client

Supports

– WMS versions: 1.0.0, 1.1.0 and 1.1.1

– WCS versions: 1.0.0, 1.1.0 and 1.1.1

– SOS versions: 0.0.0 and 1.0.0

– SAS version: 0.9.0

– CSW: 2.0.2 together with ebRIM 3.0

52north.org

OX-F Rich Client

52north.org

OX-F Rich Client

Future steps:

– SOS mobile support

– Support of the SES specification as soon as it has reached a stable state

– Closer coupling to releases of the SWE services

52north.org

Thin-Clients

Web based client for accessing

– SOS versions: 0.0.0 and 1.0.0

– SAS version: 0.9.0

SOS client

– Time series display

– Based on Dojo (framework for generating diagrams)

SAS client

– Definition of simple alert conditions

– Submission of subscriptions

52north.org

Thin-Clients

52north.org

Thin-Clients

SOS

– Currently analysis of charting frameworks/concepts improve the performance

– Analysis of ways for allowing also a cartographic displays (e.g. using Open Layers)

SAS

– Allow more complex alert conditions

– Advancing the client implementation to support the SES as soon as the specification is stable

Important discussion topic

52north.org

ArcGIS Adapter

Adapter allowing to access a SOS

Features and latest observations are stored within a personal geodatabase

Allows to retrieve data from a SOS and to use it for further work and analysis within ArcGIS

Provides links to the time series display web client

First prototype available

Next steps

– Advance the prototype to a state that can be published

– Improve the interoperability

52north.org

uDig Plug-In

uDig Open Source GIS based on Eclipse

Plug-In allows to load data from a SOS and to integrate this data as a new layer

Current version is compatible to the SOS version 1.0.0

Retrieval of all features and observations from a SOS

Future Steps:

– Advance the implementation to a release

– Implement temporal filtering

– Facilitate the installation

52north.org

Google Maps Display

Display of sensor positions including the measured phenomena

Link to thin SOS client

Future Steps:

– Enhance the display in order to show the latest observed values

52north.org

Google Maps Display

52north.org

SWEcurity

52north.org

SWEcurity

Controls access to SOS instances

Uses the components of the 52N Security community

Powerful mechanisms for user based access control

Future Steps

– Support further SWE services

– OWS-6

SWE Client SOS

WSS-ProtocolSOS-Protocol

SOS Facade

Security Client

SOS Client

WSS

SO

S-P

roto

col

SO

S-P

roto

col

52north.org

Incubation

52north.org

Sensor Instance Registry

Discover sensors based on– Spatial criteria– Temporal criteria– Thematic criteria

Basic support of semantic concepts Discover not only the sensors but also the SWE services through

which they can be accessed Harvesting of necessary metadata But also: Handle the status of sensors

– Sensor positions ( in most cases this is a status property)– Battery state– ...

52north.org

Sensor Instance Registry

SIR interface consists of two parts:– Discovery

• Discover which sensors provide a requested type of information • Discover which SWE services provide a requested type of

information• Discover which SWE services make a given sensor accessible

or controllable– Sensor status handling

• Requesting the status of a specific sensor• Requesting the status of all sensors which match certain

criteria • Subscription to sensor status information • Insertion of sensor status information by sensor providers

More than catalogue functionality

52north.org

http://v-swe.uni-muenster.de:8080/SensorRegistry

Sensor Instance Registry

52north.org

Sensor Instance Registry

Future steps:– Align to the OGC Catalogue specification– Improve the harvesting mechanisms– Integrate temporal indices

52north.org

Sensor Observable Registry

Manage the definitions and semantics of observables Extend the search capabilities of the SIR e.g.

fuzzy search Functionality

– Handling references to definitions of phenomena/observables

– Retrieving the definition of a given phenomenon– Retrieving the semantically related phenomena of a given

phenomenon– Retrieving a list of all known phenomena

52north.org

Sensor Observable Registry

Currently the implementation is starting

Future steps:

– Allow the definition of semantic relationships that are of interest

– Advance to a stable version

52north.org

Home Weather Station System

52north.org

Home Weather Station System

Practical demonstration of the SWE components Use case that can be understood by a large

audience Using a SOS for collecting the home weather

station data Development of a bridge for connecting a

weather station to the system Future Steps:

–

52north.org

Home Weather Station System

52north.org

Home Weather Station System

Web based client: http://v-swe.uni-muenster.de:8080/WeatherSweClient/index.html

52north.org

Sensor World

Framework for simulating sensor networks

Developed within OSIRIS

Aims at

– Testing of SWE services in connection with complex, potentially autonomous sensor networks

– Evaluating sensor network organization models

Message based architecture (JMS)

52north.org

Sensor World

Comprises simulation components for

– Phenomena

– Sensor behavior

– Sensor communication

Adapter to connect to

– SOS

– SPS

52north.org

Thank you!