OGC 10-135 EO Satellite Tasking Extension for SPS
Exception Codes Applicable
OperationNotSupported Yes MissingParameterValue Yes
InvalidParameterValue Yes VersionNegotiationFailed No
InvalidUpdateSequence No OptionNotSupported No
NoApplicableCode Yes InvalidRequest Yes
An InvalidParameterValue exception shall be returned when the task identifier does not correspond to an existing non-expired feasibility study.
Requirement http:www.opengis.netspecEOSPS2.0reqsidtask-id-valid
Req 53. The task parameter of a SubmitSegmentByID request shall contain the
identifier of an existing and active feasibility study. If this is not the case, the server
shall return an exception with the code “InvalidParameterValue” as specified in
[OGC 06‐121].
An InvalidParameterValue exception shall be returned when segment identifiers listed in the request do not correspond to the ones listed in a previously generated feasibility
report and with a status different from ‘REJECTED’.
Requirement http:www.opengis.netspecEOSPS2.0reqsidsegment-id-valid
Req 54. The segmentID parameter of a SubmitSegmentByID request shall contain
the identifier of a feasible segment listed in the status report of the selected
feasibility study. If this is not the case, the server shall return an exception with the
code “InvalidParameterValue” as specified in [OGC 06‐121].
92 Copyright
© 2011
Open Geospatial
Consortium
EO Satellite Tasking Extension for SPS OGC 10-135
8.4 Requirements Class: SOAP binding
8.4.1 Introduction
This class defines additional requirements so that operations defined in this standard can be accessible via the HTTPSOAP binding. Implementations seeking conformance to this
requirements class shall implement the SOAP binding for all operations defined in [OGC 09-000] as well as the ones defined in this document and supported by the service.
All requirements related to the SOAP binding defined in the SPS 2.0 standard [OGC 09-000] are applicable. In particular, exceptions shall be returned in the format
specified and the correct SOAP action URIs shall be used with the corresponding message facets without changes.
8.4.2 Action URIs
When using the SOAP binding to access the operations defined in this standard, the SOAP actions listed in the following table shall be used:
Message Facet SOAP Action URI
GetSensorAvailability http:www.opengis.neteosps2.0GetSensorAvailability
GetSensorAvailabilityResponse http:www.opengis.neteosps2.0GetSensorAvailabilityResponse
Validate
http:www.opengis.neteosps2.0Validate
Requirements Class http:www.opengis.netspecEOSPS2.0reqsoap
Target Type Server Implementation
Dependency http:www.opengis.netspecEOSPS2.0reqcore
Dependency http:www.opengis.netdocISSPS2.0clause9
Requirement http:www.opengis.netspecEOSPS2.0reqsoapall-operations
Req 55. The EO SPS implementation shall allow access to all supported operations
via the SOAP binding defined in [OGC 09‐000].
Requirement http:www.opengis.netspecEOSPS2.0reqsoapdependency-sps
Req 56. An EO SPS implementation passing the “SOAP binding” conformance class
shall first pass the “SOAP” conformance class of [OGC 09‐000].
Copyright ©
2011 Open
Geospatial Consortium
93
OGC 10-135 EO Satellite Tasking Extension for SPS
ValidateResponse http:www.opengis.neteosps2.0ValidateResponse
SubmitSegmentByID http:www.opengis.neteosps2.0SubmitSegmentByID
Requirement http:www.opengis.netspecEOSPS2.0reqsoapaction-uris
Req 57. The proper SOAP action URI shall be used when calling EO SPS operations
via the SOAP binding version 1.1 or 1.2.
8.4.3 Asynchronous call to GetFeasibility with WS-Addressing
When the SOAP binding is implemented, asynchronous behavior of the GetFeasibility operation using WS-Addressing is required to be implemented in addition to the
synchronous version and in accordance with the ReplyTo mechanism defined in the WS- Addressing standard from W3C [W3C WS-A].
Requirement http:www.opengis.netspecEOSPS2.0reqsoapgf-wsa-support
Req 58. The EO SPS implementation shall support asynchronous access to the
GetFeasibility operation by using WS‐Addressing ReplyTo mechanism.
When the GetFeasibility operation is called with a WS-Addressing ReplyTo element in the SOAP header, the server shall send a single GetFeasibiltyResponse to the ReplyTo
URL and this response shall contain the final feasibility study report.
Requirement http:www.opengis.netspecEOSPS2.0reqsoapgf-wsa-single-response
Req 59. When the header of the SOAP GetFeasibility request contains the ReplyTo
element, a single response shall be sent to the ReplyTo URL.
94 Copyright
© 2011
Open Geospatial
Consortium
