Optional Parameters SPS tasking parameters representation

Copyright © 2011 Open Geospatial Consortium 129 Listing 3 – example for optional and required tasking parameters swe:DataRecord … -- Mandatory Parameter-- swe:field name = taskTimeFrame swe:TimeRange optional = false … -- … -- swe:TimeRange swe:field -- Optional Parameter-- swe:field name = p ositioningChoice swe:DataChoice optional = true … swe:item name = pointToLookAt swe:Vector … -- … -- swe:Vector swe:item swe:item name = relativePositioning swe:DataRecord … -- Optional Parameter-- swe:field name = alPan relativeHorizont swe:Quantity optional = true … -- … -- swe:Quantity swe:field -- Optional Parameter-- swe:field name = Pan relativeVertical swe:Quantity optional = true … -- …-- swe:Quantity swe:field swe:DataRecord swe:item swe:DataChoice swe:field -- Optional Parameter-- swe:field name = focalLength swe:Quantity optional = true … -- …-- swe:Quantity swe:field swe:DataRecord 7.4.2 Default Values All data components defined in [OGC 08-094] can be either used as data descriptors or data containers. Data containers set the attribute values, data descriptors don’t. SPS uses both descriptors and containers to describe tasking parameters Given values indicate default values. The SPS can set default values for each tasking parameter. An SPS may but is not required to provide default values. The client can either accept this default value and use it as-is or overwrite it in a tasking request. 130 Copyright © 2011 Open Geospatial Consortium Listing 4 – example of a tasking parameter description without default values swe:DataRecord … -- -- swe:field name = positioningChoice swe:DataChoice … swe:item name = pointToLookAt swe:Vector … -- -- swe:coordinate name = h swe:Quantity definition = http:sweet.jpl.nasa.gov2.0spaceCoordinates.owlVertical axisID = h swe:uom code = m swe:Quantity swe:coordinate swe:Vector swe:item -- -- swe:DataChoice swe:field -- -- swe:DataRecord Listing 5 – example of a tasking parameter description including default values swe:DataRecord … -- -- swe:field name = positioningChoice swe:DataChoice … swe:item name = pointToLookAt swe:Vector … -- -- swe:coordinate name = h swe:Quantity … swe:uom code = m swe:value swe:value swe:Quantity swe:coordinate swe:Vector swe:item -- -- swe:DataChoice swe:field -- -- swe:DataRecord If an SPS uses a DataArray or Matrix in its tasking parameters description then it may provide default values that are encoded according to a description that the service also provides in that arraymatrix. As clients may safely ignore given default values, they can also ignore unknownunsupported encodings that they might encounter in a DataArrayMatrix provided by an SPS. 7.4.3 Updatable parameters AbstractDataComponents as defined in OGC 08-094 clause 7.2 provide an optional updatable attribute. This attribute is set to true if the corresponding tasking parameter can be included in an Update request. If the attribute is not set or set to false, the tasking parameter cannot be updated and thus no value for it is included in an Update request. Clients can simply strip any component from the tasking parameter description retrieved via DescribeTasking that are not updatable. The resulting description defines the structure Copyright © 2011 Open Geospatial Consortium 131 of the parameters to be included in an update request. If the data component that represents the whole tasking parameter descriptor for tasking a given procedure is not updatable then the Update operation is not realized for that procedure. Listing 6 – example of tasking parameter description with updatable and non-updatable parameters -- Update operation is implemented for procedure -- swe:DataRecord … -- Parameter not updatable -- swe:field name = taskTimeFrame swe:TimeRange … updatable = false -- -- swe:TimeRange swe:field -- Parameter is updatable -- swe:field name = positioningChoice swe:DataChoice … -- Choice item is available for Update -- swe:item name = pointToLookAt swe:Vector … -- -- swe:Vector swe:item -- Choice item is available for Update -- swe:item name = relativePositioning swe:DataRecord … -- Record field is available for Update -- swe:field name = relativeHorizontalPan swe:Quantity … -- -- swe:Quantity swe:field -- Record field is available for Update -- swe:field name = relativeVerticalPan swe:Quantity … -- -- swe:Quantity swe:field swe:DataRecord swe:item swe:DataChoice swe:field -- Parameter is updatable -- swe:field name = focalLength swe:Quantity … -- -- swe:Quantity swe:field swe:DataRecord Removing all components that are not updatable would result in the following parameter description. A client would use this description in an Update request. 132 Copyright © 2011 Open Geospatial Consortium Listing 7 – example of tasking parameter description for update request where all non-updatable parameters have been removed swe:DataRecord … swe:field name = positioningChoice swe:DataChoice … swe:item name = pointToLookAt swe:Vector … -- -- swe:Vector swe:item swe:item name = relativePositioning swe:DataRecord … swe:field name = relativeHorizontalPan swe:Quantity … -- -- swe:Quantity swe:field swe:field name = relativeVerticalPan swe:Quantity … -- -- swe:Quantity swe:field swe:DataRecord swe:item swe:DataChoice swe:field swe:field name = focalLength swe:Quantity … -- -- swe:Quantity swe:field swe:DataRecord 7.4.4 Constraintsrestrictions Most of the simple components defined in SWE Common allow provision of constraint attributes. Those can be set by SPS to constrain allowed values for tasking parameters. Listing 8 – example of constraintsrestrictions on tasking parameter values swe:DataRecord … swe:field name = taskTimeFrame -- -- swe:field swe:field name = positioningChoice swe:DataChoice optional = true swe:item name = pointToLookAt -- -- swe:item swe:item name = relativePositioning swe:DataRecord … swe:field name = relativeHorizontalPan swe:Quantity … swe:uom code = deg swe:constraint swe:AllowedValues swe:interval -180 180 swe:interval swe:AllowedValues swe:constraint swe:Quantity swe:field swe:field name = relativeVerticalPan swe:Quantity … swe:uom code = deg swe:constraint swe:AllowedValues swe:interval -90 90 swe:interval Copyright © 2011 Open Geospatial Consortium 133 swe:AllowedValues swe:constraint swe:Quantity swe:field swe:DataRecord swe:item swe:DataChoice swe:field swe:field name = focalLength swe:Quantity … swe:uom code = mm swe:constraint swe:AllowedValues swe:interval 3.5 10 swe:interval swe:AllowedValues swe:constraint swe:Quantity swe:field swe:DataRecord

7.4.5 Definition observedPropertySemantics

Each tasking parameter sets the values for a single property. The property is defined using the definition attribute of the data component. Resolving the URN can retrieve the semantics.

7.4.6 Uoms

The unit of measure UOM is defined in data component using the mechanisms described in [OGC08-094] clause 6.2.3.

7.4.7 Encoding XML, text, binary

SPS defines the supported encodings as described in clause 7.3.3.3. It is recommended to use either TextEncoding or XMLEncoding defined in OGC08-094 clause 7.6, though the advanced encoding package, which supports raw and base 64 binary blocks defined in OGC08-094 clause 7.7, can be supported as well. 8 PublishSubscribe

8.1 Introduction

The publishsubscribe functionality is an optional feature of SPS. The SPS model defines events, which can be published to interested consumers via a publishsubscribe interface see clause 10, more specifically see Figure 32 and Figure 34. The events represent state changes of a task or tasking request. However, further events can also be recognized by an SPS, for example the events defined in [OGC 09- 001]. NOTE: As discussed in chapter 17.2 of [OGC 09-001], the realization of the publishsubscribe functionality defined in this chapter shall be documented in a specific binding for this standard e.g., the realization in the SOAP binding is documented in clause 9. 134 Copyright © 2011 Open Geospatial Consortium A publishsubscribe interface may support various subscription models as explained in [OGC 09-001] and [OGC 09-032]. If supported, content based filtering using XPath 1.0 and FES 1.1 [OGC 04-095] shall be implemented as specified in clause 17.2.3 of [OGC 09-001].

8.2 SPS Events

The publishable events recognized by this standard are defined in Table 64. Requirement http:www.opengis.netspecSPS2.0reqEventseventTypes REQ 104. Any SPS implementing publishsubscribe functionality shall implement the events according to Table 64. An SPS may also recognize and publish the events defined by the SWE Service Model see OGC 09-001 clause 17.2 or any other event. Requirement http:www.opengis.netspecSPS2.0reqEventschannelBasedSubscription REQ 105. If an SPS supports channel based subscriptions see clause 8.3, it shall state the topics and thus supported events in the topic set contained in its notification metadata see clause 7.3.2.4. Table 64 — SPS Events and their encoding Event name a Event definition State transition from Æ to Encoding of the event Use at SPS that implements PublishSub scribe TaskingReque stAccepted Tasking request was accepted. Initial | Pending Æ Accepted see Table 65 mandatory TaskingReque stRejected Tasking request was rejected. Initial | Pending Æ Rejected see Table 65 optional TaskingReque stPending Tasking request is pending. Initial Æ Pending see Table 65 optional TaskingReque see Table 14 Pending Æ Rejected TaskingRequestExpi see Table mandatory