62 Copyright © 2011 Open Geospatial Consortium
Table 25 — Code values applicable to the supportedEncoding property
Applicable Code Values Additional Note
http:www.opengis.netswe2.0TextEncoding best suited in most cases if
ASCII encoded parameters are used
http:www.opengis.netswe2.0XMLEncoding generally applicable
http:www.opengis.netswe2.0BinaryEncoding suited for example for
transferring image data to the service
7.3.3.4 SensorOffering
This data type contains metadata about a sensor provided by the service. The SensorOffering see Figure 17 type is derived from SWES AbstractOffering defined
in clause 7 of [OGC 09-001] and therefore inherits all the properties contained in that type. SensorOffering does not restrict the content model of AbstractOffering.
Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsesensorOffering
REQ 46. The SensorOffering type shall contain the properties defined for
SWES AbstractOffering. In addition, it shall contain the property according to Table 26.
Table 26 — Properties in the SensorOffering type
Name Definition
Data type and values Multiplicity and use
observable Area
the area that the sensor can observe
PointOrPolygon, see clause 7.3.3.5
One mandatory
The SensorOffering represents an inheritor of the properties contained in the SPSContents
. The following table shows which of the properties defined in the content model of SensorOffering can be inherited and which cardinality is expected after the
inheritance mechanism has been applied.
Copyright © 2011 Open Geospatial Consortium 63
Table 27 — Inheritance of SensorOffering properties from SPSContents Property Cardinality
Inheritance
procedure 1 NA
procedureDescriptionFormat 1.. replace observableProperty 1..
replace relatedFeature 0..
replace observableArea 1
NA
Thus, even though the UML model and schema encoding define the observableProperty and procedureDescriptionFormat properties as optional, they are mandatory in each
SensorOffering . In other words, each offering has to include at least one value for these
two properties after the property inheritance mechanism was applied.
7.3.3.5 PointOrPolygon
This type represents a choice between the geometric types point or a polygon. Those two types are e.g. used to describe the point or the area observed by a sensor.
Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsePointOrPolygon
REQ 47. The PointOrPolygon union shall contain the propertieschoices
according to Table 28.
Table 28 — Properties in the PointOrPolygon union
Name Definition
Data type and values Multiplicity and use
byPoint a point
GM_Point, see clause 10.3.1 in [OGC 07-
036] One mandatory
Because PointOrPolygon is a union, either a point
or polygon shall be used i.e. there is a choice
between the properties byPolygon a
polygon Polygon, see clause
10.5.4 in [OGC 07- 036]
7.3.4 DescribeTasking Operation
7.3.4.1 Introduction
The DescribeTasking operation allows SPS clients to retrieve the description of the data structures for the tasking parameters of a sensor. The data structure description is
encoded in SWE Common see clause 7.4 - SPS tasking parameters representation.
64 Co
7.3.4.2 Data Types
The conceptual model of the DescribeTasking operation is shown in the following UML diagram.
Figure 18 — Data types of the DescribeTasking operation
The details of the operation request and response are explained in the following subclauses.
7.3.4.3 Operation Request - DescribeTasking
Sending an instance of the DescribeTasking data type to the service performs an SPS DescribeTasking
operation request. The DescribeTasking data type is derived from the SWES ExtensibleRequest data type
specified in clause 9 of [OGC 09-001] and therefore inherits all the properties contained in that data type.
Requirement http:www.opengis.netspecSPS2.0reqDescribeTaskingRequestdataType
REQ 48. The DescribeTasking data type shall contain the properties
defined for SWES ExtensibleRequest. In addition, it shall contain the property according to Table 29.
pyright © 2011 Open Geospatial Consortium
