OGC 10-135 EO Satellite Tasking Extension for SPS
An InvalidParameterValue exception shall be returned when the sensor identifier is not recognized by the service.
Requirement http:www.opengis.netspecEOSPS2.0reqgsasensor-id-valid
Req 43. The sensor parameter of a GetSensorAvailability request shall contain the
identifier of a sensor listed in the capabilities. If this is not the case, the server shall
return an exception with the code “InvalidParameterValue” as specified in [OGC 06‐
121].
82 Copyright
© 2011
Open Geospatial
Consortium
EO Satellite Tasking Extension for SPS OGC 10-135
8.2 Requirements Class: Validate Operation
Requirements Class http:www.opengis.netspecEOSPS2.0reqval
Target Type Server Implementation
Dependency http:www.opengis.netspecEOSPS2.0reqcore
8.2.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
client-side validation of acquired data segments but most requirements are also applicable to client implementations seeking to support this feature.
Requirement http:www.opengis.netspecEOSPS2.0reqvalcapabilities
Req 44. The Validate operation shall be listed in the capabilities document of the
service.
Several attempts are sometimes needed for earth observation systems to acquire satisfactory data for an area of the earth surface. For instance, optical acquisitions are
subject to cloud cover that can prevent clear imaging of the region of interest. In this case new acquisitions are performed until the region of interest is image properly.
The desired image quality is expressed when sending the programming request to the service so that the data provider can automatically select acquisitions that match the
validation criteria. However, some users want to control this validation step manually. The validate operation fulfills this need by allowing the user to stop further acquisitions
over a given cell when he is satisfied with the image quality or to request continuation of acquisitions when he is not.
8.2.2 Data model
The following UML diagram shows the exact model of the Validate operation:
Copyright ©
2011 Open
Geospatial Consortium
83
OGC 10-135 EO Satellite Tasking Extension for SPS
«DataType»
SWES Common:: ExtensibleRequest
«property» «DataType»
SWES Common:: ExtensibleResponse
«property» + service:
CharacterString + version: CharacterString
+ extension: Any [0..] + extension: Any [0..]
«DataType»
Validate
«DataType»
ValidateResponse
«property» «property»
+ task: ScopedName
+ segmentID: GenericName [1..] + result:
StatusReport
Figure 23 – UML diagram of the Validate operation
8.2.2.1 Operation request – Validate
Sending an instance of the Validate data type to the service performs an SPS EO Validate operation request.
The Validate 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. Validate 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 validated. ScopedName, value as
provided in StatusReport. One mandatory
segmentID Identifier of the acquisition segment to be
validated. All segments selected for validation shall have the status
ACQUIRED. GenericName, shall
correspond to the ID of Segment objects listed in
the ProgrammingStatus. One or more
mandatory
8.2.2.2 Operation response – ValidateResponse
The ValidateResponse data type represents the response to an SPS EO Validate operation request. It shall contain a StatusReport object similarly to many SPS operations. The
status of all segment identified in the request shall be switched to ‘VALIDATED’ unless an error occurred.
84 Copyright
© 2011
Open Geospatial
Consortium
