Operation Response - GetFeasibilityResponse

Copyright © 2011 Open Geospatial Consortium 115 Table 57 – StatusReport usage for different state transitions of a GetFeasibility request property namecardin ality GetFeasibility Request State Transitions From Æ To Initial Æ Pending Initial Æ Accepted Initial Æ Rejected Pending Æ Accepted Pending Æ Rejected Pending Æ Rejected request expired task1 new identifier provided by service identifier previously provided by service estimatedToC 0..1 NA event code0..1 NA TaskingRe questExpir ed percentCompl etion0..1 NA 1 procedure1 identifier of procedure for which GetFeasibility request was made requestStatus code1 Pending Accepted Rejected Accepted Rejected Rejected statusMessage 0.. service may provide additional information to client in human readable form taskingParam eters0..1 NA 2 taskStatus code0..1 NA 3 updateTime1 point in time when transition was made alternative0.. may be provided by service StatusReport encoded as ReservationR eport no Applicable in GetFeasibility Response yes yes yes no no no NA = not applicable, means that property is not provided Notes: 1 only applicable to tasks that are being or have been executed 2 not applicable in direct response to tasking request 3 GetFeasibility does not lead to a scheduled task

7.3.11.5 Exceptions

116 Copyright © 2011 Open Geospatial Consortium Requirement http:www.opengis.netspecSPS2.0reqGetFeasibilityResponseexceptions REQ 93. When an SPS server encounters an error while performing a GetFeasibility operation, it shall return an exception message as specified in clause 7.2.

7.3.11.6 Examples

Clause 9.6 provides example XML instances for the GetFeasibility operation request and response.

7.3.12 Update Operation

7.3.12.1 Introduction

The Update operation allows SPS clients to update a successfully submittedreserved task that has not been finalized yet. Requirement http:www.opengis.netspecSPS2.0reqUpdateRules REQ 94. The client encodes the tasking parameters according to the parameter description of the DescribeTasking response. This description indicates which parameters can be updated see clause 7.4.3. The following rules apply: 1. The default value of the updatable property on a SWE Common AbstractDataComponent used for describing the syntax and semantics of tasking parameters at SPS shall have the default value true. Thus, whenever a client encounters a tasking parameter component where the updatable property is omitted, that component is considered to be updatable. If the parameter is not set, the parameter is considered as non-updateable. 2. The structure of the tasking parameters in an Update request reflect the description in the DescribeTasking response with non-updatable parameters being removed. Thus fieldsitems of DataRecordsDataChoices in the parameter description shall be removed entirely if the contained data component is not updatable. 3. Any SPS server shall reject Update requests if clients try to update non-updateable parameters. The server shall