Open Geospatial Consortium
OGC Doc
08-172?????
CR-Form-v3
CHANGE REQUEST
SOS CR
08-172?
rev-
Current version: 06-009r6 For
HELP
on using this form, see bottom of this page or look at the pop-up text over the symbols.Proposed change affects: AS Imp Spec X Best Practices Paper Other
Title: Addition of the UpdateSensor operation
Source: University of Muenster, Institute for Geoinformatics (IfGI)
Work item code: Date: 2008-11-06
Category: B
C
Use one of the following categories: F (Critical correction)
A (corresponds to a correction in an earlier release)
B (Addition of feature),
C (Functional modification of feature) D (Editorial modification)
Detailed explanations of the above categories can be found in the TC Policies and Procedures.
Reason for change: Currently the SOS lacks a mechanism for updating sensor properties that are changing during the course of time. At the moment there is no operation for changing properties that are described within a SensorML document.
This causes problems especially in case of mobile sensors which are moving around through an area of interest. In order to update the sensor positions within the SOS the new UpdateSensor operation is needed.
In addition also other sensor properties require sometimes updates within the SOS. Examples for this comprise status properties like the battery state but also information if a sensor is currently active or inactive.
Summary of change: Add the new UpdateSensor operation.
Consequences if
not approved: Lacking support for which change during the course of time.mobile sensors and sensors that have dynamic properties
Clauses affected: 10.8 (new clause)
Other specs Other core specifications
The OGC Technical Committee Policies & Procedures 05-020r3
Add a new sub clause 10.8 as follows:
10.8 UpdateSensor (optional)
10.8.1 Introduction
The UpdateSensor operation allows updating properties of a sensor. This comprises
sensor status information (e.g. active/inactive, battery level, etc.) as well as sensor
positions (i.e. in case of moving sensors).
10.8.2 Request
Figure UpdateSensor (optional)-1 Parameters for an UpdateSensor Request
The OGC Technical Committee Policies & Procedures 05-020r3
Table 1. Parameters of an UpdateSensor Request
Name a Definition Data type and values Multiplicity and use
service Service type identifier SOS One (mandatory) version Specification version for operation Supported version of
SOS One (mandatory) sensorID The ID of the sensor for which the
position/status information is updated. anyURI One (mandatory) timestamp This parameter provides the information at
which instance of time the inserted position/sensor status is valid.
swe:Time One (mandatory)
position This parameter can be used for inserting an
updated sensor position. swe:PositionType One (Optional) property For each other sensor property, except
position,which is supposed to that is be
updated one a property element can be beaded included in to the UpdateSensor request.
swe:DataComponentProp
ertyType Zero or more (Optional)
a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 06-121r3].
10.8.3 Response
The response to an UpdateSensor request is the fixed string “sensorUpdated” which
indicates that the
sensor
submitted sensor properties were successfully updated. Otherwise
an exception is returned (see 10.8.4).
10.8.4 Exceptions
When a
n
SOS server encounters an error while performing an UpdateSensor operation, it
shall return an exception report message as specified in clause 8 of [OGC 06-121r3].
10.8.5 Examples
10.8.5.1 Example 1
Here is an UpdateSensor request that updates the properties of sensor the sensor with the
id urn:ogc:object:Sensor:MyOrg:12349 at a given time. It changes the sensor position and
sets the property “isActive” to true.
<sos:UpdateSensor service="SOS" version="1.0.0" xmlns:gml="http://www.opengis.net/gml"
xmlns:sos="http://www.opengis.net/sos/1.0" xmlns:swe="http://www.opengis.net/swe/1.0.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="://www.opengis.net/sos/1.0 http://schemas.opengis.net/sos/1.0.0/sosAll.xsd ">
<sos:sensorID>urn:ogc:object:Sensor:MyOrg:12349</sos:sensorID> <sos:timeStamp>
<gml:timePosition>2008-11-06T14:12:20-08:00</gml:timePosition>
</sos:timeStamp>
<sos:position referenceFrame="urn:ogc:def:crs:EPSG:6.14:31466"> <swe:location>
<swe:Vector gml:id="SENSOR_POSITION"> <swe:coordinate name="easting">
<swe:Quantity axisID="x"> <swe:uom code="m"/>
<swe:value>2112308.332</swe:value>
</swe:Quantity>
</swe:coordinate>
<swe:coordinate name="northing"> <swe:Quantity axisID="y">
The OGC Technical Committee Policies & Procedures 05-020r3
<swe:uom code="m"/>
<swe:value>5219592.542</swe:value>
</swe:Quantity>
</swe:coordinate>
<swe:coordinate name="altitude"> <swe:Quantity axisID="z">
<swe:uom code="m"/> <swe:value>45.0</swe:value>
</swe:Quantity>
</swe:coordinate>
</swe:Vector>
</swe:location>
</sos:position>
<sos:property name="isActive"> <swe:Boolean>
<swe:value>true</swe:value>
</swe:Boolean>
</sos:property>
</sos:UpdateSensor>
Here is what the response might look like. In this example the SOS is reporting that the
sensor properties were successfully updated.
<sos:UpdateSensorResponse xmlns:sos="http://www.opengis.net/sos/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="://www.opengis.net/sos/1.0 http://schemas.opengis.net/sos/1.0.0/sosAll.xsd ">
<sos:status>sensorUpdated</sos:status>
</sos:UpdateSensorResponse>
