OGC 10-135 EO Satellite Tasking Extension for SPS
Name Description
Type unit
MaxNoiseLevel Maximum acceptable signal to noise ratio for each acquired imagery
segment. Real decibel
MaxAmbiguityLevel Maximum acceptable ambiguity level for each acquired imagery segment.
Real decibel
7.3.2.2.3 SWE Common encoding
The following table and XML snippet describe how this tasking parameters group shall be encoded using the SWE Common Data Model:
Field Name Definition
Component
ValidationParameters http:www.opengis.netdefpropertyOGC-EO0sarValidationParametersSAR
DataRecord MaxNoiseLevel
http:www.opengis.netdefpropertyOGC-EO0sarMaxNoiseLevel Quantity
MaxAmbiguityLevel http:www.opengis.netdefpropertyOGC-EO0sarMaxAmbiguityLevel
Quantity swe:field
name =
ValidationParameters swe:DataRecord
definition =
http:www.opengis.netdefpropertyOGC-EO0sarValidationParametersSAR swe:field
name =
MaxNoiseLevel swe:Quantity
definition =
http:www.opengis.netdefpropertyOGC-EO0sarMaxNoiseLevel gml:name
Max Noise Level gml:name
swe:uom code
= dB
swe:Quantity swe:field
swe:field name
= MaxAmbiguityLevel
swe:Quantity definition
= http:www.opengis.netdefpropertyOGC-EO0sarMaxAmbiguityLevel
gml:name Max Ambiguity Level
gml:name swe:uom
code =
dB swe:Quantity
swe:field swe:DataRecord
swe:field
7.3.3 Tasking responses for SAR missions
The Segment objects listed in feasibility and task status reports and corresponding to imagery segments acquired by SAR instruments can make use of the Acquisition class
defined in the SAR package of the EO Metadata standard [OGC 10-157] instead of the Acquisition class defined in the core EOP package.
This class defines additional acquisition metadata specific to SAR instruments such as polarization mode and channels, antenna look direction, etc…
76 Copyright
© 2011
Open Geospatial
Consortium
EO Satellite Tasking Extension for SPS OGC 10-135
8 Additional operations and SOAP binding
8.1 Requirements Class: GetSensorAvailability Operation
Requirements Class http:www.opengis.netspecEOSPS2.0reqgsa
Target Type Server Implementation
Dependency http:www.opengis.netspecEOSPS2.0reqcore
8.1.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
retrieval of future sensor availability but most requirements are also applicable to client implementations seeking to support this feature.
Requirement http:www.opengis.netspecEOSPS2.0reqgsacapabilities
Req 40. The GetSensorAvailability operation shall be listed in the capabilities
document of the service.
An EO system may not be available over a period of time for different reasons such as workload, maintenance, etc. The GetSensorAvailability operation allows the client to
obtain a preview of the periods of availability of a sensor before a feasibility study is requested.
The granularity of the provided information is up to the data provider who can choose to describe its exact workload or simply list approximate periods of availability. For
instance, a provider may wish to list a period of one week as soon as the sensor is available for tasking at least during 50 of the period. This allows a provider to choose
the most appropriate granularity of information to help the users while maintaining its exact workload secret.
8.1.2 Data model
The following UML diagram shows the exact model of the GetSensorAvailability operation:
Copyright ©
2011 Open
Geospatial Consortium
77
