EO Satellite Tasking Extension for SPS OGC 10-135
simpleType name
= FeasibilityLevelEnumerationType
restriction base
= string
enumeration value
= SIMPLE
enumeration value
= COMPLETE
restriction simpleType
simpleType name
= FeasibilityLevelOtherType
restriction base
= string
pattern value
= other: \w{2,}
restriction simpleType
This parameter shall be encapsulated in an extension slot of a GetFeasibility request as show below:
sps:GetFeasibility xmlns:sps
= http:www.opengis.netsps2.0
xmlns:swes =
http:www.opengis.netswes2.0 xmlns:eosps
= http:www.opengis.neteosps2.0
swes:extension eosps:FeasibilityLevel
COMPLETE eosps:FeasibilityLevel
swes:extension ...
sps:GetFeasibility
Requirement http:www.opengis.netspecEOSPS2.0reqcorefeasibility-level-valid
Req 11. The FeasibilityLevel XML element shall be valid with respect to the
spsRequestExtensions.xsd schema and inserted within an extension element of the
GetFeasibility request.
7.1.3.2 ReferenceFeasibilityID Element
7.1.3.2.1 Description
The ReferenceFeasibilityID tag can be inserted within Submit or Reserve requests to reference a previously generated feasibility study. The ReferenceFeasibilityID tag can be
omitted by clients but servers shall read and store its value for the same amount of time as the feasibility study or task information itself.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreref-feasibility-id-used
Req 12. A Submit or Reserve request containing the ReferenceFeasibilityID
parameter shall be associated with the corresponding feasibility study.
After a feasibility study has been requested and approved by a client, a task with identical parameters can be submitted or reserved, provided the referred feasibility study is not
yet expired as indicated by its expiration date. See section 7.1.4.2. The provider can
Copyright ©
2011 Open
Geospatial Consortium
49
OGC 10-135 EO Satellite Tasking Extension for SPS
then make sure acquisitions are executed as closely as possible to what was agreed upon in the feasibility assessment.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreref-feasibility-id-correct
Req 13. The value of ReferenceFeasibilityID parameter shall be the identifier of an
existing and active i.e. not expired feasibility study report.
For such a request to be valid, the tasking parameters values specified in the Submit operation shall match the ones used in the previous GetFeasibility request.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreref-feasibility-id-params
Req 14. The values of tasking parameters included in a Submit or Reserve request
shall be identical to the ones used in the GetFeasibility request referred to by the
ReferenceFeasibilityID parameter.
This feature is especially useful because certain data providers consider the acceptance of a ‘complete’ feasibility study by the customer as contractually binding for both parties.
The acceptance of the feasibility study is triggered by the submission of the task via the Submit operation with a ReferenceFeasibilityID referring to a previously generated
feasibility study. Note that each data provider is responsible for specifying the exact consequences of this acceptance in its terms of services. In particular, data providers can
consider feasibility studies as informational only.
Note that the only way for a client to “accept” a feasibility study is to use the ReferenceFeasibilityID tag in a subsequent Submit or Reserve request. A tasking request
with no such tag will be processed completely separately, and in this case, the data provider is free to satisfy the request in any way desired without disclosing how it will be
done to the client.
7.1.3.2.2 XML encoding
The following schema snippet shows the global element declaration that normalizes the encoding of this parameter in XML:
element name
= ReferenceFeasibilityID
type =
string
This parameter shall be encapsulated in an extension slot of a Submit or Reserve request as show below:
sps:Submit xmlns:sps
= http:www.opengis.netsps2.0
xmlns:swes =
http:www.opengis.netswes2.0 xmlns:eosps
= http:www.opengis.neteosps2.0
50 Copyright
© 2011
Open Geospatial
Consortium
