SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
72 The following table describes the elements of the Cancel request schema:
Table 18-1: Parameters in Cancel operation request Name
a
Definition Data type and values
Multiplicity and use
service Service type identifier
Character String type, not empty Value is OWS type abbreviation
“SPS” One mandatory
version Specification version for
operation Character String type, not empty
Equals the
number of
this document
One mandatory
ID Identifies the task to be
cancelled token
one mandatory a
The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
18.4. Cancel request acknowledgment
See § 8.3. Note: when the value of the status element is “confirmed”, it does not mean that the task is
cancelled or will be cancelled. It only means that the server has successfully received the Cancel request and that this request will be processed. The client must wait for the asynchronous Cancel
response to know if the task is cancelled.
18.5. Cancel response
Schema of the Cancel response:
Figure 18-5 - Cancel response schema
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
73 The following table describes the elements of the Cancel response schema:
Table 18-2: Parts of Cancel operation response Name
Definition Data type and values
Multiplicity and use
ID Identifies the task
token one mandatory
status String
Possible values are: -
task cancelled -
cancellation rejected one mandatory
description further
information in
continuous text String
one optional
18.6. Cancel response acknowledgement
See § 8.3.
18.7. Exceptions
When a SPS server encounters an error while performing a Cancel operation, it shall return an exception report message as specified in Subclause 7.4 of [OGC 05-008].
18.8. Examples
Example of Cancel operation request:
Cancel xmlns
= http:www.opengis.netspseop
service =
SPS version
= 0.9.5
ID 433
ID Cancel
Example of Cancel asynchronous response when the task has been successfully cancelled:
CancelResponse xmlns
= http:www.opengis.netspseop
ID 433
ID status
task cancelled status
CancelResponse
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
74
19. DescribeResultAccess operation mandatory, synchronous
19.1. Introduction
The DescribeResultAccess operation allows SPS clients to retrieve information where the observed data can be accessed from. For the EO Application profile, the response should either
point to an OGC Web Service desirable option or to a datastore accessible using FTP. The link to the acquired data is needed to close the acquisition loop and provide an access to the data or a
preview of this data to validate the image acquired.
19.2. EO profile specific
DescribeResultAccess request: taskID replaced by ID. Reason: homogeneity with other operations request.
19.3. DescribeResultAccess operation request
Schema of the DescribeResultAccess request:
Figure 19-1: - DescribeResultAccess request schema
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
75 The following table describes the elements of the DescribeResultAccess request schema:
Table 19-1: Parameters in DescribeResultAccess operation request Name
a
Definition Data type and values
Multiplicity and use
service Service type identifier
Character String type, not empty Value is OWS type abbreviation
“SPS” One mandatory
request Operation name
Character String type, not empty Value
is operation
name ”DescribeResultAccess”
One mandatory
version Specification version for
operation Character String type, not empty
Equals the
number of
this document
One mandatory
ID Identifies task taskID
Token one
mandatory; if
sensorID is not used sensorID
If specified the service will return the services
which will serve the data when acquired
b
. Token
one mandatory; if ID is not used
a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
b Allows the client to know if it can deal with the service serving the data before sending a submit request.
19.4. DescribeResultAccess operation response
