i. Abstract
This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking.
This OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set.
This document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program.
The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects.
ii. Keywords
ogcdoc, ogc documents, opensearch, eo, EO, hma, sps
iii. Submitting organizations
The following organizations submitted this Document to the Open Geospatial Consortium (OGC):
- Astrium Satellites Limited
- European Space Agency
- UK Space Agency
- Spacebel
- Terradue SRL
iv. Submitters
All questions regarding this submission should be directed to the editor or the submitters:
Name | Representing | OGC member |
---|---|---|
Nicolas Fanjeau | Astrium Satellites Limited | Yes |
Sebastian Ulrich | Astrium Satellites Limited | Yes |
Corentin Guillo | Catapult SA Limited | No |
v. Changes to the OGC® Abstract Specification
The OGC® Abstract Specification does not require changes to accommodate this OGC® standard.
vi. Future Work
Improvements to SPS defined in this document are desirable as enhancements to the OGC® Sensor Planning Service Interface Standard 2.1 Earth Observation Satellite Tasking Extension (OGC 10-135) undertaken within the scope of the ESA Decision Support and Real Time Earth Observation Data Management (DREAM) project. DREAM is an ESA project that will address the technology, architecture and Payload Data Ground System interfaces needed to streamline the planning, ordering and access to Earth observation missions. Two main business scenarios are covered: the European Maritime Safety Agency (EMSA), active in marine safety, and the European Union Satellite Centre (EUSC) whose mission is to support the decision making process of the European Union. Both will be reference use cases in addition to some representative users of the COPERNICUS (formerly GMES) portal and related applications[1].
vii. Foreword
This document is the specification of an OpenSearch extension for Earth Observation Satellites Tasking.
This OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set.
This OpenSearch extension takes into account:
• The OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking Extension (OGC 10-135) and its dependencies with the OGC® Sensor Planning Service Implementation Standard 2.0 (OGC 09-000) and the OGC®SWE Common Data Model Encoding Standard 2.0.0 (OGC 08-094r1).
• The OGC® OpenSearch Extension for Earth Observation Products (OGC 13-026) and its dependencies from the OGC® OpenSearch GeoSpatial and Temporal Extensions (OGC 10-032)
The arrows in black represent the applicable dependencies which impact this document while the arrows in blue represent dependencies for harmonization between two OGC documents.
This document includes three annexes; Annexes A and B are normative, and Annex C is informative.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. However, to date, no such rights have been claimed or identified.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.
viii. Introduction
The OpenSearch specification originated in a community effort built around Amazon’s A9.com. OpenSearch was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group has published in 2013 an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org.
In 2013, an extension to support the search of archived Earth Observation products ( OGC 13-026) was proposed and adopted in the context of the Ground European Network for Earth Science Interoperation - Digital Repositories (GENESI-DR) project by several European Earth Science data centres.
This first interface standard was the minimal compliance level to develop discovery mechanisms in heterogeneous sites and to transform the repository network into a virtual distributed repository.
GENESI-DR was a two years Framework Programme 7 project funded by the European Commission (EC) under the INFRASTRUCTURES-2007-1, Capacity Programme, INFRA-2007-1.2.1 Scientific Digital Repositories. The project consortium was led by ESA and included 13 partners holding several Earth Observation data repositories.
Then, following this first successful implementation, the adoption of the draft specification within the scope of the user services for the ESA Sentinel Missions and HMA Architecture Working Group’s (HMA-AWG) recommendations, in 2012 ESA financed the specification and adoption of two OpenSearch extensions (i.e. OGC 10-032 and OGC 13-026) related to the search of archived EO products within the scope of the HMA-S project.
In addition, following the progress of ESA DREAM project which is aimed at integrating heterogeneous EO sensor planning systems simulating the future Global Monitoring for Environment and Security (GMES) Collaborative Missions (GCM) capabilities, ESA and the HMA-AWG have decided to specify and submit for adoption another OpenSearch extension dedicated to EO satellites tasking (purpose of this document).
Future EO acquisitions have the same characteristics as archived EO products like the region of interest, the time of interest (but in the future), the orbit number or acquisition stations for example.; but their difference belong to their encoding method, which inherit from SWE Common (OGC 08-094) for the future acquisition and from the O&M (OGC 10-157) for the archived products.
Scope
This OGC best practice specifies an Earth Observation extension to the OpenSearch query protocol dedicated to future acquisition from satellite missions. OpenSearch is a collection of simple formats for the sharing of search results.
The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.
The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results.
Services that support the OpenSearch Specification and the Earth Observation extension defined in this document are called OpenSearch Earth Observation Services.
Conformance
Conformance with this best practice shall be checked using all the relevant tests specified in Annex A (normative) of this document. The framework, concepts, and methodology for testing, and the criteria to be achieved to claim conformance are specified in the OGC Compliance Testing Policies and Procedures and the OGC Compliance Testing web site[2].
In order to conform to this OGC Implementation Best Practice, a software implementation shall choose to implement any one of the conformance levels specified in Annex A (normative).
All requirements-classes and conformance-classes described in this document are owned by the specification identified as http://a9.com/-/opensearch/extensions/eosp/1.0/
The following table describes the conformance classes defined in this standard:
Conformance Class Name | Description | Test |
---|---|---|
OpenSearch Description | The server generates a valid OpenSearch description document. | A.1 |
OpenSearch Feasibility result | The server generates a result from a KVP search request. | A.2 |
Normative References
The following normative documents contain provisions, which, through reference in this text, constitute provisions of this document. For dated references, subsequence amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies.
- Internet Engineering Task Force (IETF): ATOM: The Atom Syndication Format
http://tools.ietf.org/html/rfc4287 - Internet Engineering Task Force (IETF): RFC 3066: Tags for the Identification of Languages
http://tools.ietf.org/html/rfc3066 - Internet Engineering Task Force (IETF): RFC 3339: Date and Time on the Internet: Timestamps
http://www.ietf.org/rfc/rfc3339.txt - Internet Engineering Task Force (IETF): RFC 5988: Web Linking
http://tools.ietf.org/html/rfc5988
http://www.iana.org/assignments/link-relations/link-relations.xhtml - OpenSearch: OpenSearch Specification 1.1
http://www.opensearch.org/Specifications/OpenSearch/1.1 - OpenSearch: OpenSearch Geo Extension
http://www.opensearch.org/Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2 - OpenSearch: OpenSearch Time Extension
http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0/Draft_1 - OpenSearch: OpenSearch Parameters Extension
http://www.opensearch.org/Specifications/OpenSearch/Extensions/Parameter/1.0 - OpenSearch: Organisation for the Advancement of Structured Information Standards (OASIS): OASIS OpenSearch - searchRetrieve: Part 4. APD Binding for OpenSearch Version 1.0, OASIS Standard, 30 January 2013
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/os/part4-opensearch/searchRetrieve-v1.0-os-part4-opensearch.html - HMA: Heterogeneous Missions Accessibility – Design Methodology, Architecture and Use of Geospatial Standards for the Ground Segment Support of Earth Observation missions ESA TM-21
http://www.esa.int/About_Us/ESA_Publications/ESA_TM-21_Heterogeneous_Missions_Accessibility - Open Geospatial Consortium (OGC): OGC 05-008r1 - OGC Web Services Common Specification
http://portal.opengeospatial.org/files/?artifact_id=8798 - Open Geospatial Consortium (OGC): OGC 06-121r9 - OWS Common Implementation Specification
http://portal.opengeospatial.org/files/?artifact_id=38867 - Open Geospatial Consortium (OGC): OGC 06-103r4 - OpenGIS® Implementation Standard for Geographic information - Simple feature access - Part 1: Common architecture
http://portal.opengeospatial.org/files/?artifact_id=25355 - Open Geospatial Consortium (OGC): OGC 10-157r4 - Earth Observation Metadata profile of Observations & Measurements
https://portal.opengeospatial.org/files/?artifact_id=59391&version=2 - Open Geospatial Consortium (OGC): OGC 10-026r4 - OpenSearch Earth Observation product Extension
http://portal.opengeospatial.org/files/?artifact_id=25218 - Open Geospatial Consortium (OGC): OGC 10-032r8 - OpenSearch GeoSpatial and Temporal Extensions
https://portal.opengeospatial.org/files/?artifact_id=56866&version=1 - Open Geospatial Consortium (OGC): OGC 08-094 - SWE Common Data Model Encoding Standard 2.0.0
http://portal.opengeospatial.org/files/?artifact_id=41157 - Open Geospatial Consortium (OGC): OGC 09-000 - Sensor Planning Service Implementation Standard 2.0
http://portal.opengeospatial.org/files/?artifact_id=38478 - Open Geospatial Consortium (OGC): OGC 10-135 - Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking Extension
http://portal.opengeospatial.org/files/?artifact_id=40185
Terms and Definitions
For the purposes of this standard, the definitions specified in Clause 4 of the OWS Common Implementation Specification [OGC 05-008] shall apply. In addition, the following terms and definitions apply.
- 4.1 OpenSearch
- Draft specification for web search syndication, originating from Amazon’s A9 project and given a corresponding interface binding by the OASIS Search Web Services working group.
- 4.2 OpenSearch Geo-Temporal Service
- Defines servers that comply with the OpenSearch Specification and the Geo-Temporal extension defined in OGC 10-032 “OpenSearch GeoSpatial and Temporal Extensions”.
- 4.3 OpenSearch Description Document
- An XML document available at a consistent location describing metadata for the service and providing templates for queries.
- 4.4 OpenSearch Earth Observation Service
- Defines servers that comply with the OpenSearch Specification and the Earth Observation extension defined in this document.
Conventions
Abbreviated terms
Some of the abbreviated terms listed in sub clause 5.1 of the OWS Common Implementation Specification (OGC 06-121) apply to this document, plus the following abbreviated terms.
- ATM
- Atmospheric
- DCP
- Distributed Computing Platform
- EC
- European Commission
- EO
- Earth Observation
- ESA
- European Space Agency
- GENESI-DR
- Ground European Network for Earth Science Interoperation - Digital Repositories
- GMES
- Global Monitoring for Environment and Security
- GCM
- GMES Collaborative Mission
- HMA
- Heterogeneous Mission Accessibility
- HMA-AWG
- HMA Architecture Working Group
- HTTP
- Hypertext Transport Protocol
- IETF
- Internet Engineering Task Force
- ISO
- International Organisation for Standardisation
- KVP
- Key Value Pair
- LTDP
- Long Term Data Preservation
- O&M
- Observations & Measurements
- OASIS
- Organisation for the Advancement of Structured Information Standards
- OPT
- Optical
- REST
- Representational State Transfer
- RSS
- Rich Site Summary
- SAR
- Synthetic Aperture Radar
- SensorML
- Sensor Model Language
- SPS
- Sensor Planning Service
- SWE
- Sensor Web Enablement
- SWS
- Search Web Services
- UML
- Unified Modelling Language
- URI
- Uniform Resource Identifier
- URL
- Uniform Resource Locator
- URN
- Uniform Resource Name
- UUID
- Universal Unique Identifier
- W3C
- World Wide Web Consortium
- WKT
- Well Known Text
- XML
- eXtensible Markup Language
UML notation
Most diagrams that appear in this standard are presented using the Unified Modeling Language (UML) static structure diagram, as described in sub-clause 5.2 of OGC 05-008.
Used parts of other documents
This document uses significant parts of document OGC 10-032. To reduce the need to refer to that document, this document copies some of those parts with small modifications. To indicate those parts to readers of this document, the largely copied parts are shown with a light grey background (15%).
Platform-neutral and platform-specific standards
As specified in Clause 10 of OGC Abstract Specification Topic 12 “OpenGIS Service Architecture” (which contains ISO 19119), this document includes both Distributed Computing Platform-neutral and platform-specific standards. This document first specifies each operation request and response in platform-neutral fashion. This is done using a table for each data structure, which lists and defines the parameters and other data structures contained.
The specified platform-neutral data could be encoded in many alternative ways, each appropriate to one or more specific DCPs. This document now specifies encoding appropriate for use of HTTP GET transfer of operations requests (using KVP encoding), and for use of HTTP POST transfer of operations requests (using XML or KVP encoding).
Data dictionary tables
The UML model data dictionary is specified herein in a series of tables.
Column title | Column contents |
---|---|
Names (left column) | Two names for each included parameter or association (or data structure). The first name is the UML model attribute or association role name. The second name uses the XML encoding capitalization specified in sub-clause 11.6.2 of [OGC 05-008]. The name capitalization rules used are specified in sub-clause 11.6.2 of [OGC 05-008]. Some names in the tables may appear to contain spaces, but no names contain spaces. |
Definition (second column) | Specifies the definition of this parameter (omitting un-necessary words such as “a”, “the”, and “is”). If the parameter value is the identifier of something, not a description or definition, the definition of this parameter should read something like “Identifier of TBD”. |
Data type and value (third column) or Data type (if are no second items are included in rows of table) | Normally contains two items: The mandatory first item is often the data type used for this parameter, using data types appropriate in a UML model, in which this parameter is a named attribute of a UML class. Alternately, the first item can identify the data structure (or class) referenced by this association, and references a separate table used to specify the contents of that class (or data structure). The optional second item in the third column of each table should indicate the source of values for this parameter, the alternative values, or other value information, unless the values are quite clear from other listed information. |
Multiplicity and use (right or fourth column) or Multiplicity (if are no second items are included in rows of table) | Normally contains two items: The mandatory first item specifies the multiplicity and optionality of this parameter in this data structure, either “One (mandatory)”, “One or more (mandatory)”, “Zero or one (optional)”, or “Zero or more (optional)”. The second item in the right column of each table should specify how any multiplicity other than “One (mandatory)” shall be used. If that parameter is optional, under what condition(s) shall that parameter be included or not included? If that parameter can be repeated, for what is that parameter repeated? |
When the data type used for this parameter, in the third column of such a table, is an enumeration or code list, all the values specified by a specific OWS shall be listed, together with the meaning of each value. When this information is extensive, these values and meanings should be specified in a separate table that is referenced in the third column of this table row.
The data type of many parameters, in the third table column, is specified as “Character String type, not empty”. In the XML Schema Documents specified herein, these parameters are encoded with the xsd:string type, which does NOT require that these strings not be empty.
The contents of these data dictionary tables are normative, including any table footnotes.
OpenSearch Extension for Earth Observation Satellite Tasking overview
As the operations of the main OpenSearch specification are expressed in the OASIS SWS bindings, we confine ourselves here to the operations for the Earth Observation Satellite Tasking extension.
However, a short overview of how they fit within the primary OpenSearch specification is provided hereafter:
The basic concept of OpenSearch is to specify how to query a web resource, and additional metadata to support syndicating the results. Search clients can use OpenSearch description documents to learn about the public interface of a search engine. These description documents contain parameterized URL templates that indicate how the search client should make search requests. Search engines can use the OpenSearch response elements to add search metadata to results in a variety of content formats. For example, if a web site allows search by the URL:
http://www.example.com?q=question
OpenSearch provides a way to define where that search term goes. Essentially it would look like: http:// www.example.com?q={searchTerms}, where {searchTerms} would be replaced by any general string. Using OpenSearch, aggregators and applications have a way to simply define a search service and let a user just type in their terms, but then search N search engines. For example, the Firefox search bar is powered by OpenSearch and allows the user to add new OpenSearch compliant site.
The Description element provides some basic metadata about the contents of the service and the contact information pertaining to it, along with a set of URL Templates which illustrate the parameters accepted by the service and the variety of output formats in which results can be obtained. The OpenSearch request interface is simple, consisting of a description of a HTTP GET request with a series of optional key-value parameters that can be used to constrain the search.
The Earth Observation Satellite Tasking Extension specifies a series of parameters that can be used to constrain search results on future acquisition capabilities. These are discussed in more detail in Section 9. In short, provision is made to filter results by:
- Region of Interest
- Time of Interest
- Acquisition Type
- Parameters of Acquisition
The purpose of this OpenSearch extension is to make sure that common elements with OGC 13-026 and OGC 10-032 are aligned and new elements specific to future acquisition respect the naming convention specified into the OGC 08-094 that defines sensor related data.
The OpenSearch description document for the satellite Tasking is an aggregation of the information available via the GetCapabilities, the DescribeTasking and the DescribeSensor operations of the EO-SPS standard. The OpenSearch search operation is mapped to the GetFeasibility operation, the response of the search operation provide for each of the results a summary and/or the link to their dedicated EO-SPS GetTask operation.
A sample of a Description showing the use of this extension with several output formats can be seen in Annex C.
Shared aspects
Not Applicable
OpenSearch Description (Requirement)
Introduction
The OpenSearch Description Document allows clients to retrieve service metadata from a server. The response to a request for a Description shall be an XML document in the form specified by the SWS OpenSearch bindings published by OASIS. A brief summary of the Description’s requirements is provided in OGC 10-032 and summarized hereafter:
The service metadata covered by the OpenSearch Description corresponds to the service metadata returned by e.g. a WMS GetCapabilities request. The request is not parameterised, but simply takes the form of an HTTP GET request to a URL (advertised on a web page or obtained from a repository of OpenSearch services which offer syndication of their result sets).
The Description document contains information on the maintainer of the service and their contact information. It includes a brief title and short abstract describing the contents of the service, along with a list of keywords and optionally a list of languages in which the contents may be returned.
The key feature of the Description document is the URL template, which instructs a client application how to issue queries to the service. The URL template represents a parameterized form of the URL by which a search engine is queried. Each response format supported by the service needs its own distinct URL template included in the Description. A service can extend the basic parameters included in the template.
EXAMPLE 1 The following XML document provides a sample response to a request for an OpenSearch Description from a repository supporting the Satellite Tasking Extension.
Note that the response type is given in the type attribute and not implicitly on the URL path
<?xml version=“1.0” encoding=“UTF-8”?>
<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/"
xmlns:geo="http://a9.com/-/opensearch/extensions/geo/1.0/"
xmlns:eo="http://a9.com/-/opensearch/extensions/eo/1.0/"
xmlns:eosp="http://a9.com/-/opensearch/extensions/eosp/1.0/">
<ShortName>Web Search</ShortName>
<Description>Use Example.com to search the Web.</Description>
<Tags>example web</Tags>
<Contact></Contact>
<Url type=“application/atom+xml” template="http://example.com/?q={searchTerms}&bbox={geo:box?}&pw={startPage?}"/>
<LongName>Example.com Web Search</LongName>
<Query role=“example” searchTerms=“opt” geo:box=”10,10,12,12”/>
<Attribution>Copyright 2005, Example.com, Inc.</Attribution>
<SyndicationRight>open</SyndicationRight>
</OpenSearchDescription>
For detail on the required and optional fields please refer to the information on Annex D of OGC 10-032.
OpenSearch Earth Observation Satellite Tasking operation
Introduction
OpenSearch Extension for Earth Observation Satellite Tasking is designed to provide a search facility for future acquisition data from Earth Observation sensors to the OpenSearch protocol.
One namespace is provided for use in URL templates that form part of the OpenSearch Description Document (see Example 1), published by the server in XML at a stable URL.
Requirements Class | |
---|---|
http://a9.com/-/opensearch/extensions/eosp/1.0/req/req-class-a | |
Target type | Token |
Requirement |
http://a9.com/-/opensearch/extensions/eosp/1.0/req/req-class-a/namespaces
This namespaces and a corresponding namespace prefix shall be included when the extension is used in an OpenSearch Description document: http://a9.com/-/opensearch/extensions/eosp/1.0/ |
OpenSearch has a lot more functionality and is especially useful when requesting syndication formats such as ATOM or RSS. The flexibility of the OpenSearch protocol allows one to return lists of search results in any format that a client can be persuaded to understand. A server provides a description document that a client reads to determine how to formulate a search/retrieve request and interpret the response.
The OpenSearch Description Document includes a mandatory URL element containing a mandatory request template. Where several request templates are provided, a client may choose the one offering the most useful format (specified by MIME-type defined in the type attribute of the element) as shown in Example 1.
Requirements Class | |
---|---|
http://a9.com/-/opensearch/extensions/eosp/1.0/req/req-class-a | |
Target type | Token |
Requirement |
http://a9.com/-/opensearch/extensions/eosp/1.0/req/req-class-a/response_payload Any server supporting the Earth Observation extension shall at least return results in Atom 1.0 |
Search operation request
Search operation request
The following table contains a comparison of search parameters between OGC 10-135 and OGC 13-026 which can be used to task EO satellite based sensors. It contains also the additional search parameters which can be used to task EO satellite based sensors but which are not offered by OGC 13-026.
This last one would be the preferred encoding choice as it is harmonized with the OGC 13-026 to search archived EO products.
The following Opensearch parameters from the Earth Observation product extension are relevant in the case of the Satellite Tasking. These parameters are not dedicated to the product data and their operations (processing, archiving…) and can be used in the step prior to the acquisition managed by the SPS and EO-SPS specifications.
Name | Definition | Data type and values | Multiplicity and use | Equivalent in OGC 10-135 | Equivalent in OGC 13-026 |
---|---|---|---|---|---|
Platform | A string identifying the platform (e.g. ENVISAT, SPOT). | Character String | One or more (optional) | N/A | eo:platform |
SensorType | A string identifying the sensor type. | Code List OPT SAR | One or more (optional) | N/A | eo:sensorType |
Instrument | A string identifying the instrument (e.g. MERIS, AATSR, ASAR, HRVIR). | Character String | One or more (optional) | Swes:procedure | eo:instrument |
RegionOfInterestPoint | The geometry is defined using the Well Known Text and supports the following 2D geographic shapes. | POINT (lat lon) in (Real [EPSG:4326]) | One (optional) | N/A | geo:lat geo: |
RegionOfInterestPolygon | The geometry is defined using the Well Known Text and supports the following 2D geographic shapes. | POLYGON ((lat1 lon1, ..., lat1 lon1)) in (Real [EPSG:4326]) | One (optional) | RegionOfInterest/GM_Polygon/Polygon | geo:geometry ((geo:lat1 geo:lon1, ..., geo:lat1 geo:lon1)) |
AcquisitionDate | A date interval requesting entries possible to acquire within a given time interval. | ISO8061 date range (yyyy-mm-dd/yyyy-mm-dd) | One (optional) | TimeOfInterest/ SurveyPeriod | time:start & time:end |
IncidenceAzimuthAngle | Range of acceptable azimuth incidence angles. The azimuth angle is the angle that the look vector (projected vertically on the earth surface) makes with the north direction. It thus indicates from which geographic direction (i.e. North, East, West, South) the region of interest should be imaged. | Real Pair (degrees) = (min/max) | One (optional) | (Mono-Stereo)acquisition / AcquisitionAngle / IncidenceRange / AzimuthAngle | N/A |
IncidenceElevationAngle | Range of acceptable elevation incidence angles. The elevation angle is the angle that the look vector makes with the local vertical. It thus indicates how vertically the region should be imaged. This is the traditional meaning of incidence angle. | Real Pair (degrees) = (min/max) | One (optional) | (Mono-Stereo)acquisition / AcquisitionAngle / IncidenceRange / ElevationAngle | eo:minimum IncidenceAngle eo:maximum IncidenceAngle |
PointingAlongTrackAngle | Range of acceptable pointing angles in the along track direction (i.e. the angle between the nadir direction and the look vector, measured around the axis of the satellite reference frame that is orthogonal to the orbit plane). | Real Pair (degrees) = (min/max) | One (optional) | (Mono-Stereo)acquisition / AcquisitionAngle / PointingRange/ AlongTrackAngle | N/A |
PointingAcrossTrackAngle | Range of acceptable pointing angles in the across track direction (i.e. the angle between the nadir direction and the look vector, measured around the axis of the satellite reference frame with a direction tangent to the satellite trajectory). | Real Pair (degrees) = (min/max) | One (optional) | (Mono-Stereo)acquisition / AcquisitionAngle / PointingRange/ AcrossTrackAngle | N/A |
MinimumLuminosity | Minimum luminosity acceptable for the acquired imagery. This constrains the solar incidence angle of the acquired imagery. | Real (%) | One (optional) | AcquisitionParameter/ AcquisitionParametersOPT / MinLuminosity | N/A |
PolarizationMode | The sensor specific parameters. | String | One (optional) | AcquisitionParameter/ AcquisitionParametersSAR / PolarizationMode | eo:polarisationMode |
CloudCover | Maximum acceptable cloud cover. The cloud cover is the portion of the image area covered by clouds. | Real (%) | One (optional) | ValidationParameters / ValidationParametersOPT / MaxCloudCover | eo:cloudCover |
SnowCover | Maximum acceptable snow coverage. The snow cover is the portion of the image area covered by snow. | Real (%) | One (optional) | ValidationParameters / ValidationParametersOPT / MaxSnowCover | eo:snowCover |
MaximumSunGlint | Maximum acceptable portion of the image covered by a sun glint effect. | Real (%) | One (optional) | ValidationParameters / ValidationParametersOPT / MaxSunGlint | N/A |
HazeAccepted | Specifies if haze is acceptable. | Boolean | One (optional) | ValidationParameters / ValidationParametersOPT / HazeAccepted | N/A |
SandWindAccepted | Specifies if sand wind is acceptable. | Boolean | One (optional) | ValidationParameters / ValidationParametersOPT / SandWindAccepted | N/A |
MaximumNoiseLevel | Maximum acceptable signal to noise ratio for each acquired imagery segment. | Real (decibel) | One (optional) | ValidationParameters / ValidationParametersSAR / MaxNoiseLevel | N/A |
MaximumAmbiguityLevel | Maximum acceptable ambiguity level for each acquired imagery segment. | Real (decibel) | One (optional) | ValidationParameters / ValidationParametersSAR / MaxAmbiguityLevel | N/A |
GroundResolution | The ground resolution is the distance between two contiguous pixels of remote sensed imagery when projected on the earth. This parameter allows the user to select a range of acceptable ground resolutions. | Real Pair (meter) = (min/max) | One or more (optional) | AcquisitionParameters / OPT-SAR AcquisitionParameters / GroundResolution | eo:resolution |
OrbitDirection | A string identifying the acquisition orbit direction. | Code List ASCENDING DESCENDING | One (optional) | N/A | eo:orbitDirection |
SensorMode | A categorical value used to specify a particular instrument configuration. All possible modes should be defined in a code space, usually specific to the type of instrument. | Character String | One or more (optional) | AcquisitionParameters / OPT-SAR AcquisitionParameters / InstrumentMode | eo:sensorMode |
CompositeType | Specifies if imagery obtained by fusing several images acquired separately and co-registered is acceptable. | Boolean | One (optional) | AcquisitionParameters / (OPT-SAR)AcquisitionParameters / FusionAccepted | eo:compositeType |
CoverageType | Specifies if the imagery should be acquired in one or multiple passes. SINGLE_SWATH: The region of interest should be covered by a single segment. MONOPASS: The region of interest must be covered by one or more segments acquired from the same orbit. MULTIPASS: The region of interest can be covered by using images extracted from several segments acquired at different dates provided that they are all acquired within the requested time period. | Code List SINGLE_SWATH, MONOPASS, MULTIPASS | One (optional) | (Mono-Stereo)acquisition / CoverageType | N/A |
Orbit number | An integer number interval requesting a range of orbit numbers. | Integer/IntegerPair | One (optional) | SwathProgrammingRequest/SwathSegment/ StartOrbit SwathProgrammingRequest/SwathSegment/ StopOrbit | orbitNumber |
Frame | An integer number interval requesting a range of orbit frame numbers. | Integer/IntegerPair | One (optional) | SwathProgrammingRequest /SwathSegment/ StartFrame SwathProgrammingRequest /SwathSegment/ StopFrame | frame |
Track | An integer number interval requesting a range of orbit track numbers | Integer | One (optional) | SwathProgrammingRequest | track |
Swath | Swath identifier (e.g. Envisat ASAR has 7 distinct swaths (I1,I2,I3...I7) that correspond to precise incidence angles for the sensor). | Integer | One (optional) | N/A | swath |
Cycle | If we start with any randomly selected pass in a satellite's orbit, an orbit cycle will be completed when the satellite retraces its path. | Integer | One (optional) | Cycle | N/A |
Search request KVP encoding (mandatory)
Note that for the given key-value pairs, the key can be an arbitrary string, specified by one given instance of an OpenSearch repository. For example, one Description may provide a URL template asking for platform={eo:platform}, another specifying plat={eo:platform}. It is the responsibility of the client application to parse the URL template and create the appropriate keys for each key-value pair. These parameter sets are templates from which URLs can be constructed. The search client must replace every instance of a template parameter with a value before the search request is performed. If a search engine wishes to indicate that a template parameter is optional and can be replaced with the empty string, then the “?” notation described in the section on optional template parameters should be used. According to the OpenSearch specification (OGC 10-032 Annex D), all the “optional” parameters and data structures in the Search operation request should be implemented by all Search clients using the specified values for each implemented search to which that parameter or data structure applies. Similarly, all the “optional” parameters and data structures should be implemented by all OpenSearch Earth Observation Servers, for each implemented Search to which that parameter or data structure applies.
All parameters of the OpenSearch query should be mapped to the appropriate feasibility result fields. For example, the generic searchTerms parameter can be mapped to a given number of elements. The following table maps the EOP for O&M (OGC 10-157r4) element name to the OpenSearch parameters.
Requirements Class | |
http://www.opengis.net/spec/opensearcheo/m.n/req/req-class-b | |
Target type | Token |
Requirement | http://www.opengis.net/spec/opensearchgeo/1.0/req/req-class-b/http_get_transfer Servers shall implement HTTP GET transfer of the Search operation request, using KVP encoding. |
Requirement | http://www.opengis.net/spec/opensearchgeo/1.0/req/req-class-b/url_parameters The KVP encoding of the Search operation request shall use the parameters specified in Table 4 |
Requirement | http://www.opengis.net/spec/opensearchgeo/1.0/req/req-class-b/search_parameters The parameters listed in Table 4 shall be as specified in Table 2 above. |
Name and example | Optionality and use | Definition and format |
---|---|---|
platform={eo: platform } | One or more (optional) | See Table 3 |
sensorType={eo:sensorType} | One or more (optional) | See Table 3 |
instrument={eo:instrument} | One or more (optional) | See Table 3 |
resolution={eo:resolution} | One or more (optional) | See Table 3 |
box={geo:box} | One (optional) | See Table 3 |
start={time:start} | One (optional) | See Table 3 |
end={time:end} | One (mandatory) | See Table 3 |
angleIncidenceAz={eosp:incidenceAzimuthAngle} | One (optional) | See Table 3 |
angleIncidenceEl={eosp:incidenceElevationAngle} | One (optional) | See Table 3 |
anglePointingAlong={eosp: pointingAlongTrackAngle} | One (optional) | See Table 3 |
anglePointingAcross={eosp: pointingAcrossTrackAngle} | One (optional) | See Table 3 |
sensorMode={eo:sensorMode} | One or more (optional) | See Table 3 |
compositeType ={eo:compositeType } | One (optional) | See Table 3 |
minLum={eosp:minimumLuminosity} | One (optional) | See Table 3 |
polMode={eosp:polarizationMode} | One or more (optional) | See Table 3 |
cloudCover={eo:cloudCover} | One (optional) | See Table 3 |
snowCover={eo:snowCover} | One (optional) | See Table 3 |
maxSunGlint={eosp:maxSunGlint} | One (optional) | See Table 3 |
haze={eosp:hazeAcepted} | One (optional) | See Table 3 |
sandWind={eosp:sandWindAccepted} | One (optional) | See Table 3 |
maxNoise={eosp:maximumNoiseLevel} | One (optional) | See Table 3 |
maxAmbiguity={eosp:maxAmbiguityLevel} | One (optional) | See Table 3 |
covType={eosp:CoverageType} | One (optional) | See Table 3 |
orbitNumber ={eo: orbitNumber} | One(optional) | See Table 3 |
frame={eo: frame} | One(optional) | See Table 3 |
cycle={eo:cycle} | One (optional) | See Table 3 |
track ={eo:track} | One (optional) | See Table 3 |
orbitDirection={eo:orbitDirection} | One (optional) | See Table 3 |
orbitNumber={eo:orbitNumber} | One (optional) | See Table 3 |
EXAMPLE 6 An example Search operation request KVP encoded for HTTP GET is:
http://example.com/foo?q=&platform=sentinel1&instrument=c-sar&end=2014-06-01
Search operation response
Normal response parameters
The normal response to a valid Search operation request shall be in one of several formats that are specified in the OpenSearch Description for a given instance. The mandatory response format is ATOM but the server may support other formats.
Normal response XML encoding
The normative response format for an OpenSearch service using the extension for EO satellite tasking shall be in ATOM 1.0.
The properties shown in the ATOM and OpenSearch namespaces are those mandated by the core specification.
Following the ATOM format the response is made of an atom:feed element that may contain several atom:entry elements. While latter describes the returned resources that respect the query performed the first describes the discovery service or search engine.
In the atom:feed element the response should include the elements listed in Table 7 “Elements of Search operation response in the atom:feed element” of the OGC 13-026 r4 and the atom:entry elements should include the elements listed in Table 6 (respecting the rules defined in [ATOM]) and Table 8 “Elements of Search operation response in the atom:entry elements describing each search result” of the OGC 13-026 r4.
The metadata for each item in the result set should provide a link to a “full” view of the result, where more detailed metadata can be provided and, when available, a direct link to the resource using the atom:link element.
Term | OGC returnable | Atom Element | Description | Mult. |
---|---|---|---|---|
Date | eop:EarthObservation /om:phenomenonTime/gml:TimePeriod |
atom:entry/ dc:date |
A date or range of dates relevant to the resource (ISO-8601). | 1 optional |
Envelope | eop:EarthObservation /om:featureOfInterest /eop:Footprint | atom:entry/ georss:* | The spatial extent or scope of the content of the resource defined with an GEORSS element | 1 optional |
GetFeasibilityResponse | eosps:GetFeasibilityResponse | atom:entry/ eosps: GetFeasibilityResponse | EO-SPS metadata | 1 optional |
The complete listing of the examples can be seen in Annex C.
Annex A: Abstract Test Suite (Normative)
A.1 OpenSearch description document
Test Purpose: | Verify that the server generates a valid OpenSearch description document. |
Test Method: | Execute an HTTP GET request to retrieve a server's description document. Verify that the response is correct XML and is valid according to the description in this standard. |
References: | Section 8 |
Test type: | Capability |
A.2 ATOM Response Type
Test Purpose: | Verify that the server defines an URL template for the ATOM response. |
Test Method: | Execute an HTTP GET request to retrieve a server's description document. Verify that an URL element with the type equal to “application/atom+xml” exists. |
References: | Section 8 |
Test type: | Capability |
A.3 Parameter options suggestion
Test Purpose: | Verify that the server implements suggestions for string parameters for the Satellite Tasking extension elements on the OpenSearch Description document. |
Test Method: | Execute an HTTP GET request to retrieve a server's description document. Verify that the URL template includes parameters. Verify that the document includes parameter elements with the attribute pattern or with child Option elements with suggested values. |
References: | Section 8 & 9.2 |
Test type: | Capability |
A.4 Parameter list suggestion for character string type parameter
Test Purpose: | Verify that the server implements a suggestion of parameters list for the Satellite Tasking extension character string type elements on the OpenSearch Description document. |
Test Method: | Execute an HTTP GET request to retrieve a server's description document. Verify that the URL template includes parameters of the character string type. Verify that the document includes a parameter element with the attribute pattern or with child Option elements with suggested values. |
References: | Section 9.2 |
Test type: | Capability |
A.5 Earth Observation range suggestion for numerical type parameter
Test Purpose: | Verify that the server implements a suggestion of parameters range for the Satellite Tasking extension numerical type elements on the OpenSearch Description document. |
Test Method: | Execute an HTTP GET request to retrieve a server's description document. Verify that the URL template includes parameters of the numeric type. Verify that the document includes a parameter element with the attribute suggesting the value range. |
References: | Section 9.2 |
Test type: | Capability |
A.6 Earth Observation foreign element
Test Purpose: | Verify that the server response includes a eosp:EarthObservationSatelliteTasking element for each entry. |
Test Method: | Submit a series of requests to the server and verify that the server responds as include a eosp:EarthObservationSatelliteTasking element for each entry. |
References: | Section 9.2 |
Test type: | Capability |
Annex B: XML Schema Documents (informative)
Not Applicable.
Note: Schemas are defined in [ATOM] for the ATOM response format and in [OASIS OPENSEARCH] for the OpenSearch Description Document.
Annex C: Examples (informative)
C.1 OpenSearch Description with Earth Observation Satellite Tasking Extension
<?xml version=“1.0” encoding=“UTF-8”?>
<OpenSearchDescription xmlns=“http://a9.com/-/spec/opensearch/1.1/”
xmlns:eo=“http://a9.com/-/opensearch/extensions/eo/1.0/”
xmlns:eosp=“http://a9.com/-/opensearch/extensions/eosp/1.0/”
xmlns:geo=“http://a9.com/-/opensearch/extensions/geo/1.0/”
xmlns:param=“http://a9.com/-/spec/opensearch/extensions/parameters/1.0/” xmlns:time=“http://a9.com/-/opensearch/extensions/time/1.0/”>
<ShortName>EO Feasibility</ShortName>
<Description>This search engine permits to retrieve feasibility results for EO Satellites</Description>
<Tags>EO, satellite, sensor, feasibility</Tags>
<Contact>johndoe@example.com</Contact>
<Url rel=“self” template=“http://127.0.0.1:8080/ HMAS-FAS-1.0-SNAPSHOT/hmas/fas/os/description” type=“text/xml”/>
<Url xmlns:parameters=“http://a9.com/-/spec/opensearch/extensions/parameters/1.0/”
type=“text/html”
template=“127.0.0.1:8080/HMAS-FAS-1.0-SNAPSHOT/hmas/fas/os/search”
parameters:method=“POST”
parameters:enctype=“application/GetFeasibilityDocument+xml”>
<Url rel=“search”
template=“127.0.0.1:8080/HMAS-FAS-1.0-SNAPSHOT/hmas/fas/os/search?q={searchterms}&platform={eo:platform?}&compositeType={eo:compositeType?}&maxAmbiguityLevel={eosp:validationParametersSARMaxAmbiguityLevel?}&cloudCover={eo:cloudCover?}&incEl={eosp:acquisitionAngleIncidenceElevation?}&sensorMode={eo:sensorMode?}&hazeAccepted={eosp:validationParametersOPTHazeAcepted?}&snowCover={eo:snowCover?}&pointAl={eosp:acquisitionAnglePointingRangeAlongTrack?}&instrument={eo:instrument?}&resolution={eo:resolution?}&maxSunGlint={eosp:validationParametersOPTmaxSunGlint?}&minLum={eosp:acquisitionParametersOPTMinimumLuminosity?}&sandWindAccepted={eosp:validationParametersOPTSandWindAccepted?}&start={time:start?}&sensorType={eo:sensorType?}&coverage={eosp:coverageType?}&maxNoiseLevel={eosp:validationParametersSARMaximumNoiseLevel?}&pointAc={eosp:acquisitionAnglePointingRangeAcrossTrack?}&box={geo:box?}&polMode={eosp:acquisitionParametersSARPolarizationMode?}&incAz={eosp:acquisitionAngleIncidenceAzimuth?}&end={time:end?}&orbitDirection={eo:orbitDirection?}&orbitNumber={eo:orbitNumber?}&frame={eo:frame?}&track={eo:track?}&cycle={eosp:cycle?}” type=“application/atom+xml”>
<param:Parameter name=“platform” title=“Platform” value=“{eo:platform}”>
<param:option label=“Sentinel1” value=“Sentinel1”/>
</param:Parameter>
<param:Parameter name=“compositeType” title=“Composite type” value=“{eo:compositeType}”>
<param:option label=“” value=“false”/>
<param:option label=“” value=“true”/>
</param:Parameter>
<param:Parameter maxInclusive=“-1” minInclusive=“0”
name=“maxAmbiguityLevel”
title=“Maximum Ambiguity Level for SAR acquisitions” value=“{eosp:validationParametersSARMaxAmbiguityLevel}"/>
<param:Parameter maxInclusive=“100” minInclusive=“0”
name=“cloudCover”
title=“Acceptable cloud coverage percent for optical acquisitions” value=“{eo:cloudCover}"/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“incEl” title=“IncidenceElevationAngle” value=“{eosp:acquisitionAngleIncidenceElevation}"/>
<param:Parameter name=“sensorMode” title=“Sensor Mode” value=“{eo:sensorMode}”>
<param:option label=“EW” value=“EW”/>
<param:option label=“IW” value=“IW”/>
<param:option label=“SM” value=“SM”/>
<param:option label=“WV” value=“WV”/>
</param:Parameter>
<param:Parameter name=“hazeAccepted”
title=“Acceptation of haze on optical images” value=“{eosp:validationParametersOPTHazeAcepted}”>
<param:option label=“” value=“false”/>
<param:option label=“” value=“true”/>
</param:Parameter>
<param:Parameter maxInclusive=“100” minInclusive=“0”
name=“snowCover”
title=“Acceptable snow coverage percent for optical acquisitions” value=“{eo:snowCover}"/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“pointAl” title=“PointingAlongTrackAngle” value=“{eosp:acquisitionAnglePointingRangeAlongTrack}"/>
<param:Parameter name=“instrument” title=“Instrument Name” value=“{eo:instrument}”>
<param:option label=“Sentinel 1 SAR” value=“S1SAR”/>
</param:Parameter>
<param:Parameter name=“resolution” title=“Ground Resolution” value=“{eo:resolution}”>
<param:option label=“20.0” value=“20.0”/>
<param:option label=“40.0” value=“40.0”/>
<param:option label=“25.0” value=“25.0”/>
<param:option label=“5.0” value=“5.0”/>
</param:Parameter>
<param:Parameter maxInclusive=“100” minInclusive=“0”
name=“maxSunGlint”
title=“Maximum sun glint percent for optical acquisitions” value=“{eosp:validationParametersOPTmaxSunGlint}"/>
<param:Parameter maxInclusive=“100” minInclusive=“0”
name=“minLum”
title=“Minimum Luminosity of an optical product” value=“{eosp:acquisitionParametersOPTMinimumLuminosity}"/>
<param:Parameter name=“sandWindAccepted”
title=“Acceptation of sand wind on optical images” value=“{eosp:validationParametersOPTSandWindAccepted}”>
<param:option label=“” value=“false”/>
<param:option label=“” value=“true”/>
</param:Parameter>
<param:Parameter maxInclusive=“9999-12-31T23:59:59Z”
minInclusive=“2013-09-16T21:50:17Z” name=“start”
title=“Start of the Time Of Interest” value=“{time:start}"/>
<param:Parameter name=“sensorType” title=“Sensor Type” value=“{eo:sensorType}”>
<param:option label=“Synthetic Aperture Radar” value=“sar”/>
</param:Parameter>
<param:Parameter name=“coverage” title=“Coverage Type” value=“{eosp:coverageType}”>
<param:option label=“SINGLE_SWATH” value=“SINGLE_SWATH”/>
<param:option label=“MULTIPASS” value=“MULTIPASS”/>
<param:option label=“MONOPASS” value=“MONOPASS”/>
</param:Parameter>
<param:Parameter maxInclusive=“-1” minInclusive=“0”
name=“maxNoiseLevel”
title=“Maximum Noise Level for SAR acquisitions” value=“{eosp:validationParametersSARMaximumNoiseLevel}"/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“pointAc” title=“PointingAcrossTrackAngle” value=“{eosp:acquisitionAnglePointingRangeAcrossTrack”/>
<param:Parameter maxInclusive=“90.0 , 180.0”
minInclusive=“-90.0 , -180.0” name=“box”
title=“Region Of Interest in the shape of a box” value=“{geo:box}"/>
<param:Parameter name=“polMode” title=“Polarisation Mode” value=“{eosp:acquisitionParametersSARPolarizationMode}”>
<param:option label=“VH” value=“VH”/>
<param:option label=“HH” value=“HH”/>
<param:option label=“VV” value=“VV”/>
<param:option label=“HV” value=“HV”/>
</param:Parameter>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“incAz” title=“IncidenceAzimuthAngle” value=“{eosp:acquisitionAngleIncidenceAzimuth”/>
<param:Parameter maxInclusive=“9999-12-31T23:59:59Z”
minInclusive=“2013-09-16T21:50:17Z” name=“end”
title=“End of the Time Of Interest” value=“{time:end}"/>
<param:Parameter name=“orbitDirection” title=“Orbit Direction”
value=“eo:orbitDirection”>
<param:option label=“ASCENDING” value=“{ASCENDING}”/>
<param:option label=“DESCENDING” value=“{DESCENDING}”/>
</param:Parameter>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“orbitNumber” title=“Orbit Number” value=“{eo:orbitNumber}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“frame” title=“Frame” value=“{eo:frame}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“cycle” title=“Cycle” value=“{eosp:cycle}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“track” title=“Track” value=“{eo:track}”/>
</Url>
</OpenSearchDescription>
C.2 OpenSearch ATOM 1.0 Response for Earth Observation Satellite Tasking Extension search.
In the example below some rules are used for:
- id: urn:uuid:“timestamp_ms”-“sensorId”-“cpt”
- title: “PlatformId”-“SensorId”-“BeginAcqTime”-“EndAcqTime”-“AcqAngle”
<atom:feed xmlns:atom=“http://www.w3.org/2005/Atom”>
<atom:title>EO feasibility for S1SAR beginning Wed Sep 18 17:38:51 BST 2013</atom:title>
<atom:id>S1SAR - </atom:id>
<atom:entry>
<atom:id>S1SAR - </atom:id>
<atom:title>EO feasibility for S1SAR beginning Wed Sep 18 17:38:51 BST 2013</atom:title>
<ns:date xmlns:ns=“http://purl.org/dc/elements/1.1/”>Wed Sep 18 17:38:51 BST 2013</ns:date>
<atom:link rel=“enclosure” href=“http://127.0.0.1:8080/HMAS-FAS-1.0-SNAPSHOT/hmas/fas/Sentinel1?service=eosps&request=GetTask&acceptFormat=application/xml&task=1”/>
<ns:GetFeasibilityResponse xmlns:ns=“http://www.opengis.net/eosps/2.0”>
<ns1:extension xmlns:ns1=“http://www.opengis.net/swes/2.1”>
<ns:FeasibilityStudy ns2:id=“” xmlns:ns2=“http://www.opengis.net/gml/3.2”>
<ns:estimatedCost uom=“”>0.0</ns:estimatedCost>
<ns:segment>
<ns:Segment ns2:id=“1”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">83.06816233065794,92.32650675881824 82.87616382555294,90.01179442577885 85.15085291052824,-0.022522488648560685 85.43334305283298,-2.376154635943016 83.06816233065794,92.32650675881824 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T09:43:02.238Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T09:45:24.908Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“2”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">70.08587928245636,90.97328220388947 70.0059197770449,90.00038000917866 85.90589488341355,-0.01179907456061203 86.24347836543997,-0.8291880823604326 70.08587928245636,90.97328220388947 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T11:17:57.910Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T11:23:35.553Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“3”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">60.00001029326065,71.25389329508941 59.93529092304281,70.58549101974334 85.8302574771214,-1.2292811557805217 86.1613009784052,0.011730173681816962 60.00001029326065,71.25389329508941 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T12:53:52.343Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T13:01:52.281Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“4”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">60.00001029326065,46.5681790093715 59.93529092304281,45.89977673402543 84.91201244459619,-2.4398116237512415 85.1808347021254,0.012789748971427595 60.00001029326065,46.5681790093715 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T14:32:36.914Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T14:40:02.314Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“5”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">60.00001029326065,21.882464723615666 59.93529092304281,21.2140624482696 81.41693946043603,-2.0370493132331733 81.57755091504171,0.005841958657873767 60.00001029326065,21.882464723615666 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T16:11:21.486Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T16:17:32.042Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
</ns:FeasibilityStudy>
</ns1:extension>
<ns:result>
<ns:StatusReport>
<ns1:identifier xmlns:ns1=“http://www.opengis.net/swes/2.1”>5</ns1:identifier>
<ns1:task xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/sps/2.1” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns1:estimatedToC xmlns:ns1=“http://www.opengis.net/sps/2.1”>2013-09-18T17:38:51.784+01:00</ns1:estimatedToC>
<ns1:percentCompletion xmlns:ns1=“http://www.opengis.net/sps/2.1”>100.0</ns1:percentCompletion>
<ns1:procedure xmlns:ns1=“http://www.opengis.net/sps/2.1”>S1SAR</ns1:procedure>
<ns1:statusMessage xmlns:ns1=“http://www.opengis.net/sps/2.1”>Feasibility analysis complete</ns1:statusMessage>
<ns1:updateTime xmlns:ns1=“http://www.opengis.net/sps/2.1”>2013-09-18T17:38:51.784+01:00</ns1:updateTime>
<ns:eoTaskingParameters>
<ns:CoverageProgrammingRequest>
<ns:RegionOfInterest>
<ns:Polygon>
<ns1:exterior xmlns:ns1=“http://www.opengis.net/gml/3.2”>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">0.0,60.0 0.0,90.0 90.0,90.0 90.0,60.0 0.0,60.0</ns:coordinates>
</ns:AbstractRing>
</ns1:exterior>
</ns:Polygon>
</ns:RegionOfInterest>
<ns:TimeOfInterest>
<ns:SurveyPeriod>
<ns1:TimePeriod xmlns:ns1=“http://www.opengis.net/gml/3.2”>
<ns1:beginPosition>2002-03-01T09:20:02Z</ns1:beginPosition>
<ns1:endPosition>2002-03-01T20:58:46Z</ns1:endPosition>
</ns1:TimePeriod>
</ns:SurveyPeriod>
</ns:TimeOfInterest>
<ns:AcquisitionType>
<ns:MonoscopicAcquisition>
<ns:CoverageType>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:CoverageType>
<ns:CoverageType>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:CoverageType>
<ns:AcquisitionAngle>
<ns:PointingRange>
<ns:AlongTrackAngle>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AlongTrackAngle>
<ns:AcrossTrackAngle>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AcrossTrackAngle>
</ns:PointingRange>
<ns:IncidenceRange>
<ns:AzimuthAngle>
<ns1:uom code=“deg” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AzimuthAngle>
<ns:ElevationAngle>
<ns1:uom code=“deg” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:ElevationAngle>
</ns:IncidenceRange>
</ns:AcquisitionAngle>
<ns:AcquisitionParameters>
<ns:AcquisitionParametersSAR>
<ns:InstrumentMode>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:InstrumentMode>
<ns:PolarizationMode>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:PolarizationMode>
<ns:FusionAccepted>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>false</ns1:value>
</ns:FusionAccepted>
</ns:AcquisitionParametersSAR>
</ns:AcquisitionParameters>
</ns:MonoscopicAcquisition>
</ns:AcquisitionType>
<ns:ValidationParameters>
<ns:ValidationParametersSAR>
<ns:MaxNoiseLevel>
<ns1:uom code=“dB” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0</ns1:value>
</ns:MaxNoiseLevel>
<ns:MaxAmbiguityLevel>
<ns1:uom code=“dB” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0</ns1:value>
</ns:MaxAmbiguityLevel>
</ns:ValidationParametersSAR>
</ns:ValidationParameters>
</ns:CoverageProgrammingRequest>
</ns:eoTaskingParameters>
</ns:StatusReport>
</ns:result>
</ns:GetFeasibilityResponse>
</atom:entry>
</atom:feed>
Annex D
(Informative)
D.1 HTTP GET request to retrieve a server’s OpenSearch Description with Earth Observation Satellite Tasking Extension
http://testserver/eosp/osd.xml
D.2 Retrieved server’s OpenSearch Description with Earth Observation Satellite Tasking Extension
<?xml version=“1.0” encoding=“UTF-8”?>
<OpenSearchDescription xmlns=“http://a9.com/-/spec/opensearch/1.1/” xmlns:eo=“http://a9.com/-/opensearch/extensions/eo/1.0/” xmlns:eosp=“http://a9.com/-/opensearch/extensions/eosp/1.0/” xmlns:geo=“http://a9.com/-/opensearch/extensions/geo/1.0/” xmlns:param=“http://a9.com/-/spec/opensearch/extensions/parameters/1.0/” xmlns:time=“http://a9.com/-/opensearch/extensions/time/1.0/”>
<ShortName>EO Feasibility</ShortName>
<Description>
This search engine permits to retrieve feasibility results for EO Satellites
</Description>
<Tags>EO, satellite, sensor, feasibility</Tags>
<Contact>johndoe@example.com</Contact>
<Url rel=“self” template=http://127.0.0.1:8080/fas/os/description type=“application/OpenSearchDescription+xml”/>
<Url xmlns:parameters=“http://a9.com/-/spec/opensearch/extensions/parameters/1.0/”
type=“text/html”
template="127.0.0.1:8080//DreamServices-1.0-SNAPSHOT/dream/os/mmfas/gmes-mmfas/search"
parameters:method=“POST”
parameters:enctype=“application/GetFeasibilityDocument+xml”>
<Url rel=“search” template="127.0.0.1:8080//DreamServices-1.0-SNAPSHOT/dream/os/mmfas/gmes-mmfas/search?q={searchterms}&platform={eo:platform?}&compositeType={eo:compositeType?}&maxSunGlint={eosp:maxSunGlint?}&cloudCover={eo:cloudCover?}&incEl={eosp:IncidenceElevationAngle?}&sensorMode={eo:SensorMode?}&hazeAccepted={eosp:hazeAccepted?}&snowCover={eo:snowCover?}&pointAl={eosp:PointingAlongTrackAngle?}&instrument={eo:Instrument?}&resolution={eo:Resolution?}&maxSunGlint={eosp:maxSunGlint?}&minLum={eosp:MinimumLuminosity?}&sandWindAccepted={eosp:sandWindAccepted?}&start={time:start?}&sensorType={eo:SensorType?}&coverage={eosp:CoverageType?}&maxSunGlint={eosp:maxSunGlint?}&pointAc={eosp:PointingAcrossTrackAngle?}&box={geo:box?}&polMode={eosp:PolarisationMode?}&incAz={eosp:IncidenceAzimuthAngle?}&end={time:end?}&orbitDirection={eo:orbitDirection?}&orbitNumber={eo:orbitNumber?}&frame={eo:frame?}&track={eo:track?}&cycle={eosp:cycle?}" type=“application/atom+xml”>
<param:Parameter name=“platform” title=“Platform” value=“{eo:platform}”>
<param:option label=“Sentinel2” value=“Sentinel2”/>
<param:option label=“Sentinel1” value=“Sentinel1”/>
</param:Parameter>
<param:Parameter name=“compositeType” title=“Composite type”
value=“{eo:compositeType}”>
<param:option label=“” value=“true”/>
<param:option label=“” value=“false”/>
</param:Parameter>
<param:Parameter maxInclusive=“-1” minInclusive=“0” name=“maxSunGlint”
title=“Maximum sun glint percent for optical acquisitions” value=“{eosp:maxSunGlint}”/>
<param:Parameter maxInclusive=“100” minInclusive=“0” name=“cloudCover”
title=“Acceptable cloud coverage percent for optical acquisitions”
value=“{eo:cloudCover}”/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“incEl” title=“IncidenceElevationAngle”
value=“{eosp:IncidenceElevationAngle}”/>
<param:Parameter name=“sensorMode” title=“Sensor Mode”
value=“{eo:SensorMode}”>
<param:option label=“WV” value=“WV”/>
<param:option label=“EW” value=“EW”/>
<param:option label=“SM” value=“SM”/>
<param:option label=“MSI” value=“MSI”/>
<param:option label=“IW” value=“IW”/>
</param:Parameter>
<param:Parameter name=“hazeAccepted” title="Acceptation of haze on
optical images" value=“{eosp:hazeAccepted}”>
<param:option label=“” value=“false”/>
<param:option label=“” value=“true”/>
</param:Parameter>
<param:Parameter maxInclusive=“100” minInclusive=“0” name=“snowCover”
title=“Acceptable snow coverage percent for optical acquisitions”
value=“{eo:snowCover}”/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“pointAl” title=“PointingAlongTrackAngle”
value=“{eosp:PointingAlongTrackAngle}”/>
<param:Parameter name=“instrument” title=“Instrument Name”
value=“{eo:Instrument}”>
<param:option label=“Sentinel 1 SAR” value=“S1SAR”/>
<param:option label=“Sentinel 2 OPT” value=“S2OPT”/>
</param:Parameter>
<param:Parameter name=“resolution” title=“Ground Resolution”
value=“{eo:Resolution}”>
<param:option label=“” value=“25.0”/>
<param:option label=“” value=“5.0”/>
<param:option label=“” value=“20.0”/>
<param:option label=“” value=“40.0”/>
</param:Parameter>
<param:Parameter maxInclusive=“100” minInclusive=“0” name=“maxSunGlint”
title=“Maximum sun glint percent for optical acquisitions”
value=“{eosp:maxSunGlint}”/>
<param:Parameter maxInclusive=“100” minInclusive=“0” name=“minLum”
title=“Minimum Luminosity of an optical product” value=“{eosp:MinimumLuminosity}”/>
<param:Parameter name=“sandWindAccepted”
title=“Acceptation of sand wind on optical images”
value=“{eosp:sandWindAccepted}”>
<param:option label=“” value=“true”/>
<param:option label=“” value=“false”/>
</param:Parameter>
<param:Parameter maxInclusive=“9999-12-31T23:59:59Z”
minInclusive=“2013-09-04T11:04:21Z” name=“start”
title=“Start of the Time Of Interest” value=“{time:start}”/>
<param:Parameter name=“sensorType” title=“Sensor Type”
value=“{eo:SensorType}”>
<param:option label=“Optical” value=“opt”/>
<param:option label=“Synthetic Aperture Radar” value=“sar”/>
</param:Parameter>
<param:Parameter name=“coverage” title=“Coverage Type”
value=“{eosp:CoverageType}”>
<param:option label=“” value=“MONOPASS”/>
<param:option label=“” value=“SINGLE_SWATH”/>
<param:option label=“” value=“MULTIPASS”/>
</param:Parameter>
<param:Parameter maxInclusive=“-1” minInclusive=“0” name=“maxSunGlint”
title=“Maximum sun glint percent for optical acquisitions”
value=“{eosp:maxSunGlint}”/>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“pointAc” title=“PointingAcrossTrackAngle”
value=“{eosp:PointingAcrossTrackAngle}”/>
<param:Parameter maxInclusive=“90.0 , 180.0”
minInclusive=“-90.0 , -180.0” name=“box”
title=“Region Of Interest in the shape of a box” value=“{geo:box}”/>
<param:Parameter name=“polMode” title=“Polarisation Mode”
value=“{eosp:PolarisationMode}”>
<param:option label=“VV” value=“VV”/>
<param:option label=“HV” value=“HV”/>
<param:option label=“VH” value=“VH”/>
<param:option label=“HH” value=“HH”/>
</param:Parameter>
<param:Parameter maxInclusive=“90 , 90” minInclusive=“-90 , -90”
name=“incAz” title=“IncidenceAzimuthAngle”
value=“{eosp:IncidenceAzimuthAngle}”/>
<param:Parameter maxInclusive=“9999-12-31T23:59:59Z”
minInclusive=“2013-09-04T11:04:21Z” name=“end”
title=“End of the Time Of Interest” value=“{time:end}”/>
<param:Parameter name=“orbitDirection” title=“Orbit Direction”
value=“eo:orbitDirection”>
<param:option label=“ASCENDING” value=“{ASCENDING}”/>
<param:option label=“DESCENDING” value=“{DESCENDING}”/>
</param:Parameter>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“orbitNumber”
title=“Orbit Number” value=“{eo:orbitNumber}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“frame”
title=“Frame” value=“{eo:frame}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“cycle”
title=“Cycle” value=“{eosp:cycle}”/>
<param:Parameter maxInclusive=“0” minInclusive=“0” name=“track”
title=“Track” value=“{eo:track}”/>
</Url>
</OpenSearchDescription>
Annex E
(Informative)
E.1 HTTP GET search request OpenSearch Earth Observation Satellite Tasking Extension to retrieve available results
http://testserver/eosp/search?q=&platform=Sentinel1&sensor=SAR&instrument=c-sar
E.2 Retrieved server’s OpenSearch feasibility results with Earth Observation Satellite Tasking Extension
In the example below some rules are used for:
- id: urn:uuid:“timestamp_ms”-“sensorId”-“cpt”
- title: “PlatformId”-“SensorId”-“BeginAcqTime”-“EndAcqTime”-“AcqAngle”
<atom:feed xmlns:atom=“http://www.w3.org/2005/Atom”>
<atom:title>EO feasibility for S1SAR beginning Tue Sep 17 11:41:07 BST 2013</atom:title>
<atom:id>S1SAR - </atom:id>
<atom:entry>
<atom:id>S1SAR - </atom:id>
<atom:title>EO feasibility for S1SAR beginning Tue Sep 17 11:41:07 BST 2013</atom:title>
<ns:date xmlns:ns=“http://purl.org/dc/elements/1.1/”>Tue Sep 17 11:41:07 BST 2013</ns:date>
<ns:GetFeasibilityResponse xmlns:ns=“http://www.opengis.net/eosps/2.0”>
<ns1:extension xmlns:ns1=“http://www.opengis.net/swes/2.1”>
<ns:FeasibilityStudy ns2:id=“” xmlns:ns2=“http://www.opengis.net/gml/3.2”>
<ns:estimatedCost uom=“”>0.0</ns:estimatedCost>
<ns:segment>
<ns:Segment ns2:id=“1”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">0.9261603190366344,134.29551226241506 83.47066734669293,90.00545584441541 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T09:20:01.272Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T09:43:10.292Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“2”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">85.55963259287697,-0.02842598877720495 71.44167545549354,90.00048829732705 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T09:45:21.202Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T11:18:20.969Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“3”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">86.25233958449165,-0.012504152076290633 60.00001029326065,71.25389329508941 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T11:23:34.655Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T12:53:52.343Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“4”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">86.1613009784052,0.011730173681816962 60.00001029326065,46.5681790093715 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T13:01:52.281Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T14:32:36.914Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
<ns:segment>
<ns:Segment ns2:id=“5”>
<ns:footprint>
<ns2:Polygon>
<ns2:exterior>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">85.1808347021254,0.012789748971427595 60.00001029326065,21.882464723615666 </ns:coordinates>
</ns:AbstractRing>
</ns2:exterior>
</ns2:Polygon>
</ns:footprint>
<ns:acquisitionStartTime>2002-03-01T14:40:02.314Z</ns:acquisitionStartTime>
<ns:acquisitionStopTime>2002-03-01T16:11:21.486Z</ns:acquisitionStopTime>
<ns:acquisitionMethod>
<eop:EarthObservationEquipment xmlns:eop=“http://earth.esa.int/eop”>
<ns2:description xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns2:identifier>SSO - S1SAR</ns2:identifier>
<eop:platform>
<eop:Platform>
<eop:shortName xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<eop:serialIdentifier>SSO</eop:serialIdentifier>
<eop:orbitType xsi:nil=“true” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</eop:Platform>
</eop:platform>
<eop:instrument>
<eop:Instrument>
<eop:shortName>S1SAR</eop:shortName>
</eop:Instrument>
</eop:instrument>
<eop:sensor>
<eop:Sensor>
<eop:sensorType codeSpace=“SAR”/>
</eop:Sensor>
</eop:sensor>
</eop:EarthObservationEquipment>
</ns:acquisitionMethod>
</ns:Segment>
</ns:segment>
</ns:FeasibilityStudy>
</ns1:extension>
<ns:result>
<ns:StatusReport>
<ns1:identifier xmlns:ns1=“http://www.opengis.net/swes/2.1”>5</ns1:identifier>
<ns1:task xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/sps/2.1” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
<ns1:estimatedToC xmlns:ns1=“http://www.opengis.net/sps/2.1”>2013-09-17T11:41:07.617+01:00</ns1:estimatedToC>
<ns1:percentCompletion xmlns:ns1=“http://www.opengis.net/sps/2.1”>100.0</ns1:percentCompletion>
<ns1:procedure xmlns:ns1=“http://www.opengis.net/sps/2.1”>S1SAR</ns1:procedure>
<ns1:statusMessage xmlns:ns1=“http://www.opengis.net/sps/2.1”>Feasibility analysis complete</ns1:statusMessage>
<ns1:updateTime xmlns:ns1=“http://www.opengis.net/sps/2.1”>2013-09-17T11:41:07.617+01:00</ns1:updateTime>
<ns:eoTaskingParameters>
<ns:CoverageProgrammingRequest>
<ns:RegionOfInterest>
<ns:Polygon>
<ns1:exterior xmlns:ns1=“http://www.opengis.net/gml/3.2”>
<ns:AbstractRing xsi:type=“ns:LinearRingType” xmlns:ns=“http://www.opengis.net/gml/3.2” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ns:coordinates decimal=“.” cs=“,” ts=" ">0.0,60.0 90.0,60.0 90.0,90.0 0.0,90.0 0.0,60.0</ns:coordinates>
</ns:AbstractRing>
</ns1:exterior>
</ns:Polygon>
</ns:RegionOfInterest>
<ns:TimeOfInterest>
<ns:SurveyPeriod>
<ns1:TimePeriod xmlns:ns1=“http://www.opengis.net/gml/3.2”>
<ns1:beginPosition>2002-03-01T09:20:02Z</ns1:beginPosition>
<ns1:endPosition>2002-03-01T20:58:46Z</ns1:endPosition>
</ns1:TimePeriod>
</ns:SurveyPeriod>
</ns:TimeOfInterest>
<ns:AcquisitionType>
<ns:MonoscopicAcquisition>
<ns:CoverageType>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:CoverageType>
<ns:CoverageType>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:CoverageType>
<ns:AcquisitionAngle>
<ns:PointingRange>
<ns:AlongTrackAngle>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AlongTrackAngle>
<ns:AcrossTrackAngle>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AcrossTrackAngle>
</ns:PointingRange>
<ns:IncidenceRange>
<ns:AzimuthAngle>
<ns1:uom code=“deg” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:AzimuthAngle>
<ns:ElevationAngle>
<ns1:uom code=“deg” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0 0.0</ns1:value>
</ns:ElevationAngle>
</ns:IncidenceRange>
</ns:AcquisitionAngle>
<ns:AcquisitionParameters>
<ns:AcquisitionParametersSAR>
<ns:InstrumentMode>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:InstrumentMode>
<ns:PolarizationMode>
<ns1:value xsi:nil=“true” xmlns:ns1=“http://www.opengis.net/swe/2.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”/>
</ns:PolarizationMode>
<ns:FusionAccepted>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>false</ns1:value>
</ns:FusionAccepted>
</ns:AcquisitionParametersSAR>
</ns:AcquisitionParameters>
</ns:MonoscopicAcquisition>
</ns:AcquisitionType>
<ns:ValidationParameters>
<ns:ValidationParametersSAR>
<ns:MaxNoiseLevel>
<ns1:uom code=“dB” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0</ns1:value>
</ns:MaxNoiseLevel>
<ns:MaxAmbiguityLevel>
<ns1:uom code=“dB” xmlns:ns1=“http://www.opengis.net/swe/2.0”/>
<ns1:value xmlns:ns1=“http://www.opengis.net/swe/2.0”>0.0</ns1:value>
</ns:MaxAmbiguityLevel>
</ns:ValidationParametersSAR>
</ns:ValidationParameters>
</ns:CoverageProgrammingRequest>
</ns:eoTaskingParameters>
</ns:StatusReport>
</ns:result>
</ns:GetFeasibilityResponse>
</atom:entry>
</atom:feed>
Revision history
Date | Release | Editor | Primary clauses modified | Description |
---|---|---|---|---|
13-06-20 | 1.0.0 | Nicolas Fanjeau Sebastian Ulrich | ALL | First release of the document |
13-08-20 | 1.1.0 | Nicolas Fanjeau Sebastian Ulrich | ALL | Second release of the document following RIDs list v1.4 from the ESA HMA-S wiki |
13-11-04 | 2.0.0 | Nicolas Fanjeau Sebastian Ulrich | ALL | Third release of the document following RIDs list v1.7 from the ESA HMA-S wiki |
Footnotes