SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
47 The following table describes the elements of the DescribeGetFeasibility request schema:
Table 13-1: - Parameters in DescribeGetFeasibility operation request Name
a
Definition Data type and values
Multiplicity and use
service Service type identifier
Character String type, not empty fixed:
Value is
OWS type
abbreviation: SPS One mandatory
version Specification version for
operation Character String type, not empty
Value is specified by each OGC standard and Schemas version
One mandatory
sensorID Defines sensor to be
described token
One mandatory a
The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
13.4. DescribeGetFeasibility operation response
If the client provides a valid sensorID cf. capabilities, the SPS server will respond with a DescribeGetFeasibilityResponse. Schema of the DescribeGetFeasibility response:
Figure 13-2: - DescribeGetFeasibility response schema
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
48 The following table describes the elements of the DescribeGetFeasibility response schema:
Table 13-2: Parts of DescribeGetFeasibility operation response Name
Definition Data type and values
Multiplicity and use
InputParameters Provides the parameters of
a GetFeasibility request Complex
type Contains a description
and a
list of
ParameterDescriptor one, mandatory
OutputParameters Describe the parameters
returned in the response. EO profile: list of pseudo
scenes scenes which may be acquired.
Complex type
Contains a description and
a list
of ParameterDescriptor
one, optional
13.5. Exceptions
When a SPS server encounters an error while performing a DescribeGetFeasibility operation, it shall return an exception report message as specified in Subclause 7.4 of [OGC 05-008].
13.6. Examples
Example of DescribeGetFeasibility request:
DescribeGetFeasibility service=
SPS version=
0.9.5 xmlns=
http:www.opengis.netspseop sensorID
urn:ogc:object:feature:Sensor:SpotImage:spot5 sensorID
DescribeGetFeasibility
Example of DescribeGetFeasibility response: See annex B of this document.
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
49
14. DescribeSubmit operation mandatory, synchronous
14.1. Introduction
The DescribeSubmit operation request allows SPS clients to request the information necessary to prepare a programming request targeted at the sensors that are supported by the SPS and that are
selected by the client. The server will return information about all parameters that have to be set by the client in order to perform a Submit operation.
Because Submit operation is mandatory, DescribeSubmit is also mandatory.
14.2. EO profile specific
- This operation is inherited of the OGC 07-014 operation DescribeTasking.
-
TaskingDescriptor
has been renamed
ParameterDescriptor
and has been modified see § 9.1. -
The DescribeSubmit response contains two elements :
InputParameters
list and description of parameters required to perform a Submit and
OutputParameters
list and description of parameters returned in the Submit response.
14.3. DescribeSubmit operation request
Schema of the DescribeSubmit request:
Figure 14-1 - DescribeSubmit request schema
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
50 The following table describes the elements of the DescribeSubmit request schema:
Table 14-1: - Parameters in DescribeSubmit operation request Name
a
Definition Data type and values
Multiplicity and use
service Service type identifier
Character String type, not empty fixed:
Value is
OWS type
abbreviation: SPS One mandatory
version Specification version for
operation Character String type, not empty
Value is specified by each OGC standard and Schemas version
One mandatory
sensorID Defines sensor to be
described token
One mandatory a
The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
14.4. DescribeSubmit operation response
