Sensor Observation Service (SOS) 2.0 SWG

1.    Sensor Observation Service (SOS) 2.0 SWG

2.    Purpose of the Standards Working Group

The purpose of this Standards Working Group is to update the SOS Version 1.0 Standard and to develop Version 2.0. It will achieve this objective by evaluating and processing the Change Requests listed in Section 3, ensuring that the standard is consistent with the OGC baseline and business plan.

3.    Scope of Work

The primary aim of this SWG is to redesign the existing service model and to improve and facilitate its usage from a client's perspective. This will be done by analyzing the current specification and by clearly identifying end user requirements to a refactored SOS interface.

Further on the SWG will collect all outstanding and planned Change Requests, evaluate each of these proposals, and edit the standard based on these Change Requests and related decisions of the SWG membership. This SWG will consider at least the following Change Request Proposals and discussion items:

  • 08-030: Combined CRs from OWS-5 CITE
    • Observation offering and procedure consistency
    • Guarantee match between procedure IDs and ID contained in sensor description document
    • Indication of responseMode in GetObservation response
    • Clarification of outputFormat parameter in DescribeSensor operation
  • 08-171: Enhance GetFeatureOfInterestTime
  • 08-172: Add UpdateSensor
  • 08-173: KVP Encoding for Core Operations
  • 08-174: Introducing SensorOffering Concept
  • 08-177: Addition of the InsertResult Operation
  • 08-180: Consistency of inserting updating and removing observation offerings and procedures
  • 08-181: Observation Offering and Default Response when event time is not provided
  • 08-182: Observation offering and procedure consistency
  • 08-183: Obligation of observedProperty parameter in GetObservation request
  • 08-184: srsName multiplicity
  • 08-186: Clarification of observedProperty in SOS with respect to SensorML description
  • 08-195: Add Time To DescribeSensor

Additional Change Requests may be addressed at the discretion of the SWG based on criticality of the change and available time and resources.

Apart from those explicit work items the SWG will harmonize the SOS specification with other OGC standards. Especially the harmonization with the Web Feature Service (WFS) and the Web Coverage Service (WCS) will be taken into consideration.

3.1       What is out of scope?

Only those change requests submitted through the formal process as identified in the Policy and Procedures will be addressed.  Therefore, any items suggested through emails, vocal discussions, etc will be outside of the scope of this SWG until formally submitted.

3.2    Specific Existing Work Used as Starting Point

The starting point for the work will be Version 1.0 of the SOS standard (OGC 06-009r6).

3.3    How to Determine when Work of SWG has been Completed

The following criteria will be used to determine the completion of this SWG:

A completed revision of Sensor Observation Service Standard documents have been produced and reviewed by the SWG and have been approved for submission to the TC for approval as an adopted standard.

4.    Description of deliverables

The following deliverables will result from the work of this SWG:

  • A final version of the SOS version 2.0 Standard documents for submission to the TC.
  • Corresponding XML schemas associated with version 2.0 of the SOS Standard documents.

The following schedule of activities is anticipated:

1)      Seek approval for formation of the SOS SWG at the OGC TC held in Valencia in December 01-05, 2008.

2)      Begin the organization and assignment of SWG work activities during the SOS SWG ad-hoc session at the TC meeting in December 2008.

3)      Internal review of SOS 2.0 initial release documents status during TC meeting in June 2009. This review will include initial evaluation of which proposed changes are not likely to be ready in time for inclusion in the version 2.0 initial release documents.

4)      Final version of the SOS 2.0 documents completed at least three weeks prior to TC meeting in September 2009.

5)      SOS version 2.0 Standards documents submitted to the TC during the TC meeting in December 2009 for approval as version 2.0.

The above schedule is meant to serve as a guideline to the SWG in order to determine completion milestones.  However, based on the actual Change Requests, completion dates may be adjusted to accommodate critical updates to the documents.  Although all change requests will be addressed, some may be postponed due to the need to more quickly produce a document containing higher priority requests.

5.    IPR Policy for this SWG

RAND-Royalty Free

6.    Anticipated Audience

The target audience of SOS version 2.0 is any implementers and / or users of OGC SOS standard or related SWE specifications.

7.    Other informative information about the work of this SWG

a. Similar or applicable standards work

The following standards may be relevant to this SWG's planned work:

  • OGC SWE Common
  • OGC SensorML
  • OGC O&M
  • OGC SAS, and SPS services
  • OGC GML 3.2
  • ISO TC 211 suite
  • XML Schema
  • RelaxNG

b. Projected on-going meeting schedule

The work of this SWG will be carried out primarily by email and conference calls, with face-to-face meetings at each of the OGC TC meetings as defined by the chair. The teleconference calls are currently planned every one or two weeks. The concrete dates will be announced by the SWG.

c. Supporters of this Charter

The following persons support this SWG and are committed to the Charter and projected meeting schedule.



Arne Broering


Christoph Stasch

University of Muenster

Luis Bermudez

Southeastern Universities Research Association (SURA)

Mike Botts

University of Alabama in Huntsville

Johannes Echterhoff

International Geospatial Services Institute GmbH (iGSI)

Jeff de La Beaujardiere

National Oceanic and Atmospheric Administration

Christian Heier


Alex Robin

SPOT Image


d. Convener

Arne Broering (52°North Initiative for Geospatial Open Source Software GmbH)

Christoph Stasch (University of Muenster)