SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
43 The following table describes the elements of the DescribeSensor request schema:
Table 11-1- Parameters of DescribeSensor Request Name
a
Definition Data type and
values Multiplicity
and use
SensorId The sensorId parameter specifies the sensor
for which the description is to be returned. token
One mandatory
descriptionType Type of description that the server should return.
String Possible values:
- brief
- full
One mandatory
service Service type identifier
Character String
Fixed value : 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
a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
11.4. DescribeSensor operation response
A SensorML document describing the sensor system.
11.5. Exceptions
When a SPS server encounters an error while performing a DescribeSensor operation, it shall return an exception report message as specified in clause 8 of [OGC 05-008].
11.6. Examples
Example of DescribeSensor operation request:
DescribeSensor service
= SPS
version =
0.9.5 outputFormat
= textxml;subtype=SensorML1.0.0
xmlns =
http:www.opengis.netspseop xmlns:xsi
= http:www.w3.org2001XMLSchema-instance
xsi:schemaLocation =
http:www.opengis.netspseop http:ws.spotimage.comowsschemasswespseop_v0.9.5spsDescribeSensor.xsd
sensorID urn:ogc:object:feature:Sensor:SpotImage:spot5
sensorID descriptionType
brief descriptionType
DescribeSensor
DescribeSensor response example: see Annex B.
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
44
12. EstimateSensorWorkload operation optional, synchronous
The EstimateSensorWorkload provides information about the estimated workload of the requested sensor. This information is under the responsibility of each mission and must be accessible on demand by the SPS
server. The SPS server has to maintain up to date information of such workload by harvesting the information to the mission on regular basis weekly, or monthly
The minimal information provided by the mission is as follows:
Temporal domain: begin date, end date, Temporal resolution: number of days i.e. how many days between two consecutive values in a
mesh, Spatial domain: lat min, lat max, long min, long max somewhat similar to Area of service,
Spatial resolution: size of the meshes, expressed in degrees, minutes or in km Further on, the following information has to be provided for each mesh:
mesh location: lat-long coordinates of the mesh centre, mesh date or range of dates
workload value: percentage of the resource already booked on this mesh at this date
12.1. EO profile specific
The operation EstimateSensorWorkload is specific to the EO profile.
12.2. EstimateSensorWorkload operation request
Table 12-1- Attributes of EstimateSensorWorkload Request Name
a
Definition Data type and
values Multiplicity
and use
outputForm at
The outputFormat attribute specifies the desired
output format
of the
EstimateSensorWorkload operation. For the EO Profile the format will be SensorML
Character String
type Mandatory
SensorId The sensorId parameter specifies the sensor for
which the description is to be returned. token
One mandatory
service Service type identifier
Character String
Fixed value : SPS One
mandatory version
Specification version for operation Character
String type, not empty
Value is specified by
each Implementation
Specification and
Schemas version One
mandatory
a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
45
12.3. EstimateSensorWorkload operation response
Table 12-2- Parts of EstimateSensorWorkload operation response Name
Definition Data type and values
Multiplicity and use
sensorID Identifies the sensor that
shall be tasked token
one, mandatory description
Provides EstimateSensorWorkload
description complex
one to many, mandatory
12.4. Exceptions
When a SPS server encounters an error while performing a EstimateSensorWorkload operation, it shall return an exception report message as specified in clause 8 of [OGC 05-008].
12.5. Examples
Example of EstimateSensorWorkload operation request:
EstimateSensorWorkload version=
0.9.5 service=
SPS outputFormat=
textxml;subtype=sensorML1.0.0 xmlns=
http:www.opengis.netspseop SensorId
urn:ogc:object:feature:Sensor:SpotImage:spot10M SensorId
EstimateSensorWorkload
Example of EstimateSensorWorkload operation response:
EstimateSensorWorkloadResponse xmlns=
http:www.opengis.netspseop xmlns:xlink=
http:www.w3.org1999xlink SensorID
urn:ogc:object:feature:Sensor:SpotImage:spot10M sensorID
sml:SensorML xmlns:sml=
http:www.opengis.netsensorML xmlns:swe=
http:www.opengis.netswe xmlns:gml=
http:www.opengis.netgml xmlns:xsi=
http:www.w3.org2001XMLSchema-instance xmlns:xlink=
http:www.w3.org1999xlink xsi:schemaLocation=
http:www.opengis.netsensorML http:vast.uah.eduschemassensorML1.0.30basesensorML.xsd
version= 1.0
SensorID urn:ogc:object:feature:Sensor:SpotImage:spot10M
SensorID --~~~~~~~~~~~~~-------------------
-- EstimateSensorWorkload
Inputs-- --~~~~~~~~~~~~~-------------------
EstimateSensorWorkload Response
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
46
13. DescribeGetFeasibility operation optional, synchronous
13.1. Introduction
The DescribeGetFeasibility operation 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 GetFeasibility operation and eventually the description of
parameters returned in the GetFeasibility response. The only additional parameter “SensorID” defines the specific sensors that shall be described by the server. This allows servers to façade
multiple sensors that require parameterization and return all information to the client using one call only.
Because GetFeasibility operation is optional, DescribeGetFeasibility is also optional.
13.2. EO profile specific
