OGC 10-135 EO Satellite Tasking Extension for SPS
This parameter shall be encapsulated in an extension slot of a Submit or Reserve request as show below:
sps:Submit service
= SPS
version =
2.0 xmlns:sps
= http:www.opengis.netsps2.0
xmlns:swes =
http:www.opengis.netswes2.0 xmlns:eosps
= http:www.opengis.neteosps2.0
swes:extension eosps:ManualValidation
true eosps:ManualValidation
swes:extension ...
sps:Submit
Requirement http:www.opengis.netspecEOSPS2.0reqvalmanual-validation-valid
Req 49. The ManualValidation XML element shall be valid with respect to the
spsRequestExtensions.xsd schema and inserted within an extension element of the
Submit or Reserve XML request.
88 Copyright
© 2011
Open Geospatial
Consortium
EO Satellite Tasking Extension for SPS OGC 10-135
8.3 Requirements Class: SubmitSegmentByID Operation
Requirements Class http:www.opengis.netspecEOSPS2.0reqsid
Target Type Server Implementation
Dependency http:www.opengis.netspecEOSPS2.0reqcore
8.3.1 Introduction
This section defines an additional operation that can be implemented by EO SPS servers and clients. The standardization target of this class is a server implementation supporting
the selection of individual segments for tasking but most requirements are also applicable to client implementations seeking to support this feature.
Requirement http:www.opengis.netspecEOSPS2.0reqsidcapabilities
Req 50. The SubmitSegmentByID operation shall be listed in the capabilities
document of the service.
The SubmitSegmentByID operation can be used by deterministic missions to allow the user to request the acquisition of only some of potential segments identified in a
feasibility study report.
8.3.2 Data model
Like for all other SPS operations, the SubmitSegmentByID request and response classes are derived from common abstract classes defined in the SWE Service Model standard
and inherited from the SPS standard. The following UML diagram shows the exact model of the operation:
Copyright ©
2011 Open
Geospatial Consortium
89
OGC 10-135 EO Satellite Tasking Extension for SPS
«DataType»
SWES Common:: ExtensibleRequest
«property» + service:
CharacterString + version:
CharacterString + extension: Any [0..]
«DataType»
SubmitSegmentByID
«property» + task:
ScopedName + segmentID: GenericName [1..]
Figure 24 – UML diagram of the SubmitSegmentByID operation
8.3.2.1 Operation request – SubmitSegmentByID
Sending an instance of the SubmitSegmentByID data type to the service performs an SPS EO SubmitSegmentByID operation request.
The SubmitSegmentByID data type is derived from the ExtensibleRequest data type specified in the SWE Service Model standard [OGC 09-001] and therefore inherits all the
properties contained in that data type. SubmitSegmentByID does not restrict the content model of ExtensibleRequest. It shall contain the properties defined for ExtensibleRequest.
In addition, it shall include the properties listed in the following table.
Name Definition
Data Type Multiplicity
task Identifier of the task that contains the
segment to be acquired. ScopedName, value as
provided in StatusReport. One mandatory
segmentID Identifier of the planned or potential
segment to be acquired. GenericName, shall
correspond to the ID of Segment objects listed in
a FeasibilityStudy object. One or more
mandatory
8.3.2.2 Operation response – SubmitResponse
The response to the SubmitSegmentByID request shall be a SubmitResponse data type as defined in the Sensor Planning Service standard.
90 Copyright
© 2011
Open Geospatial
Consortium
