Sensor Observation Service (SOS)

---

Overview

The objective of the Sensor Observation Service (SOS) is to make sensors and sensor data archives accessible via an interoperable web based interface. The 52°North SOS was used as reference for the compliance tests during the OWS5 testbed. After the SOS has been published as official OGC implementation specification in spring of 2008, this new implementation is now implemented with the 52°North SOS version 3.1.0.

This page documents the progress of development concerning the SOS.

SOS implementation specification

The result of the OWS-5 has been an update of the SOS specification, which yielded in the SOS implementation specification 1.0 (OGC 06-009r6) . The specification could be downloaded from http://www.opengeospatial.org/standards/sos.

---

52°North SOS

Active SOS developers

• Christoph Beekmans
• Carsten Hollmann
• Martin Kiesow
• Christoph Stasch
• Stephan Künster
• Alexander Strotmann
• Alexander C. Walkowski
• Arne Bröring

Former SOS developers

• Thomas Remmersmann
• Julian Kuhlmann
• Oliver Meyer

Implementation

The 52°North SOS version 3.1.0 implements the SOS implementation specification 1.0. The implementation is written in Java and uses the following technical frameworks:

• PostgreSQL DBMS with PostGIS extension
• XMLBeans for parsing and encoding XML requests and responses
• Java Topology Suite (JTS)
• Log4J
• Apache Maven

Supported Filters

The following filter operations are supported for the GetObservation operation:

• spatial filters:
  • Contains
  • Intersets
  • Overlaps
  • BBOX
• temporal filters:
  • T_Equals
  • T_After
  • T_Before
  • T_During
• result filters:
  • PropertyIsEqualTo
  • PropertyIsNotEqualTo
  • PropertyIsLessThan
  • PropertyIsGreaterThan
  • PropertyIsLessThanOrEqualTo
  • PropertyIsGreaterThanOrEqualTo
  • PropertyIsLike
  • PropertyIsNull
  • PropertyIsBetween

Operations

A detailed description of the supported operations could be found at the SosOperations page.

The currently supported operations of the 52° North's SOS implementation are:

• complete core profile (GetCapabilities,DescribeSensor and GetObservation
• GetFeatureOfInterest: Returns the target Feature of the observation.
• GetResult: Enables the client to retrieve new data of same sensors, phenomena and features repeatedly from SOS, without the need of sending the whole requests repeatedly
• GetObservationById: Returns an observation for a passed observation id

SOS Mobile Extension

The 52°North SOS implements an extension for mobile Sensors, e.g. a position history for sensors and adjustments of operations to handle redundant features of interest. You find a description of the features at SosMobileExtension.

SOS tutorial

You find the SOS installation guide in the project of the SOS in the doc folder. Additionally, we are currently working on a SosTutorial side.

SOS troubleshooting

In the TroubleShooting you find solutions for several problems

SOS example application

You can test an example application of the SOS-v3.1.0 using the following links:

operation	link
GetCapabilities	http://mars.uni-muenster.de:8080/OWS5SOS/testClient_capabilities.html
DescribeSensor	http://mars.uni-muenster.de:8080/OWS5SOS/testClient_describeSensor.html
GetObservation	http://mars.uni-muenster.de:8080/OWS5SOS/testClient_timePeriod.html

Further test clients with different getObservation-requests could be found at:

• http://mars.uni-muenster.de:8080/OWS5SOS

Road map

• 2010-03-31 Release-Update to version 3.1.1: Bugfixes, SOAP Binding
• 2010-04-15 Publish modules as beta: HibernateDAOs and WfsDAOs
• 2010-06-30 Minor Release to version 3.2.0 with SOAP Binding, Hibernate and support of feature handling via WFS

implementation log

• 2007-11-09 implementation changed to final schemata v1.0
• 2007-11-26 implementation of transactional profile finished
• 2008-03-04 implementation of SOS version 3.00.01 finished

working tasks

• integration of JUnit tests (Carsten + Christoph)
• implementation of the enhanced profile (all)
• change encoding of O&M from XmlBeans to Stax to enable bigger response documents (currently limited to about 5 MB) (high complexity) (all)
• seperate feature management from SOS (use existing WFS implementation) (Carsten)
• change DAO implementations to Hibernate (Christoph B.)

52°North SOS client development

• 52north is developing a multiclient framework for integration of multiple OGC web services into one client application. The development currently focuses on the integration of sensor data from the SensorObservationService. See OX-Framework for more details!
• For ArcGIS, an SOS adapter currently is under development. It will be part of the CCIP demo within the upcoming FOSS4G in Sydney.

---

SOS former developments

You can find documentation about former developments on the SosFormerDevelopments topic.

Setting up SOS project as Dynamic Web project in eclipse

See SosDynamicWebProject

---

-- ChristophStasch - 07 Jan 2010