esrin FedEO FEDEO CLIENT PARTNER GUIDE Prepared by Yves Coene Reference HMASE-SPB-D Issue 1 Revision 0 Document Type TN Distribution

Transcription

1 esrin FedEO Prepared by Yves Coene Reference HMASE-SPB-D Issue 1 Revision 0 Status Issued Document Type TN Distribution

2 The copyright of this document is vested in the European Space Agency. This document may only be reproduced in whole or in part, stored in a retrieval system, transmitted in any form, or by any means electronically, mechanically, or by photocopying, or otherwise, with the prior written permission of the Agency. Page 2/116

3 Title FedEO Client Partner Guide Issue 1 Revision 0 Authors Date 05/02/2014 Yves Coene Tri Tran Minh Minh Nguyen Quang Patrick Jacques Approved by PPhilippe Mougnaud (ESA) Andrea Della Vecchia (ESA) Date Reason for change Issue Revision Date Initial issue /02/2014 Issue 1 Revision 0 Reason for change Date Pages Paragraph(s) Page 3/116

4 Table of contents: 1 INTRODUCTION Purpose Scope Glossary Acronyms Definition of Terms References Applicable Documents Reference Documents Document Overview GENERAL DESCRIPTION Function and Purpose Relation to Other Systems FedEO Systems Contact Information FEDEO QUERY INTERFACE Main Principles Dataset Series Unique Search Interface Loose binding Explain Operation SearchRetrieve Operation Main OpenSearch Description Document Dataset series-specific OpenSearch Description Document Search Parameters Search Responses Links to Metadata Metadata embedded as foreign markup EOP O&M Metadata example ISO Metadata example Dublin Core Metadata example Thumbnail, Browse and Mask information Exceptions FEDEO CLIENT PARTNER IMPLEMENTATION OUTLINE Client starts from FedEO Dataset Series Catalogue Client starts from FedEO Clearinghouse Capabilities CATALOGUE CONNECTORS ASF Connector Dataset series metadata Dataset metadata Search Parameters Response Formats Examples CWIC Connector Dataset series metadata Dataset metadata Search Parameters Response Formats Examples...62 Page 4/116

5 5.3 OGC Connector Dataset series metadata Dataset metadata Search Parameters Response Formats Examples G-POD Connector Dataset series metadata Search Parameters Response Formats Examples Dataset metadata Search Parameters Response Formats Examples Virtual Archive 4 Connector Dataset series metadata Search Parameters Response Formats Examples Dataset metadata Search Parameters Response Formats Examples ISO Dataset Series Catalogue Connector Dataset series metadata Search Parameters Response Formats Examples Appendix A Explain Document Appendix B Dataset Series Search Parameters Appendix C Dataset Search Parameters Page 5/116

6 Table of figures: Figure 1: Top-level view of FedEO Environment Figure 2: Dataset Series Hierarchy (extract) Figure 3: Dataset Series as assets of metadata records (extract) Figure 4: FedEO search results shown by Google Maps Figure 5: Responses containing metadata information Figure 6: EOP O&M Metadata Model (source: [RD.1]) Figure 7: FedEO Collection Search Results in Firefox Figure 8: ASF search result in Atom format shown in Firefox Figure 9: CWIC search result in Atom format shown in Firefox Figure 10: OGC search result in Atom format shown in Firefox Figure 11: OGC search result in RSS format shown in Firefox Figure 12: EOP:ESA:GPOD-EO dataset series search result shown in Firefox Figure 13: EOP:ESA:GPOD-EO dataset search result shown in Firefox Figure 14: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series search result shown in Firefox Figure 15: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset search result shown in Firefox Figure 16: Product downloads protected by the ESA EO Single Signon system Figure 17: OGC search result in Atom format shown in Firefox Table of tables: Table 1: Applicable Documents Table 2: Reference Documents Table 3: Explain document sections Table 4: Search Parameters (Dataset series and Datasets) Table 5: Additional Search Parameters (Dataset Series) Table 6: Values for dc:type Table 7: Values for relation Table 8: Record Schemas and Atom link media type Table 9: List of exception codes Table 10: FedEO Dataset Series Catalogues Table 11: Search Parameters (Datasets) Table 12: ASF Supported Media Types Table 13: ASF Supported Record Schemas Table 14: Search Parameters (Datasets) Table 15: CWIC Supported Media Types Table 16: CWIC Supported Record Schemas Table 17: OGC Connector Supported Media Types Table 18: OGC Connector Supported Record Schemas Table 19: EOP:ESA:GPOD-EO Supported Media Types (Dataset Series) Table 20: EOP:ESA:GPOD-EO Supported Record Schemas (Dataset Series) Table 21: EOP:ESA:GPOD-EO Supported Media Types (Datasets) Table 22: EOP:ESA:GPOD-EO Supported Record Schemas (Datasets) Table 23: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Media Types Table 24: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Record Schemas Table 25: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Media Types (Datasets) Table 26: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Record Schemas (Datasets) Page 6/116

7 Table 27: Search Parameters Table 28: ISO Dataset Series Connector Supported Media Types Table 29: ISO Dataset Series Connector Supported Record Schemas Table of examples: Example 1: Simple request with SRU parameter names Example 2: Request OSDD for a dataset series Example 3: Request dataset series metadata Example 4: Search request with geo:name parameter Example 5: Dataset series search request with URI of concept Example 6: ISO metadata with semantic annotation Example 7: Atom links pointing to dataset metadata Example 8: Request EOP O&M metadata Example 9: Request ISO metadata Example 10: Request DC metadata Example 11: Inclusion of Quicklook information Example 12: Inclusion of Cloud mask information Example 13: Search response in case of exceptions Example 14: Simple dataset series search request Example 15: Extract of dataset series search result Example 16: Simple dataset search request Example 17: ASF dataset search request Example 18: CWIC dataset search request (metadata link) Example 19: CWIC dataset search request (ISO metadata) Example 20: CWIC dataset search request (DC metadata) Example 21: OGC dataset search request (Atom) Example 22: OGC dataset search request (RSS) Example 23: EOP:ESA:GPOD-EO dataset series search request Example 24: EOP:ESA:GPOD-EO dataset search request Example 25: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series search request Example 26: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series metadata (extract) Example 27: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset search request Example 28: OGC Connector search request Example 29: EOP:ESA:FEDEO:COLLECTIONS dataset series metadata (extract) Page 7/116

8 1 INTRODUCTION 1.1 Purpose This document provides technical information about the external interfaces offered by FedEO and is intended to help developers to develop client applications accessing discovery, ordering and online data access services offered by FedEO. Note: The current version of the document covers only the OpenSearch discovery interfaces of FedEO. 1.2 Scope The Federated Earth Observation Missions (FedEO) initiative was initially an OGC pilot activity aimed to refine OGC specifications relevant to Earth Observation. The same OGC specifications have subsequently been implemented in support of the GMES programme, in particular to provide interoperable access to catalogues from European Earth Observation Missions and support the subsequent ordering of data in support of the European Commissions' GMES Service Projects. The resulting interoperable catalogue is presented here as the FedEO Clearinghouse, providing discovery, ordering 1 and on-line data access services for space based Earth Observation missions from over 25 years, as a potential contribution to GEO GEOSS. The FedEO Clearinghouse brings together the catalogues from ESA, e-geoss, EUMETSAT, DLR, DMC, DMI, MDA, SPOT and VITO, as well as the catalogue of data contributed to the International Disaster for Space and Major Disasters and access to Alaska Satellite Facility and the CEOS WGISS Integrated Catalog. The development of the OGC specifications used are developed and maintained in a series of initiatives under an umbrella known as Heterogeneous Missions Accessibility. The HMA Projects are overviewed by the HMA Architecture Working Group and the Ground Segment Coordination Body (GSCB). The relevant links for the HMA community are available in [RD1] for further reference. 1 The ordering interfaces available through the FedEO Clearinghouse are the subject of a separate document (to be published). Page 8/116

9 1.3 Glossary Acronyms ANSI AOI API CEOS COTS CSV CSW CWIC DC DLR EO EOP ESA ESRIN FTP GIS G-POD GMES GML GSCB GSCDA GUI HMA HTML HTTP I/F ICD IDN IETF INSPIRE ISO JPEG JSP KML N/A OASIS OGC American National Standards Institute Area of Interest Application Programming Interface Committee on Earth Observation Satellites Commercial Off The Shelf Comma Separate Values Catalogue Services for the Web CEOS WGISS Integrated Catalog Dublin Core Deutschen Zentrums für Luft- und Raumfahrt Earth Observation Earth Observation Product European Space Agency European Space Research Institute File Transfer Protocol Geographic Information System Grid Processing on Demand Global Monitoring for Environment and Security Geography Mark-up Language Ground Segment Coordination Body GMES Space Component Data Access Graphical User Interface Heterogeneous Missions Accessibility Hyper Text Mark-up Language Hyper Text Transfer Protocol Interface Interface Control Document International Directory Network Internet Engineering Task Force Infrastructure for Spatial Information in Europe International Standards Organization Joint Photographic Experts Group Java Server Pages Keyhole Markup Language Not Applicable Organisation for the Advancement of Structured Information Standards Open GeoSpatial Consortium Page 9/116

10 O&M OSDD QoS RDF RDFS RSS SOA SOAP SRU SSO URL W3C WGISS WSDL XML XSL Observations & Measurements OpenSearch Description Document Quality of Service Resource Description Framework Resource Description Framework Schema RDF Site Summary Service Oriented Architecture Simple Object Access Protocol Search/Retrieval via URL Single Signon Uniform Resource Locator World Wide Web Consortium Working Group on Information Systems and Services Web Services Definition Language extensible Markup Language Extensible Style Language Definition of Terms For an extensive list of terms, we refer to [RD.1]. Collection Dataset Dataset series Granule IDN Product Datasets sharing the same product specification. A collection typically corresponds to the series of products derived from data acquired by a sensor on board a satellite and having the same mode of operation. Source: [RD.1]. Observations obtained by satellite instruments. Source: [RD.1]. Collection of datasets sharing the same product specification. In HMA, the term is used as a synonym for a collection of (Earth observation) data. Source: ISO 19113, ISO 19114, ISO19115 and [RD.1]. The smallest aggregation of data that can be independently managed (described, inventoried, and retrieved). Granules have their own metadata model and support values associated with the additional attributes defined by the owning collection. Source: [RD.16]. Same meaning as dataset. The CEOS International Directory Network, a Gateway to the world of Earth Science data and services accessible at Source: [RD.16]. Same meaning as dataset. Page 10/116

11 1.4 References Applicable Documents Ref. Title Code Version Date [AD.1] [AD.2] [AD.3] [AD.4] [AD.5] [AD.6] [AD.7] [AD.8] [AD.9] [AD.10] [AD.11] OGC r8, OGC OpenSearch GeoSpatial and Temporal Extensions, OGC r3, OGC OpenSearch Extension for Earth Observation Products. RFC 6573, The Item and Collection Link Relations, RFC 4287, The Atom Syndication Format, OGC r3, Earth Observation Metadata profile of Observations & Measurements, OGC r4, Earth Observation Metadata profile of Observations & Measurements. ISO 19139, Geographic Information Metadata XML (ISO 19139:2007), OpenSearch/Extensions/SRU/1.0/Draft_1 arch/ Extensions/Semantic/1.0/Draft_1 searchretrieve: Part 7. Explain Version 1.0, OASIS Standard, 05/09/ /12/2013 April /01/ DRAFT DRAFT 1 30 January 2013 [AD.12] searchretrieve: Part 4. APD Binding for OpenSearch Version 1.0, OASIS Standard, [AD.13] OGC r9, OGC Web Services Common Standard, [AD.14] meter/1.0/draft_2 [AD.15] Media RSS Specification, Table 1: Applicable Documents DRAFT 2 30 January Reference Documents Ref. Title Code Version Date [RD.1] Heterogeneous Missions Accessibility (HMA), Design methodology, Architecture and Use of geospatial Standards for the Ground Segment April 2012 Page 11/116

12 Ref. Title Code Version Date [RD.2] [RD.3] Support of Earth Observation Missions, European Space Agency, ESA TM-21, ISBN , OGC r5, Catalogue Services Specification 2.0 Extension Package for ebrim (ISO/TS ) Application Profile. INSPIRE Technical Guidance for the Implementation of the INSPIRE Download Services, Guidance_Download_Services_v3.1.pdf /08/2013 [RD.4] OGC r2, Ordering Services for Earth Observation Products [RD.5] OGC r2, OGC KML [RD.6] DCMI Metadata Terms, [RD.7] OGC r8, User Management for Earth Observation Services. Version 08/09/ [RD.8] OGC r3, OGC Cataloguing of ISO Metadata (CIM) Using the Version 14/12/2009 ebrim profile of CS-W [RD.9] OGC r1, OGC I15 (ISO19115 Metadata) Extension Package Version 11/10/2013 of CS-W ebrim Profile 1.0 [RD.10] OGC r1, EO Collection and Service Discovery using the ebrim Version 26/03/2013 Application Profile of CSW 2.0, [RD.11] [RD.12] OGC r5, OGC Catalogue Services Specification 2.0, Extension Package for ebrim Application Profile: Earth Observation Products. Version [RD.13] CWIC Client Partner Guide, CWIC-DOC r1, CWIC Technical V1.0 03/12/2012 Document, [RD.14] searchretrieve: Part 0. Overview Version 1.0, OASIS Standard, January 2013 overview/searchretrieve-v1.0-os-part0-overview.html [RD.15] searchretrieve: Part 3. searchretrieve Operation: APD Binding for SRU 2.0, Version 1.0, OASIS Standard, 30 January 2013 open.org/search-ws/searchretrieve/v1.0/cs01/part3- sru2.0/searchretrieve-v1.0-cs01-part3-sru2.0.html [RD.16] CWIC Client Partner Guide CWIC-DOC r1 V [RD.17] [RD.18] [RD.19] [RD.20] OGC r2, Semantic annotations in OGC standards, INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO and EN ISO 19119, pdf Google Data APIs, Protocol Reference, V1.3 29/10/2013 Page 12/116

13 Ref. Title Code Version Date [RD.21] OGC , OpenGIS Catalogue Services Specification ISO Version /07/2007 Metadata Application Profile, Version 1.0,, Table 2: Reference Documents 1.5 Document Overview Chapter-1 of this document defines the information that can be found in the document and references the list of Applicable and Reference documents. Chapter-2 provides a general description of the FedEO environment, its relation to other systems and provides contact information. Chapter-3 specifies in detail the FedEO query interface based on OpenSearch. It explains its main principles, the search parameters, and the search response format. Chapter 4 describes two use cases for FedEO clients, one starting from a dataset series catalogue and another one accessing immediately the dataset catalogue. Chapter-5 provides more details on the catalogue connectors and discusses how their corresponding dataset series and dataset metadata can be discovered, in which formats and what the limitations are of the FedEO Query Interface for the corresponding dataset series. Finally, the appendices provide the following reference information: Appendix A includes an example of an Explain document, which corresponds to an OGC-like capabilities document describing the search interface. Appendix B includes a summary table of search parameters supported by the various dataset series catalogues accessible through FedEO. Appendix C includes a summary table of search parameters supported by the various dataset catalogues accessible through FedEO. Page 13/116

14 2 GENERAL DESCRIPTION 2.1 Function and Purpose The FedEO Clearinghouse provides a unique access point for discovering, ordering and accessing Earth Observation (EO) dataset series and datasets. 2.2 Relation to Other Systems The FedEO Clearinghouse (shown as FedEO in the diagram below) provides a unique access point to a growing number of scientific catalogues and services. Figure 1: Top-level view of FedEO Environment The data providers currently reachable through FedEO include: ESA EO-DAIL, part of the ESA CDS and the GMES Space Component Data Access (GSCDA), offering dataset series from GMES Contributing Missions, ESA G-POD, ESA M2CS offering dataset series from ESA missions including ERS, ENVISAT etc. Page 14/116

15 ESA SuperSite Virtual Archive 4, DLR EO Web, EUMETSAT Catalogue, VITO Catalogue. In addition, the following external systems are also made available through FedEO: CEOS WGISS Integrated Catalog, Alaska Satellite Facility. The table below gives an overview of the number of dataset series accessible as of end of December Dataset Series # Dataset Series ESA EO-DAIL 61 ESA G-POD 331 ESA M2CS 20 ESA SuperSite Virtual Archive 4 16 DLR EO Web 16 EUMETSAT Catalogue 13 VITO Catalogue 1 Alaska Satellite Facility FedEO Systems There are two FedEO Clearinghouse instances you have as developer access to: FedEO Operational System: This is the currently operational system and is accessible to all users. It can be found at FedEO Test Environment: This is a test system area used by partners and FedEO developers to test before changes to the FedEO system go operational. It is currently located at and will eventually become available at 2 Products from 19 different platforms according to the Web site Page 15/116

16 2.4 Contact Information The FedEO Clearinghouse is operated by the RSS team at ESRIN which can be contacted at More information can be found as well on the HMA Wiki pages at Page 16/116

17 3 FEDEO QUERY INTERFACE 3.1 Main Principles Dataset Series FedEO is built around the concept of dataset series. It helps to consider each dataset series as a set of metadata records. One such metadata record can either describe another dataset series or an individual dataset (i.e. product). Each dataset series is identified by an identifier which allows addressing search requests to a particular dataset series and receiving metadata records as part of the search response. An extract of the FedEO dataset series hierarchy is depicted below. Figure 2: Dataset Series Hierarchy (extract) All identifiers shown in the above diagram in a rectangle with rounded corners (e.g. EOP:ESA:GPOD-EO) identify sets of dataset series metadata or dataset series catalogues. Performing a search request on such dataset series will return dataset series metadata. These metadata will include information on how to search for datasets inside the dataset series as well. The dataset series EOP:ESA:FEDEO is the default dataset series. It groups the dataset series shown just below as its children. It can be used to search the other dataset series catalogues with a single search request and thus supports distributed search. The identifiers not shown inside a rectangle (i.e. the leaves of the tree) identify sets of dataset metadata. Performing a search request on such dataset series will return dataset metadata. These metadata may include information on how to access the datasets inside the dataset series as well. The figure below illustrates how dataset series and dataset metadata are related and are represented by different metadata types. Page 17/116

18 EOP:ASF EOP:VITO:VGT_S10 ATS_TOA_1P MSG_SEVIRI Dataset Series metadata EOP:ESA:FEDEO:COLLECTIONS EOP:ESA:GPOD-EO : : : : Dataset metadata EOP:VITO:VGT_S10 MSG_SEVIRI Metadata Legend: ISO OGC RDF Figure 3: Dataset Series as assets of metadata records (extract) Note that there are many more dataset series than the ones depicted in Figure 1. The complete list can be found in the Explain document (See section 3.2 and Appendix A). The dataset series identifier is passed in an OpenSearch search request as {dc:subject} or {eo:parentidentifier}. The default dataset series identifier is EOP:ESA:FEDEO. Note 1 The use of {dc:subject} is deprecated. Developers are encouraged to use {eo:parentidentifier} to identify the applicable dataset series in OpenSearch requests. When a dataset series search returns Atom entries representing dataset series, they contain a <dc:identifier> element which corresponds to the dataset series identifier to be used in a subsequent dataset search. Page 18/116

19 It should be noted that dataset series identifiers may not be unique, e.g. ASA_IM 0P exists in both the G-POD catalogue and the Virtual Archive catalogue. To make dataset series identifiers unique in a search request, they can be prefixed as shown below: EOP:ESA:EO-VIRTUAL-ARCHIVE4:ASA_IM 0P EOP:ESA:GPOD-EO:ASA_IM 0P Unique Search Interface There is only a single URL to be used for discovering dataset series and datasets. Clients can request different media types or record schemas through this unique URL. This interface is encapsulated as an OpenSearch interface [AD.12] and its implementation is aligned where possible with section 3.1 of the SearchRetrieve operation [RD.15]. This means that the following (SRU) request parameters are available: query startrecord maximumrecords recordschema httpaccept Additional request parameters are added to support a large set of search parameters defined in OGC [AD.2] and OGC [AD.3]. The names of these additional parameters are to be discovered in the OpenSearch Description Document (OSDD). The mapping of these parameters on the OpenSearch parameters is shown in Table 4. Example 1: Simple request with SRU parameter names Formatted for readability: httpaccept = application/atom+xml & recordschema = iso & startrecord = 1 & maximumrecords = 10 & query = VITO URL-encoded: dschema=iso&startrecord=1&maximumrecords=10&query=vito The example above illustrates the FedEO Search Interface. The first part is formatted for readability: the query string is not URL encoded, white space is introduced, and KVP pairs are on separate lines. The second part is formatted for actual use with a URL-encoded query string. Page 19/116

20 3.1.3 Loose binding Not all dataset series may support the same list of search parameters. If a search parameter is not supported by a dataset series, it will in most cases by silently ignored. However, requesting for a media type or a record schema not supported for a dataset series will result in an exception. Future versions of the query interface may support a strict parameter as in [RD.20] which will default to false, which is the current behaviour. 3.2 Explain Operation The Explain operation allows FedEO clients to retrieve additional service metadata not available in the OSDD. The response to this request is an XML document (a.k.a. Explain document) containing service metadata about the FedEO OpenSearch interface as defined in [AD.11]. The Explain document for FedEO can be found at the following address: The response contains the following main sections: Section Description Example serverinfo Binding and service endpoint information. The <host>+<database> names constitute the URL used in the OpenSearch OSDD. <host>fedeo.esa.int</host> <port>80</port> <database>opensearch/ request</database> databaseinfo Administrative information about the service endpoint. indexinfo schemainfo Contains lists of supported values for OpenSearch parameters which are enumerations, e.g. dataset series identifiers Schemas (including identifier, short name and XML schema file URL) supported by {sru:recordschema} OpenSearch parameter eo:parentidentifier or dc:subject allowed values to be used in OpenSearch requests, e.g. <supports type="value">eop:vito:vgt_p </supports> om OGC r3 EO Profile of Observations and Measurement Version 1.0. om11 OGC r4 EO Profile of Observations and Measurement Version 1.1. iso ISO configinfo dc Dublin Core Page 20/116

21 responseformats List of different response formats (i.e. Media types) supported by the OpenSearch endpoint application/atom+xml Table 3: Explain document sections Note that not all response formats and all schemas found in this Explain document are applicable to all dataset series. To obtain the precise list of response formats and schemas available for a given dataset series, you should consult the OpenSearch Description Document (OSDD) for this dataset series as explained in the next section. An example of the Explain document is included in Annex A. 3.3 SearchRetrieve Operation FedEO provides an OpenSearch interface [AD.12] aligned where possible with the SearchRetrieve operation [RD.15] for retrieving dataset series or dataset metadata. The parameters accepted by this operation and the media types returned by the operation are described in the FedEO OpenSearch Description Document (OSDD) and are mainly taken from OGC [AD.2] and OGC [AD.3] Main OpenSearch Description Document The FedEO OpenSearch Description Document can be found 3 at: For the current document, we refer to the Internet. Below, we show its content as of October <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:time=" xmlns:eo=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:dc=" xmlns:semantic=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url type="application/opensearchdescription+xml" rel="self" template=" <Url type="application/opensearchdescription+xml" rel="search" template=" &subject={dc:subject?}"/> <!-- Url Templates for product search --> <Url type="application/atom+xml" template=" entifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={ startindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbo 3 Note that the FedEO OpenSearch Description contain a Url element which contains an HTTP URI for the OpenSearch document itself as per INSPIRE Technical Guidance Requirement 40 in [RD.3]. We will thus not systematically provide the location of the file in this document. It can be derived from the examples. Page 21/116

22 x={geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&amp ;uid={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}& platformserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensorty pe={eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}& amp;orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionsta tus?}&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection ={eo:orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathident ifier?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acq uisitionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:pr ocessorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisit ionsubtype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}& amp;completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthang le={eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&am p;polarisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&an tennalookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}& amp;maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&am p;incidenceanglevariation={eo:incidenceanglevariation?}&type={dc:type?}&title={dc:title?}&am p;stylesheet={sru:stylesheet?}&recordschema={sru:recordschema?}"/> <Url type="application/rss+xml" template=" ntifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={s tartindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox ={geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}& uid={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&p latformserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortyp e={eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&a mp;orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstat us?}&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection= {eo:orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidenti fier?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acqu isitionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:pro cessorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisiti onsubtype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}&a mp;completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangl e={eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&amp ;polarisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&ant ennalookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&a mp;maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&amp ;incidenceanglevariation={eo:incidenceanglevariation?}&type={dc:type?}&title={dc:title?}&amp ;stylesheet={sru:stylesheet?}&recordschema={sru:recordschema?}"/> <Url type="application/sru+xml" template=" ntifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={s tartindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox ={geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}& uid={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&p latformserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortyp e={eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&a mp;orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstat us?}&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection= {eo:orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidenti fier?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acqu isitionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:pro cessorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisiti onsubtype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}&a mp;completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangl e={eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&amp ;polarisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&ant ennalookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&a mp;maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&amp ;incidenceanglevariation={eo:incidenceanglevariation?}&type={dc:type?}&title={dc:title?}&amp ;stylesheet={sru:stylesheet?}&recordschema={sru:recordschema?}"/> <Url type="application/rdf+xml" template=" ntifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={s tartindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox ={geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}& uid={geo:uid?}&platformshortname={eo:platformshortname?}&instrumentshortname={eo:instruments Page 22/116

23 hortname?}&sensortype={eo:sensortype?}&stylesheet={sru:stylesheet?}&recordschema={sru:re cordschema?}"/> <!-- Url Templates for collection search --> <Url type="application/atom+xml" rel="collection" template=" entifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={ startindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&typ e={dc:type?}&title={dc:title?}&publisher={dc:publisher?}&bbox={geo:box?}&name={geo:n ame?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&organiza tionname={eo:organizationname?}&producttype={eo:producttype?}&classifiedas={semantic:classif iedas?}"/> <Url type="application/rss+xml" rel="collection" template=" ntifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={s tartindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&type ={dc:type?}&title={dc:title?}&publisher={dc:publisher?}&bbox={geo:box?}&name={geo:na me?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&organizat ionname={eo:organizationname?}&producttype={eo:producttype?}&classifiedas={semantic:classifi edas?}"/> <Url type="application/sru+xml" rel="collection" template=" entifier={eo:parentidentifier?}&subject={dc:subject?}&query={searchterms?}&startrecord={ startindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&typ e={dc:type?}&title={dc:title?}&publisher={dc:publisher?}&bbox={geo:box?}&name={geo:n ame?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&organiza tionname={eo:organizationname?}&producttype={eo:producttype?}&classifiedas={semantic:classif iedas?}"/> <!-- Example Queries for product search --> <Query role="example" eo:parentidentifier="eop:mda-gsi:rsat2_segments"/> <Query role="example" eo:parentidentifier="eop:dmi:deimos-1_l1r"/> <Query role="example" dc:subject="eop:dmcii:dmc_l1r"/> <Query role="example" dc:subject="er02_sar_raw_0p" searchterms="california"/> <Query role="example" eo:parentidentifier="eop:mda-gsi:rsat2_segments" geo:box="-74,17,- 67,20.5"/> <Query role="example" dc:subject="eop:mda-gsi:rsat2_segments" geo:box="-74,17,-67,20.5" time:start=" t00:00:00z" time:end=" t00:00:00z"/> <Query role="example" eo:parentidentifier="eop:spot:multispectral_10m" time:start=" T00:00:00Z" time:end=" t05:00:00z" eo:platformshortname="spot" eo:instrumentshortname="hrg-nb2" eo:sensortype="optical"/>... </OpenSearchDescription> In this description document, the interfaces for dataset discovery have a <Url> template without rel attribute or with the attribute set to results. The interfaces for dataset series discovery have a <Url> template with the rel attribute set to collection. This convention is recommended by RFC 6573 [AD.3]. The <Url> with rel set to self is present to comply with [RD.3]. FedEO dataset series may support multiple media types for returning results. They should at least support Atom responses (i.e. application/atom+xml). Note 2 The media types supported by FedEO are listed in the OSDD. Only the Atom interface is the subject of the current document. The other interfaces have to be considered experimental and should be used with care. Although the above OSDD lists several <Url> templates, they all point to the same physical interface (i.e. the SearchRetrieve operation) which can be found at the following address: Page 23/116

24 3.3.2 Dataset series-specific OpenSearch Description Document The OSDD document defined in the previous section is applicable to all FedEO dataset series. To allow a client to find the exact list of search parameters, record schemas and media types supported for a given dataset series, clients can access a dataset series specific OSDD document as shown below. Example 2: Request OSDD for a dataset series Formatted for readability: parentidentifier=eop:vito:vgt_s10 URL-encoded: T_S10 The dataset series-specific OSDD can be accessed directly by a client with a request as shown above. In addition, this OSDD can also be referred to from inside dataset series metadata discovered through the dataset series search. Example 3: Request dataset series metadata Formatted for readability: httpaccept = application/atom+xml & type = collection & startrecord = 1 & maximumrecords = 10 & query = VITO URL-encoded: collection&startrecord=1&maximumrecords=10&query=vito Among the VITO dataset series returned is the VGT S10 dataset series which includes in its Atom metadata the following Atom link with relation search : <link href=" EOP:VITO:VGT_S10" rel="search" type="application/opensearchdescription+xml"/> The dataset series-specific OSDD for the above example is shown below. <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:time=" xmlns:eo=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:param=" /spec/opensearch/extensions/parameters/1.0/" xmlns:dc=" Page 24/116

25 <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url type="application/opensearchdescription+xml" rel="self" template=" <Url type="application/atom+xml" template=" entifier=eop:vito:vgt_s10&subject=eop:vito:vgt_s10&query={searchterms?}&startrecord={sta rtindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={ geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&ui d={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&pla tformserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortype= {eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&amp ;orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus?}&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={e o:orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifi er?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquis itionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:proce ssorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisition SubType={eo:acquisitionSubType?}&startTimeFromAscendingNode={eo:startTimeFromAscendingNode?}&amp ;completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle= {eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&p olarisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&anten nalookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&amp ;maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&i ncidenceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <Url type="application/rss+xml" template=" ntifier=eop:vito:vgt_s10&subject=eop:vito:vgt_s10&query={searchterms?}&startrecord={star tindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={g eo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid ={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&plat formserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortype={ eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}& orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus? }&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={eo :orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifie r?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquisi tionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:proces sorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisitions ubtype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}& completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle={ eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&po larisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&antenn alookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}& maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&in cidenceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <Url type="application/sru+xml" template=" ntifier=eop:vito:vgt_s10&subject=eop:vito:vgt_s10&query={searchterms?}&startrecord={star tindex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={g eo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid ={geo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&plat formserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortype={ eo:sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}& orbittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus? }&acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={eo :orbitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifie r?}&cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquisi tionstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:proces sorname?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisitions ubtype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}& completiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle={ eo:illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&po larisationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&antenn alookdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}& Page 25/116

26 maximumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&in cidenceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <param:parameter name="recordschema" value="{sru:recordschema}"> <param:option value="om" label="o&m"/> <param:option value="om11" label="o&m Version 1.1"/> </param:parameter> <param:parameter name="sensortype" value="{eo:sensortype}"> <param:option value="limb" label="limb Looking/Sounding Sensor"/> <param:option value="radar" label="radar Sensor"/> <param:option value="optical" label="optical Sensor"/> <param:option value="altimetric" label="altimetric Sensor"/> <param:option value="atmospheric" label="atmospheric Sensor"/> </param:parameter> <param:parameter name="orbittype" value="{eo:orbittype}"> <param:option value="leo" label="low Earth Orbit"/> <param:option value="geo" label="geosynchronous Earth Orbit"/> </param:parameter> <param:parameter name="productionstatus" value="{eo:productionstatus}"> <param:option value="rejected" label="data acquisition has been rejected for whatever reason"/> <param:option value="potential" label="potential data acquisition"/> <param:option value="planned" label="data acquisition planned"/> <param:option value="failed" label="data acquisition failed"/> <param:option value="cancelled" label="data acquisition cancelled"/> <param:option value="acquired" label="data acquired"/> <param:option value="archived" label="data acquisition archived"/> </param:parameter> <param:parameter name="acquisitiontype" value="{eo:acquisitiontype}"> <param:option value="calibration" label="calibration"/> <param:option value="nominal" label="nominal"/> <param:option value="other" label="other"/> </param:parameter> <param:parameter name="orbitdirection" value="{eo:orbitdirection}"> <param:option value="ascending" label="ascending"/> <param:option value="descending" label="descending"/> </param:parameter> <param:parameter name="imagequalitydegradation" value="{eo:imagequalitydegradation}"> <param:option value="nominal" label="data acquisition passed a quality check with success"/> <param:option value="degraded" label="data acquisition passed a quality check and degradations were found"/> </param:parameter> <param:parameter name="polarisationmode" value="{eo:polarisationmode}"> <param:option value="s" label="single"/> <param:option value="d" label="dual"/> </param:parameter> <param:parameter name="polarisationchannels" value="{eo:polarisationchannels}"> <param:option value="hh" label="hh"/> <param:option value="vv" label="vv"/> <param:option value="hh,hv" label="hh,hv"/> <param:option value="vv,vh" label="vv,vh"/> </param:parameter> <param:parameter name="antennalookdirection" value="{eo:antennalookdirection}"> <param:option value="left" label="left"/> <param:option value="right" label="right"/> </param:parameter>... </OpenSearchDescription> Page 26/116

27 This dataset series-specific OSDD provides the following useful information: Media types supported: application/atom+xml, application/rss+xml and application/sru+xml. These are the allowed values for the httpaccept parameter. Record schemas supported: om and om11. The schema this corresponds to can be found in the Explain document, i.e. EOP Observations and Measurements. This is the allowed value for the recordschema parameter for this dataset series. The allowed values of enumeration parameters (such as recordschema above) are included using the OpenSearch Parameter Extension [AD.14]. We do not insert the <Parameter> element as a child of <Url>. Not having it as a child means that it applies to all <Url> in the OSDD Search Parameters The search parameters supported depend on whether the search is for dataset series or datasets and may differ per dataset series. The meaning of most parameters is clearly explained in the applicable specifications [AD.1], [AD.2], [AD.3] and is not repeated here. We provide a reference to the specification instead. When the specification is not sufficient or subject to interpretation, we provide additional information. For the full list of search parameters supported, we refer to the corresponding OSDD or to the appendices B (Dataset series) and C (Datasets). SRU Parameter name [RD.15] OpenSearch Parameters Reference to definition and comments Parameter value query {searchterms} [AD.1] free text. Interpretation (if any) depends on dataset series. {dc:subject} Same as {eo:parentidentifier}. See {eo:parentidentifier}. {eo:parentidenti fier} [AD.3] Identifies the dataset series to be searched. If absent, then a (wide) dataset series search is assumed. Valid values and default value are defined in the Explain document. {time:start} [AD.2] Default value : not present {time:end} [AD.2] Default value : not present {geo:box} [AD.2] When geo:box is specified, the search is done with this geographic constraint. {geo:lat} {geo:lon} {geo:name} [AD.2] [AD.2] [AD.2]. requires the presence of {geo:radius} When geo:name is specified, it is converted to geo:box by FedEO unless backend catalogue supports {geo:name} directly. Page 27/116

28 SRU Parameter name [RD.15] OpenSearch Parameters Reference to definition and comments Parameter value The parameter should correspond to a place name known to the gazetteer at {geo:radius} [AD.2] used in combination with {geo:name}. Expressed in meter. If {geo:box} is not specified then FedEO converts this into a geo:box with length and width equal to radius*2. The center of the geo:box is the position of {geo:name} if specified or the geographical location corresponding to {geo:lon} and {geo:lat} if both are specified. Default is meter or 100 km (configurable). {geo:uid} [AD.2] Identifier of an entry in the dataset series. maximumrecor ds {count} [AD.1] Max. number of results per page. Default is 10 (configurable). startrecord {startindex} [AD.1] Default startindex is url@indexoffset with default 1 recordschema {sru:recordsche ma} [AD.9] If absent, a response is generated with atom:links to the metadata record(s). See Table 8. om generates a response with the EOP O&M metadata embedded as foreign markup. iso generates a response with the ISO metadata embedded as foreign markup. dc generates a response with Dublin core metadata embedded as foreign markup. Not all dataset series support all recordschemas listed above. The above values are short names defined in the Explain document and bound to the record schema in the Explain document. Future versions may support EO GML, JSON etc. If the value server-choice 4 is used, then the server will return a response with metadata included as foreign markup. A single response may then contain different types of metadata for each dataset series. This avoid 4 See Page 28/116

29 SRU Parameter name [RD.15] OpenSearch Parameters Reference to definition and comments Parameter value a client having to ask for specific metadata. httpaccept url@type N/A Any of media (MIME) types defined in OpenSearch URL template as type e.g. application/atom%2bxml or application/rss%2bxml or application/sru%2bxml. The values to be put are in principle short names defined in the Explain document and bound to the MIME type in the same Explain document. FedEO uses as short names the actual MIME type names. This parameter is similar to the alt parameter in [RD.20]. {eo:xxx} [AD.3] Table 4: Search Parameters (Dataset series and Datasets) Additional search parameters only applicable to FedEO dataset series are given in the table below. SRU Parameter name [RD.15] OpenSearch Parameters Reference to definition and comments Parameter value query {searchterms} [AD.1] free text. Interpretation (if any) depends on dataset series. In case of ISO metadata, is mapped on title, keyword or abstract. {dc:publisher} [RD.6] Organisation publishing the metadata. For example: VITO {dc:type} [RD.6] Possible values are defined in the DCMI Type Vocabulary 5 : Collection, Service and other types. Default is Collection. {eo:organisation Name} [AD.3] See {dc:publisher} 5 Page 29/116

30 SRU Parameter name [RD.15] OpenSearch Parameters Reference to definition and comments Parameter value {eo:producttype } [AD.3] Identifier (or part of it) corresponding to a dataset series identifier, e.g. the gmd:fileidentifier in the ISO metadata record for the dataset series. E.g. EOP:VITO:VGT_S10 or MSG_SEVIRI. {dc:title} [RD.6] {semantic:classif iedas} [AD.10] For example: emet/concept/4678 Table 5: Additional Search Parameters (Dataset Series) The table below clarifies the mapping of the DCMI Type names which are to be used. DCMI type name (dc:type) HMA / FedEO terminology Comment Dataset dataset Also called product. Collection Service dataset series service Table 6: Values for dc:type Instead of providing a bounding box (geo:box), FedEO supports the {geo:name} and {geo:radius} search parameters to limit the search area. The example below searches for IKONOS datasets with less than 10% cloud cover overlapping with a bounding box of 2 km around Paris. The location name provided has to exist in the GeoNames gazetteer. Example 4: Search request with geo:name parameter Formatted for readability: httpaccept = application/atom+xml & parentidentifier = EOP:EGEOS:EGEOS#IKONOS & startdate = T00:00:00Z & name = paris & radius = 1000 & cloudcover = 10] URL-encoded: tidentifier=eop%3aegeos%3aegeos%23ikonos&startdate= T00:00:00Z&name=paris&radius=1000&cloudCover=10%5D Page 30/116

31 Modifying the httpaccept parameter in the above request to return an RSS response allows the results, including footprints, to be shown directly in Google Maps 6 as depicted below. Note that Google Maps does not support all variants of GEO RSS however. Figure 4: FedEO search results shown by Google Maps Part of the FedEO dataset series has ISO metadata with semantic annotations from GEMET 7 included. For instance, the concept Land use is identified by the (resolvable) URI The following example shows how to query for dataset series with this keyword. Example 5: Dataset series search request with URI of concept Formatted for readability: httpaccept = application/atom+xml Page 31/116

32 & subject = EOP:ESA:FEDEO:COLLECTIONS & classifiedas = URL-encoded: ct=eop:esa:fedeo:collections&classifiedas= ept/4678 Selecting one of the metadata records returned allows verifying that the ISO metadata was indeed semantically annotated as depicted below. Example 6: ISO metadata with semantic annotation The mechanism to include semantic annotations in FedEO dataset series, follows the best practice defined in OGC r2 [RD.17] Search Responses The search response returned depends on the media type requested (e.g. Atom, RSS, etc.), the record schema requested (e.g. EOP O&M, ISO, etc) and the dataset series which is searched. In some cases (e.g. Atom), clients can request to receive the metadata embedded in the Atom feed or have the Atom entries pointing to external metadata records. This distinction is schematically shown in the figure below. Page 32/116

33 Record schema (items) e.g. OGC , ISO 19139, etc. Media type (container) e.g. Atom, RSS, SRU, RDF, : : (2) Response with metadata as links (1) Response with metadata as foreign markup Figure 5: Responses containing metadata information The supported media types in which a search response can be requested depend on the dataset series. Clients can find out which media types are supported by inspecting the dataset seriesspecific OSDD (See section 3.3.2). They can ask for a specific mediatype using the httpaccept parameter. Clients can also ask for a specific record schema to be used inside the media type using the recordschema parameter. Table 8 lists the different possible values for the recordschema parameter. The structure of the Atom response is explained in the applicable specifications [AD.2], [AD.3] and is not repeated here. The current section only discussed implementation issues related to the Atom response specific to FedEO Links to Metadata If no {sru:recordschema} parameter is provided in a request, then the Atom responses contain entries with Atom links to the actual metadata records as shown below. Table 8 shows the mapping between the media types in the Atom links and the type of metadata they refer to. The following two types of Atom links are used to link to metadata records: alternate Relation Description Links to another representation of the entry's information. This is normally another metadata representation (EOP O&M, ISO, Dublin Core), but it can also be KML, CSV or Metalink. Page 33/116

34 via Links to the source of the entry (or feed) information. While this can be the same as alternate it implies a notion of "derived from" another information which is different than just pointing to the metadata record. Table 7: Values for relation Example 7: Atom links pointing to dataset metadata. <link href=" V5%3AG NSIDC_ECS&recordSchema=dc" rel="alternate" type="application/xml"/> <link href=" 2V5%3AG NSIDC_ECS&recordSchema=iso" rel="alternate" type="application/vnd.iso xml"/> <link href=" =EOP%3AMDA-GSI%3ARSAT2_NRT&uid=urn%3Aogc%3Adef%3AEOP%3AMDA-GSI%3ARSAT2_NRT%3A%3A%3A%3A%3Aurn%3Ao gc%3adef%3aeop%3amda-gsi%3arsat2_nrt%3apass%3a210672%3a3%3a0&recordschema=om" rel="alternate" type="application/gml+xml"/> Metadata embedded as foreign markup If the {sru:recordschema} parameter is provided in a request, then the Atom responses contain entries with the dataset series or dataset metadata embedded as foreign markup. Table 8 shows sru:recordschema values to be used to obtain various kinds of metadata. {sru:recordschema} Media type Comments (default) om application/gml+xml EOP O&M version 1.0 as defined in [AD.6] om11 application/gml+xml EOP O&M version 1.1 iso application/vnd.iso xml ISO dc application/xml Dublin core. Schema available at server-choice Any of the above [RD.11] Table 8: Record Schemas and Atom link media type Note that both EOP O&M version 1.0 and 1.1 use the GML media type. This is expected to be changed in the future once OGC (Addition of a profile parameter to GML MIME type is approved. Page 34/116

35 EOP O&M Metadata example The EOP O&M metadata embedded in the Atom response may have a different root element depending on the type of instrument the metadata applies to. The metadata embedded should be valid with respect to the EOP.XSD, OPT.XSD, SAR.XSD etc. schemas and can thus appear as an eop:earthobservation element, opt:earthobservation element or sar:earthobservation element respectively. Figure 6: EOP O&M Metadata Model (source: [RD.1]). Example 8: Request EOP O&M metadata Formatted for readability: httpaccept=application/atom+xml & parentidentifier = EOP:MDA-GSI:RSAT2_NRT & startdate = T00:00:00Z & enddate = T00:00:00Z & recordschema = om URL-encoded: tidentifier=eop:mda-gsi:rsat2_nrt&startdate= t00:00:00z&enddate= t00:00:00z&recordschema=om This request generates the following response: <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:media=" xmlns:os=" Page 35/116

36 xmlns:sru=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:wrs=" <os:totalresults>100369</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="urn%3aogc%3adef%3aeop%3amda-gsi%3arsat2_nrt" eo:parentidentifier="urn:ogc:def:eop:mda-gsi:rsat2_nrt" role="request" sru:recordschema="om" startindex="1" time:end=" t00:00:00z" time:start=" t00:00:00z"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - Search Response</title> <updated> t14:08:24z</updated> <link href=" Identifier=EOP:MDA-GSI:RSAT2_NRT&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om" rel="self" type="application/atom+xml"/> <link href=" Identifier=EOP:MDA-GSI:RSAT2_NRT&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=EOP:MDA-GSI:RSAT2_NRT&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=EOP:MDA-GSI:RSAT2_NRT&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&startRecord=100361" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> %3Aogc%3Adef%3AEOP%3AMDA-GSI%3ARSAT2_NRT&uid=urn%3Aogc%3Adef%3AEOP%3AMDA- GSI%3ARSAT2_NRT%3APASS%3A210672%3A3%3A0&recordSchema=om</id> <link href=" ject=urn%3aogc%3adef%3aeop%3amda-gsi%3arsat2_nrt&uid=urn%3aogc%3adef%3aeop%3amda- GSI%3ARSAT2_NRT%3APASS%3A210672%3A3%3A0&recordSchema=om" rel="alternate" title="url for retrieving full details of the product: urn:ogc:def:eop:mda-gsi:rsat2_nrt:pass:210672:3:0" type="application/atom+xml"/> <published> t01:29:54z</published> <title>urn:ogc:def:eop:mda-gsi:rsat2_nrt:pass:210672:3:0</title> <updated> t14:08:24z</updated> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <sar:earthobservation xmlns:sar=" xmlns:gml=" xmlns:atm=" xmlns:eop=" xmlns:gmlov=" xmlns:om=" xmlns:opt=" xmlns:ows=" xmlns:swe=" xmlns:xlink=" xmlns:xsi=" gml:id="idn10024" xsi:schemalocation=" <om:phenomenontime> <gml:timeperiod gml:id="tpn10024"> <gml:beginposition> t00:09:01.801</gml:beginposition> <gml:endposition> t00:09:10.125</gml:endposition> </gml:timeperiod> </om:phenomenontime> <om:resulttime> <gml:timeinstant gml:id="tin10024"> <gml:timeposition> t11:02:47.999</gml:timeposition> </gml:timeinstant> </om:resulttime> <om:procedure> <eop:earthobservationequipment gml:id="eoen10024"> <eop:platform> Page 36/116

37 <eop:platform> <eop:shortname>noname</eop:shortname> <eop:serialidentifier>radarsat-2</eop:serialidentifier> <eop:orbittype>leo</eop:orbittype> </eop:platform> </eop:platform> <eop:instrument> <eop:instrument> <eop:shortname>sar</eop:shortname> </eop:instrument> </eop:instrument> <eop:sensor> <eop:sensor> <eop:sensortype>radar</eop:sensortype> <eop:operationalmode codespace="urn:eop:phr:sensormode">multi-look Fine</eop:operationalMode> <eop:resolution uom="m">9.0</eop:resolution> <eop:swathidentifier>mf22w</eop:swathidentifier> </eop:sensor> </eop:sensor> <eop:acquisitionparameters> <sar:acquisition> <eop:orbitnumber>24173</eop:orbitnumber> <eop:lastorbitnumber>24173</eop:lastorbitnumber> <eop:orbitdirection>ascending</eop:orbitdirection> <sar:polarisationmode>s</sar:polarisationmode> <sar:polarisationchannels>hh</sar:polarisationchannels> <sar:antennalookdirection>right</sar:antennalookdirection> <sar:minimumincidenceangle uom="deg"> </sar:minimumincidenceangle> <sar:maximumincidenceangle uom="deg"> </sar:maximumincidenceangle> </sar:acquisition> </eop:acquisitionparameters> </eop:earthobservationequipment> </om:procedure> <om:observedproperty xlink:href="#phenom1"/> <om:featureofinterest> <eop:footprint gml:id="fpn10024"> <eop:multiextentof> <gml:multisurface gml:id="mulsfn10026" srsname="epsg:4326"> <gml:surfacemembers> <Polygon xmlns=" gml:id="pon100f6" srsname="urn:x-ogc:def:crs:epsg:6.7:4326"> <exterior> <LinearRing> <pos> </pos> <pos> </pos> <pos> </pos> <pos> </pos> <pos> </pos> </LinearRing> </exterior> </Polygon> </gml:surfacemembers> </gml:multisurface> </eop:multiextentof> <eop:centerof> <Point xmlns=" gml:id="pn10059" srsname="urn:x-ogc:def:crs:epsg:6.7:4326"> <coordinates> </coordinates> </Point> </eop:centerof> </eop:footprint> </om:featureofinterest> <om:result> <eop:earthobservationresult gml:id="eorn10024"> <eop:browse> <eop:browseinformation> <eop:type>thumbnail</eop:type> Page 37/116

38 <eop:subtype>thumbnail</eop:subtype> <eop:referencesystemidentifier codespace="epsg">urn:ogc:def:crs:epsg:6:3:4326</eop:referencesystemidentifier> <eop:filename> <ows:servicereference xlink:href=" ail.jpg"> <ows:requestmessage/> </ows:servicereference> </eop:filename> </eop:browseinformation> </eop:browse> <eop:browse> <eop:browseinformation> <eop:type>quicklook</eop:type> <eop:subtype>quicklook</eop:subtype> <eop:referencesystemidentifier codespace="epsg">urn:ogc:def:crs:epsg:6:3:4326</eop:referencesystemidentifier> <eop:filename> <ows:servicereference xlink:href=" <ows:requestmessage/> </ows:servicereference> </eop:filename> </eop:browseinformation> </eop:browse> <eop:parameter> <eop:parameterinformation> <eop:unitofmeasure uom="c"/> <eop:phenomenon> <swe:phenomenon xmlns:ns1=" ns1:id="phenom1"> <name xmlns=" </swe:phenomenon> </eop:phenomenon> </eop:parameterinformation> </eop:parameter> </eop:earthobservationresult> </om:result> <eop:metadataproperty> <eop:earthobservationmetadata> <eop:identifier>urn:ogc:def:eop:mda-gsi:rsat2_nrt:pass:210672:3:0</eop:identifier> <eop:parentidentifier>urn:ogc:def:eop:mda-gsi:rsat2_nrt</eop:parentidentifier> <eop:acquisitiontype>nominal</eop:acquisitiontype> <eop:producttype>raw</eop:producttype> <eop:status>archived</eop:status> <eop:downlinkedto> <eop:downlinkinformation> <eop:acquisitionstation codespace="urn:eop:phr:stationcode">pass</eop:acquisitionstation> </eop:downlinkinformation> </eop:downlinkedto> <eop:archivedin> <eop:archivinginformation> <eop:archivingcenter codespace="urn:eop:phr:stationcode">no</eop:archivingcenter> <eop:archivingdate> t01:29:54.000</eop:archivingdate> <eop:archivingidentifier codespace="urn:eop:phr:stationcode">213106</eop:archivingidentifier> </eop:archivinginformation> </eop:archivedin> <eop:imagequalitydegradationquotationmode>automatic</eop:imagequalitydegradationquota tionmode> <eop:processing> <eop:processinginformation/> </eop:processing> </eop:earthobservationmetadata> </eop:metadataproperty> </sar:earthobservation> Page 38/116

39 <georss:where xmlns:gml=" <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <media:group> <media:content medium="image" type="image/jpeg" url=" "> <media:category scheme=" </media:content> <media:content medium="image" type="image/jpeg" url=" <media:category scheme=" </media:content> </media:group> </entry>... </feed> Note that the same request with recordschema=om11 will return EOP O&M Version 1.1 metadata instead ISO Metadata example Some dataset series return ISO dataset series metadata (e.g. EOP:ESA:FEDEO:COLLECTIONS) or ISO dataset metadata (e.g. CWIC). The way to request it is similar and shown below. Example 9: Request ISO metadata Formatted for readability: httpaccept = application/atom+xml & parentidentifier = MYD10A2V5 & recordschema = iso & startrecord = 1 & maximumrecords = 10 URL-encoded: tidentifier=myd10a2v5&recordschema=iso&startrecord=1&maximumrecords=10 Note that FedEO is not able to return embedded ISO metadata for all dataset series. It may return an Atom response without the ISO metadata embedded in some cases, e.g. the same request as above with VITO replaced by ASAR will return as set of entries some of which will not contain embedded ISO metadata as the G-POD and VA4 subcatalogues are currently not able to return ISO metadata. Page 39/116

40 The above request generates the following response: <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:dc=" xmlns:eo=" xmlns:gco=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gmd=" xmlns:gmi=" xmlns:gml=" xmlns:os=" xmlns:ows=" xmlns:sru=" xmlns:time=" <os:totalresults>162665</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="myd10a2v5" role="request" sru:recordschema="iso" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - EO Product Search Response</title> <updated> t14:25:25z</updated> <link href=" Identifier=MYD10A2V5&recordSchema=iso&startRecord=1&maximumRecords=10" rel="self" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=162661" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> 10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS&recordSchema=iso</id> <link href=" ject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs&recordschema=iso" rel="alternate" title="url for retrieving full details of the product: MYD10A2V5:G NSIDC_ECS" type="application/atom+xml"/> <published> t00:00:00z</published> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <title>myd10a2v5:g nsidc_ecs</title> <updated> t14:25:25z</updated> <georss:where> <gml:envelope> <gml:lowercorner> e-4</gml:lowercorner> <gml:uppercorner>5.0e </gml:upperCorner> </gml:envelope> </georss:where> <gmi:mi_metadata> <gmd:fileidentifier> <gco:characterstring>myd10a2v5:g nsidc_ecs</gco:characterstring> </gmd:fileidentifier> <gmd:language> <gco:characterstring>eng</gco:characterstring> </gmd:language> <gmd:characterset> <gmd:md_charactersetcode codelist="./resources/codelist.xml#md_charactersetcode" codelistvalue="utf8">utf8</gmd:md_charactersetcode> Page 40/116

41 </gmd:characterset> <gmd:hierarchylevel> <gmd:md_scopecode codelist=" codelistvalue="dataset">dataset</gmd:md_scopecode> </gmd:hierarchylevel> <!--This is the CWIC point of contact.--> <gmd:contact>... </gmd:contact> <gmd:datestamp> <gco:date> </gco:date> </gmd:datestamp> <gmd:metadatastandardname> <gco:characterstring>geographic information - Metadata - Part 2: Extensions for imagery and gridded data</gco:characterstring> </gmd:metadatastandardname> <gmd:metadatastandardversion> <gco:characterstring>iso :2009(E)</gco:CharacterString> </gmd:metadatastandardversion> <!--This is the GCMD/IDN DIF Entry_ID for the dataset--> <gmd:dataseturi> <gco:characterstring>myd10a2v5</gco:characterstring> </gmd:dataseturi> <gmd:identificationinfo> <gmd:md_dataidentification> <gmd:citation> <gmd:ci_citation> <gmd:title> <gco:characterstring>sc:myd10a2.005: </gco:characterstring> </gmd:title> <gmd:date> <gmd:ci_date> <gmd:date> <gco:datetime> t16:15:56z</gco:datetime> </gmd:date> <gmd:datetype> <gmd:ci_datetypecode codelist="./resources/codelist.xml#ci_datetypecode" codelistvalue="revision">revision</gmd:ci_datetypecode> </gmd:datetype> </gmd:ci_date> </gmd:date> </gmd:ci_citation> </gmd:citation> <gmd:abstract> <gco:characterstring>data granule returned from NASA's Earth Observing System Clearinghouse (ECHO)</gco:CharacterString> </gmd:abstract> <!-- This is the point of contact for Author/Contributor. --> <gmd:pointofcontact>... </gmd:pointofcontact> <!-- This is the point of contact for Distributor/Publisher. --> <gmd:pointofcontact>... </gmd:pointofcontact> <!-- This is the point of contact for Originator/Creator. --> <gmd:pointofcontact>... </gmd:pointofcontact> <gmd:graphicoverview> <gmd:md_browsegraphic> <gmd:filename> <gco:characterstring>ftp://n5eil01u.ecs.nsidc.org/dp0/brws/browse.001/ /BROWSE.MYD10A2.A h18v jpg</gco:CharacterString> </gmd:filename> </gmd:md_browsegraphic> Page 41/116

42 </gmd:graphicoverview> <gmd:resourceformat> <gmd:md_format> <gmd:name> <gco:characterstring>application/x-hdfeos</gco:characterstring> </gmd:name> <gmd:version> <gco:characterstring/> </gmd:version> </gmd:md_format> </gmd:resourceformat> <gmd:language> <gco:characterstring>eng</gco:characterstring> </gmd:language> <gmd:characterset> <gmd:md_charactersetcode codelist="./resources/codelist.xml#md_charactersetcode" codelistvalue="utf8">utf8</gmd:md_charactersetcode> </gmd:characterset> <gmd:topiccategory> <gmd:md_topiccategorycode>geoscientificinformation</gmd:md_topiccategorycode> </gmd:topiccategory> <gmd:extent>... </gmd:extent> </gmd:md_dataidentification> </gmd:identificationinfo> <gmd:distributioninfo>... </gmd:distributioninfo> <gmd:dataqualityinfo>... </gmd:dataqualityinfo> <gmi:acquisitioninformation>... </gmi:acquisitioninformation> </gmi:mi_metadata> </entry>... </feed> Note 3 Dataset series served through the ISO Connector (See section 5.6) currently do not allow including ISO metadata records inside the Atom response for efficiency reasons as this would require the connector to make 1+n individual requests to be backend catalogue with n being the maxrecords parameter in the request Dublin Core Metadata example Some dataset series return Dublin Core dataset metadata (e.g. CWIC). Example 10: Request DC metadata Formatted for readability: httpaccept = application/atom+xml & parentidentifier = MYD10A2V5 & recordschema = dc Page 42/116

43 & startrecord = 1 & maximumrecords = 10 URL-encoded: tidentifier=myd10a2v5&recordschema=dc&startrecord=1&maximumrecords=10 This request generates the following response: <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:csw=" xmlns:dc=" xmlns:dct=" xmlns:eo=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gml=" xmlns:os=" xmlns:ows=" xmlns:sru=" xmlns:time=" <os:totalresults>162665</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="myd10a2v5" role="request" sru:recordschema="dc" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - EO Product Search Response</title> <updated> t14:37:59z</updated> <link href=" Identifier=MYD10A2V5&recordSchema=dc&startRecord=1&maximumRecords=10" rel="self" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=162661" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> 10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS&recordSchema=dc</id> <link href=" ject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs&recordschema=dc" rel="alternate" title="url for retrieving full details of the product: MYD10A2V5:G NSIDC_ECS" type="application/atom+xml"/> <published> t00:00:00z</published> <title>myd10a2v5:g nsidc_ecs</title> <updated> t14:37:59z</updated> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <georss:where> <gml:envelope> <gml:lowercorner>-5.0e </gml:lowercorner> <gml:uppercorner> E-4</gml:upperCorner> </gml:envelope> </georss:where> Page 43/116

44 <srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema" xmlns:xsi=" xsi:schemalocation="info:srw/schema/1/dcschema <dc:title>sc:myd10a2.005: </dc:title> <dc:creator>metadata Creator: National Snow and Ice Data Center</dc:creator> <dc:subject>myd10a2v5</dc:subject> <dc:description>data granule returned from NASA's Earth Observing System Clearinghouse (ECHO)</dc:description> <dc:publisher>distributor: NSIDC USER SERVICES; Phone: +1 (303) ; Fax: +1 (303) ; nsidc at nsidc.org</dc:publisher> <dc:contributor>point of Contact: VINCE V. SALOMONSON; Role: INVESTIGATOR; Phone: ; vincent.salomonson at utah.edu</dc:contributor> <dc:date> t16:15:56z</dc:date> <dc:type>downloadabledata</dc:type> <dc:format>na</dc:format> <dc:identifier>myd10a2v5:g nsidc_ecs</dc:identifier> <dc:source>na</dc:source> <dc:language>en</dc:language> <dc:relation>na</dc:relation> <dc:coverage>na</dc:coverage> <dc:rights>na</dc:rights> </srw_dc:dc> </entry>... </feed> Thumbnail, Browse and Mask information While the OpenSearch specification OGC provides a mechanism to return a quicklook image as atom:link with rel= icon, it does currently not provide a way to distinguish between thumbnail image, browser image, cloud mask or snow mask. In FedEO, we use the Media RSS Specification [AD.15] inside Atom and RSS feeds. Example 11: Inclusion of Quicklook information <media:content url=" PASS_RS2_210671_3_32488_1_thumbnail.jpg" type="image/jpeg" medium="image"> <media:category scheme=" </media:content> Example 12: Inclusion of Cloud mask information <media:content url=" =CLD&CP=N&SD=T&FT=BMP&CM=75" type="image/jpeg" medium="image"> <media:category scheme=" <media:title type="plain">cloud mask</media:title> </media:content> The scheme parameter reflects the thesaurus/codelist covering the various possibilities, e.g. the values allowed in the EOP O&M codelist for browse/browseinformation/type (THUMBNAIL, QUICKLOOK, ALBUM) and mask/maskinformation/type (SNOW, CLOUD, QUALITY). Page 44/116

45 Exceptions The FedEO OpenSearch implementation returns exceptions as defined in section of the OGC specification [AD.2], i.e. using HTTP exception codes. In addition, it returns a standard ows:exceptionreport element as defined in [AD.13] (chapter 8). An exception thus has 4 elements: HTTP exception code 4XX or 5XX as per OGC [AD.2]. ows:exception exceptioncode: as per table 28 of [AD.13], ows:exception exceptionlocator: as per [AD.13], ows:exceptiontext with a human readable message as per [AD.13]. Example 13: Search response in case of exceptions HTTP/ Bad Request Content-Type: application/xml <?xml version="1.0" encoding="utf-8"?> <ows:exceptionreport xmlns:ows=" xmlns:xsi=" xsi:schemalocation=" version="1.0.0" xml:lang="en"> <ows:exception exceptioncode="invalidparametervalue" locator="httpaccept"> <ows:exceptiontext>mime type {application/rdf+xml} is not supported for dataset series {urn:ogc:def:eop:mda-gsi:rsat2_nrt}.</ows:exceptiontext> </ows:exception> </ows:exceptionreport> The following table lists the possible exceptions. HTTP exception Code OWS exceptioncode OWS ExceptionText 500 NoApplicableCode Internal Server Error. 500 NoApplicableCode {Error message received from backend catalogue} 400 InvalidParameterValue Parameter {PARAM_NAME} has an invalid value. 400 InvalidParameterValue Parameter {PARAM_NAME} should be a number. 400 InvalidParameterValue Parameter {PARAM_NAME} should be an integer. 400 InvalidParameterValue Missing parameter {PARAM_NAME}. 400 InvalidParameterValue Parameter {PARAM_NAME} should be a number and between [UPPER_BOUND,LOWER_BOUND]. 400 InvalidParameterValue Parameter {PARAM_NAME} should be a range. 400 InvalidParameterValue Parameter {PARAM_NAME} should have upper bound value. Page 45/116

46 400 InvalidParameterValue Could not find dataset series {IDENTIFIER_VALUE} in the system configuration. 400 InvalidParameterValue MIME type {MIME_TYPE} is not supported for dataset series {IDENTIFIER_VALUE}. Table 9: List of exception codes Page 46/116

47 4 FEDEO CLIENT PARTNER IMPLEMENTATION OUTLINE The dataset series identifier (i.e. {eo:parentidentifier} or {dc:subject}) is a mandatory element in a FedEO Clearinghouse search request for dataset metadata. Clients can retrieve the eo:parentidentifier from either a Dataset Series search response or the Explain document of FedEO. 4.1 Client starts from FedEO Dataset Series Catalogue Data providers of FedEO have registered the metadata of their dataset series into one of the FedEO Dataset Series Catalogues. The client can interact with these catalogues to retrieve the eo:parentidentifier of a dataset series or the dataset series-specific OSDD for building a correct dataset search request. FedEO provides a number of separate dataset series catalogues which can be searched simultaneously or each individually (See Figure 2 in section 3.3.1). The table below lists the available dataset series catalogues which each have their own {eo:parentidentifier} allowing to identify them in dataset series search requests. EOP:ESA:FEDEO Identifier Describes Content Top-level dataset series catalogue comprising all individual dataset series catalogues. Heterogenous EOP:ESA:FEDEO:COLLECTIONS EO-DAIL and M2CS dataset series. ISO metadata records. EOP:ESA:REFERENCEDATA CWIC and GSCDA dataset series. ISO metadata records. EOP:ESA:EO-VIRTUAL-ARCHIVE4 ESA Virtual Archive RDF metadata records. EOP:ESA:GPOD-EO ESA GPOD RDF metadata records. Table 10: FedEO Dataset Series Catalogues The dataset series catalogues can be searched using a request using the search parameters published in the OSDD URL template for Atom with rel= collection as described in section A simple request is shown below. As no eo:parentidentifier is given in the request, the top-level dataset series catalogue EOP:ESA:FEDEO is searched (using a distributed search). Example 14: Simple dataset series search request Formatted for readability: httpaccept = application/atom+xml & startrecord = 1 & maximumrecords = 10 Page 47/116

48 & query = vegetation URL-encoded: Record=1&maximumRecords=10&query=vegetation The screen dump below shows a part of the search results as presented by Firefox. Note that results from EOP:ESA:FEDEO:COLLECTIONS have a different presentation content than the results from G-POD or VA4 which return Search feeds. Figure 7: FedEO Collection Search Results in Firefox The results returned by FedEO are typically heterogeneous as not all subcatalogues return the same metadata for the dataset series. The extract below shows a fragment of the response for the above request. It contains an entry for which ISO metadata is available and one for which only RDF metadata is available (from G-POD). For each dataset series an atom:link to a metadata record is included as well as the URL to be used to discover the OSDD for the corresponding dataset search. When clients use this OSDD for dataset search, they don t need to know the {eo:parentidentifier} to be used in the search as it will be pre-filled in the URL template for the dataset search. Page 48/116

49 Example 15: Extract of dataset series search result <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:dc=" xmlns:eo=" xmlns:gco=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gmd=" xmlns:gml=" xmlns:os=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:time=" <os:totalresults>22</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>30</os:itemsperpage> <os:query count="10" dc:subject="urn:ogc:def:eop:esa:referencedata" role="request" searchterms="vegetation" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - Search Response</title> <updated> t14:47:38z</updated> <link href=" ecord=1&maximumrecords=10&query=vegetation" rel="self" type="application/atom+xml"/> <link href=" mrecords=10&query=vegetation&startrecord=1" rel="first" type="application/atom+xml"/> <link href=" mrecords=10&query=vegetation&startrecord=11" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/>... <entry> <id> <title>terra MODIS 16-Day L3 Global 1km Vegetation Indices</title> <published> t08:21:38.788z</published> <updated> t18:21:04.944z</updated> <dc:identifier>mod13a2</dc:identifier> <dc:date> t00:00:00.000z/ t23:59:59.000z</dc:date> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link href=" rel="alternate" title="atom feed" type="application/atom+xml"> </link> <link href=" rel="search" title="search the MOD13A2" type="application/opensearchdescription+xml"> </link> <link href=" rel="via" title="rdf metadata entry" type="application/rdf+xml"> </link> <content type="html">... </content> </entry> <entry> <id> <title>envisat MERIS Land vegetation index parameters data (MER_LVI_AX)</title> <published> t15:50:40.924z</published> <updated> t16:58:45.076z</updated> <dc:identifier>mer_lvi_ax</dc:identifier> <dc:date>/</dc:date> Page 49/116

50 <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link href=" rel="alternate" title="atom feed" type="application/atom+xml"> </link> <link href=" rel="search" title="search the MER_LVI_AX" type="application/opensearchdescription+xml"> </link> <link href=" rel="via" title="rdf metadata entry" type="application/rdf+xml"> </link> <content type="html">... </content> </entry>... </feed> The atom:link with rel= search included in the response provides the URL of the dataset seriesspecific OSDD as was explained in section The <dc:identifier> element in the response provides the {eo:parentidentifier} that can be used for subsequent dataset searches. The link to the dataset series-specific OSDD is not present in the response if a search for datasets is not supported by the FedEO Clearinghouse. This parentidentifier also corresponds to the gmd:fileidentifier in the ISO metadata record for this dataset series as shown below. <gmd:md_metadata xmlns:gmd=" xmlns:gco=" xmlns:common=" xmlns:xlink=" xmlns:srv=" xmlns:gml=" xmlns:gsr=" xmlns:fo=" xmlns:gss=" xmlns:gts=" xmlns:gmx=" <gmd:fileidentifier> <gco:characterstring>urn:ogc:def:eop:esa:esa.eecf.eos_mod_xs</gco:characterstring> </gmd:fileidentifier>... </gmd:md_metadata> Note 4 Dataset series search responses from all dataset series catalogues contain the URL of the OSDD which allows for searching datasets inside the dataset series. This atom:link as the rel attribute set to search. In some cases (e.g. G-POD and VA4), this OSDD is not the OSDD published by FedEO, but a local OSDD. This is because FedEO does not transform Atom responses from catalogues natively responding with Atom format but returns their responses unchanged. This constraint may be removed in future versions of FedEO. Page 50/116

51 4.2 Client starts from FedEO Clearinghouse Capabilities In this case, clients use metadata about the search endpoint (a.k.a. Capabilities in OGC terminology). In the context of FedEO, the capabilities correspond to the Explain document or an OSDD annotated with Parameter extension information. Clients can discover the list of dataset series identifiers in the Explain document (See section 3.2). For instance EOP:DLR:EOWEB:TSX-1.SAR.L1b-ScanSAR. To search inside a particular dataset series, the client should set the {dc:subject} or {eo:parentidentifier} parameter which is used in the <Url> template in the OSDD to that specific dataset series identifier. Example 16: Simple dataset search request Formatted for readability: httpaccept = application/atom+xml & parentidentifier = EOP:DLR:EOWEB:TSX-1.SAR.L1b-ScanSAR & startrecord = 1 & maximumrecords = 10 URL-encoded: parentidentifier=eop%3adlr%3aeoweb%3atsx-1.sar.l1b-scansar& startrecord=1&maximumrecords=10 All dataset series in FedEO are required to support Atom as response type. A client can request responses in a particular media type using the httpaccept parameter. The following is an overview of the media types and record schemas supported by the various dataset series: Backend Catalogues MIME type url@type or httpaccept Record schema {sru:recordschema} Comments ASF Connector application/atom+xml application/rss+xml application/sru+xml application/atom+xml application/rss+xml om, om11 EOP O&M Version 1.0 or 1.1 embedded as foreign markup. - (Default) Atom:link pointing to EOP O&M metadata. OGC Connector application/atom+xml om, om11 EOP O&M Version 1.0 or 1.1 embedded as foreign markup. Page 51/116

52 Backend Catalogues MIME type or httpaccept Record schema {sru:recordschema} Comments application/rss+xml application/sru+xml application/atom+xml application/rss+xml - (default) Atom:link pointing to EOP O&M metadata. G-POD Connector application/rdf+xml text/plain N/A Atom:link pointing to RDF metadata. application/xhtml+xml application/vnd.googleearth.kml+xml Supersite VA4 Connector application/rdf+xml text/html application/vnd.googleearth.kml+xml N/A Atom:link pointing to RDF metadata. application/atom+xml text/plain text/tab-separated-values CWIC Connector application/atom+xml application/rss+xml - (default) Atom:link pointing to ISO and DC metadata. application/atom+xml application/rss+xml iso ISO metadata embedded as foreign markup. application/atom+xml application/rss+xml dc Dublin Core metadata embedded as foreign markup. ISO Connector application/atom+xml iso ISO metadata embedded as foreign markup (Future work). application/atom+xml - (Default) Atom:link pointing to ISO metadata. Page 52/116

53 5 CATALOGUE CONNECTORS This chapter provides information which is specific for the dataset series served via a particular backend or connector. As explained in section 3.2 and visible in, the list of dataset series identifiers can be found in the Explain document. The list contains comments indicating to which Connector the dataset series belong. 5.1 ASF Connector This connector provides access to the data repository of the Alaska Satellite Facility ( which provides free access to SAR data. The ASF Connector wraps the custom API ( and makes it available via the FedEO Clearinghouse Dataset series metadata ASF dataset series metadata is currently not available through FedEO Dataset metadata The dataset series identifier, i.e. {dc:subject} or {eo:parentidentifier} supported by the FedEO dataset search is ogc:def:eop:asf or EOP:ASF. All datasets are thus grouped in a single dataset series corresponding to the complete ASF catalogue Search Parameters The following OSDD lists the supported search parameters in the URL template section: It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:time=" xmlns:eo=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:param=" /spec/opensearch/extensions/parameters/1.0/" xmlns:dc=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url type="application/opensearchdescription+xml" rel="self" template=" <Url type="application/atom+xml" template=" entifier=eop:asf&subject=eop:asf&query={searchterms?}&maximumrecords={count?}&startd ate={time:start?}&enddate={time:end?}&bbox={geo:box?}&name={geo:name?}&lat={geo:lat? }&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&platformshortname={eo:platforms hortname?}&processinglevel={eo:processinglevel?}&frame={eo:frame?}&sensormode={eo:sensor Mode?}&polarisationMode={eo:polarisationMode?}&orbitDirection={eo:orbitDirection?}&orbit Page 53/116

54 Number={eo:orbitNumber?}&antennaLookDirection={eo:antennaLookDirection?}&recordSchema={sru:r ecordschema?}"/> <Url type="application/rss+xml" template=" entifier=eop:asf&subject=eop:asf&query={searchterms?}&maximumrecords={count?}&startd ate={time:start?}&enddate={time:end?}&bbox={geo:box?}&name={geo:name?}&lat={geo:lat? }&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&platformshortname={eo:platforms hortname?}&processinglevel={eo:processinglevel?}&frame={eo:frame?}&sensormode={eo:sensor Mode?}&polarisationMode={eo:polarisationMode?}&orbitDirection={eo:orbitDirection?}&orbit Number={eo:orbitNumber?}&antennaLookDirection={eo:antennaLookDirection?}&recordSchema={sru:r ecordschema?}"/> <param:parameter name="recordschema" value="sru:recordschema"> <param:option value="om" label="o&m"/> <param:option value="om11" label="o&m Version 1.1"/> </param:parameter> <param:parameter name="platformshortname" value="eo:platformshortname"> <param:option value="a3" label="a3"/> <param:option value="ai" label="ai"/> <param:option value="as" label="as"/> <param:option value="e1" label="e1"/> <param:option value="e2" label="e2"/> <param:option value="ers-1" label="ers-1"/> <param:option value="ers-2" label="ers-2"/> <param:option value="j1" label="j1"/> <param:option value="jers-1" label="jers-1"/> <param:option value="r1" label="r1"/> <param:option value="ua" label="ua"/> <param:option value="airmoss" label="airmoss"/> <param:option value="airsar" label="airsar"/> <param:option value="alos" label="alos"/> <param:option value="jers-1" label="jers-1"/> <param:option value="radarsat-1" label="radarsat-1"/> <param:option value="uavsar" label="uavsar"/> </param:parameter> <param:parameter name="processinglevel" value="eo:processinglevel"> <param:option value="l0" label="l0"/> <param:option value="l1" label="l1"/> <param:option value="l1.0" label="l1.0"/> <param:option value="l1.1" label="l1.1"/> <param:option value="l1.5" label="l1.5"/> <param:option value="browse" label="browse"/> <param:option value="kmz" label="kmz"/> <param:option value="projected" label="projected"/> <param:option value="pauli" label="pauli"/> <param:option value="projected_ml5x5" label="projected_ml5x5"/> <param:option value="stokes" label="stokes"/> <param:option value="amplitude" label="amplitude"/> <param:option value="complex" label="complex"/> <param:option value="dem_tiff" label="dem_tiff"/> <param:option value="projected_ml3x3" label="projected_ml3x3"/> <param:option value="metadata" label="metadata"/> <param:option value="amplitude_grd" label="amplitude_grd"/> <param:option value="interferometry" label="interferometry"/> <param:option value="nterferometry_grd" label="nterferometry_grd"/> <param:option value="3fp" label="3fp"/> <param:option value="ati" label="ati"/> <param:option value="xtiltif" label="xtiltif"/> <param:option value="ptif" label="ptif"/> <param:option value="ctif" label="ctif"/> <param:option value="pstokes" label="pstokes"/> <param:option value="dem" label="dem"/> <param:option value="cstokes" label="cstokes"/> <param:option value="jpg" label="jpg"/> <param:option value="lstokes" label="lstokes"/> </param:parameter>... </OpenSearchDescription> Page 54/116

55 The ASF connector is using the API document at [RD.19]. Its main limitation is that paging is not supported. This means that the OpenSearch parameter {startindex} is ignored. The table below does not list all search parameters available but draws attention to specific limitations and parameters proper to this Connector. Parameter name OpenSearch Parameters Reference to definition and comments Parameter value {eo:frame} [AD.3] Single values or a range with a lower and upper limit (e.g. [2580,2581] ) are allowed. Ranges with only a lower value or only an upper value (e.g. 2580] ) are not supported by the backend. {eo:antennalookdirection} [AD.3] Mapped to ASF lookdirection. See [RD.19]. {eo:orbitdirection} [AD.3] Mapped to ASF flightdirection. See [RD.19]. {eo:orbitnumber} [AD.3] Single values or a range with a lower and upper limit are allowed. Ranges with only a lower value or only an upper value are not supported by the backend. Mapped to ASF absoluteorbit. {eo:parentidentifier} [AD.3] Fixed value EOP:ASF which identifies ASF as a single dataset series. {eo:platformshortname} [AD.3] See OSDD for valid values. {eo:polarisationmode} [AD.3] Valid values depend on the {eo:platformshortname} as explained in [RD.19]. {eo:processinglevel} [AD.3] Valid values depend on the {eo:platformshortname} as explained in [RD.19]. {eo:sensormode} [AD.3] Mapped to ASF beammode. See [RD.19]. {geo:uid} Valid values should correspond to identifiers allowed in an ASF granule list. See [RD.19]. {searchterms} [AD.1] Coresponds to ASF collectionname as per [RD.19], e.g. HAITI. startrecord {startindex} [AD.1] Not supported by ASF. Table 11: Search Parameters (Datasets) Page 55/116

56 Response Formats Response media type Comments application/atom+xml application/rss+xml application/sru+xml application/rdf+xml Available. Available. Future work. Future work. Table 12: ASF Supported Media Types {sru:recordschema} Media type Comments - application/gml+xml application/text+csv application/vnd.googleearth.kml+xml application/metalink+xml Default. Returns a response with atom:links to different metadata formats including: EOP O&M format CSV format KML format Metalink format om application/gml+xml EOP O&M Version 1.0 embedded as foreign markup as defined in [AD.6]. om11 application/gml+xml EOP O&M Version 1.1 embedded as foreign markup as defined in [AD.7]. server-choice application/gml+xml [RD.11]. Same as om. Table 13: ASF Supported Record Schemas Examples The following is an example showing the use of a number of search parameters. Example 17: ASF dataset search request Formatted for readability: httpaccept = application/atom+xml & parentidentifier = EOP:ASF & box = 63.07, ,64.47, & platformshortname = A3 Page 56/116

57 & orbitdirection = DESCENDING & processinglevel = L1.0 & maximumrecords = 10 & frame = 2580 URL-encoded: tidentifier=eop:asf&box=63.07, ,64.47, &platformShortName=A3&orbitDirection=DESCENDING&processingLevel=L1.0&maxim umrecords=10&frame=2580 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:asf=" xmlns:dc=" xmlns:fn=" xmlns:geo=" xmlns:georss=" xmlns:gml=" xmlns:media=" xmlns:os=" xmlns:sru=" xmlns:time=" /opensearch/extensions/time/1.0/"> <os:totalresults>100</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="urn:ogc:def:eop:asf" role="request" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> er=eop:asf&box=63.07, ,64.47, &platformshortname=a3&orbitdirection=descendin G&processingLevel=L1.0&maximumRecords=10&frame=2580</id> <title>fedeo Clearinghouse - Search Response</title> <updated> t15:07:50z</updated> <link href=" Identifier=EOP:ASF&box=63.07, ,64.47, &platformShortName=A3&orbitDirection=D ESCENDING&processingLevel=L1.0&maximumRecords=10&frame=2580" rel="self" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> :ogc:def:eop:asf&uid=&startrecord=1</id> <title>alpsrp ALOS PALSAR sensor: High Resolution Observation Mode (single polarization)</title> <dc:date> t19:03:20z</dc:date> <updated> t00:00:00z</updated> <published> t00:00:00z</published> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <summary type="html"><![cdata[ <table>... </table>]]> Page 57/116

58 </summary> <link href=" length=" " rel="enclosure" title="download" type="application/x-binary"/> <link href=" ject=urn:ogc:def:eop:asf&uid=alpsrp &startrecord=1" rel="alternate" title="atom format" type="application/atom+xml"/> <link href=" ect=urn:ogc:def:eop:asf&uid=alpsrp &startrecord=1&recordschema=om" rel="alternate" type="application/gml+xml"/> <link href=" ect=urn:ogc:def:eop:asf&uid=alpsrp &startrecord=1&recordschema=om11" hreflang="en" rel="alternate" type="application/gml+xml"/> <link href=" p;processinglevel=l1.0&frame=2580&flightdirection=descending&maxresults=10&granule_l ist=alpsrp " rel="alternate" title="csv format" type="application/text+csv"/> <link href=" p;processinglevel=l1.0&frame=2580&flightdirection=descending&maxresults=10&granule_l ist=alpsrp " rel="alternate" title="kml format" type="application/vnd.googleearth.kml+xml"/> <link href=" A3&processingLevel=L1.0&frame=2580&flightDirection=DESCENDING&maxResults=10&gran ule_list=alpsrp " rel="alternate" title="metalink format" type="application/metalink+xml"/> </entry>... </feed> This response is visualised in Firefox as shown below. Page 58/116

59 Figure 8: ASF search result in Atom format shown in Firefox. Page 59/116

60 5.2 CWIC Connector Dataset series metadata The EOP:ESA:REFERENCEDATA parentidentifier represents a set of ISO dataset series metadata including the CWIC dataset series metadata. These metadata are served through the OGC [RD.21] ISO Connector. The dataset series identifiers to be used as {dc:subject} or {eo:parentidentifier} in the corresponding dataset search can be found in the <gmd:fileidentifier> element of the ISO records returned by the OGC ISO Connector (See section 5.6). They also correspond to the <dc:identifier> element of the corresponding dataset series entry returned by this Connector Dataset metadata The CWIC dataset series identifiers, i.e. {dc:subject} or {eo:parentidentifier} supported by the FedEO dataset search correspond to the dataset Entry IDs which can be found in the cwic:federationmetadata section of the CWIC capabilities as explained in [RD.13] or to the <dc:identifier> element in the dataset series search results Search Parameters The following OSDD lists the supported search parameters in the URL template section: It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:time=" xmlns:eo=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:param=" /spec/opensearch/extensions/parameters/1.0/" xmlns:dc=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url type="application/opensearchdescription+xml" rel="self" template=" <Url type="application/atom+xml" template=" entifier=boreas_afm2as94&subject=boreas_afm2as94&startrecord={startindex?}&maximumrecord s={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&name={geo:nam e?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&recordsche ma={sru:recordschema?}"/> <Url type="application/rss+xml" template=" ntifier=boreas_afm2as94&subject=boreas_afm2as94&startrecord={startindex?}&maximumrecords ={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&recordschem a={sru:recordschema?}"/> <Url type="application/sru+xml" template=" ntifier=boreas_afm2as94&subject=boreas_afm2as94&startrecord={startindex?}&maximumrecords ={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&name={geo:name Page 60/116

61 ?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={geo:uid?}&recordschem a={sru:recordschema?}"/> <param:parameter name="recordschema" value="sru:recordschema"> <param:option value="dc" label="dublin Core"/> <param:option value="iso" label="iso 19139"/> </param:parameter>... </OpenSearchDescription> The table below does not list all search parameters available but draws attention to specific limitations and parameters proper to this Connector. Parameter name OpenSearch Parameters Reference to definition and comments Parameter value {eo:parentidenti fier} [AD.3] CWIC dataset Entry ID, e.g. BOREAS_AFM2AS94. {geo:uid} [AD.2] Identifier of dataset (granule) as explained in section 7.5 of [RD.13]. Table 14: Search Parameters (Datasets) Response Formats Response media type Comments application/atom+xml application/rss+xml application/sru+xml application/rdf+xml Available. Available. Available. Future work. Table 15: CWIC Supported Media Types {sru:recordschema} Media type Comments - application/vnd.iso xml application/xml Default. Returns a response with atom:links to different metadata formats including: ISO format DC format iso application/vnd.iso xml ISO embedded as foreign markup. dc application/xml Dublin core embedded as foreign markup. Schema available at Page 61/116

62 server-choice application/vnd.iso xml [RD.11]. Same as iso. Table 16: CWIC Supported Record Schemas Examples The following examples show the alternative ways to obtain dataset metadata. Example 18: CWIC dataset search request (metadata link) Formatted for readability: httpaccept = application/atom+xml & parentidentifier = MYD10A2V5 & startrecord = 1 & maximumrecords = 10 URL-encoded: tidentifier=myd10a2v5&startrecord=1&maximumrecords=10 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:csw=" xmlns:dc=" xmlns:dct=" xmlns:eo=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gml=" xmlns:os=" xmlns:ows=" xmlns:sru=" xmlns:time=" <os:totalresults>162665</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="myd10a2v5" role="request" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - EO Product Search Response</title> <updated> t15:24:57z</updated> <link href=" Identifier=MYD10A2V5&startRecord=1&maximumRecords=10" rel="self" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&maximumRecords=10&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&maximumRecords=10&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&maximumRecords=10&startRecord=162661" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> Page 62/116

63 <entry> <id> 10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS</id> <link href=" ject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs" rel="alternate" title="url for retrieving full details of the product: MYD10A2V5:G NSIDC_ECS" type="application/atom+xml"/> <published> t00:00:00z</published> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <title>myd10a2v5:g nsidc_ecs</title> <updated> t15:24:57z</updated> <georss:where> <gml:envelope> <gml:lowercorner> e-4</gml:lowercorner> <gml:uppercorner>5.0e </gml:upperCorner> </gml:envelope> </georss:where> <link href=" D10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS&recordSchema=dc" rel="alternate" type="application/xml"/> <link href=" subject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs&recordschema=iso" rel="alternate" type="application/vnd.iso xml"/> </entry>... </feed> Example 19: CWIC dataset search request (ISO metadata) Formatted for readability: httpaccept=application/atom+xml & parentidentifier = MYD10A2V5 & recordschema = iso & startrecord = 1 & maximumrecords = 10 URL-encoded: tidentifier=myd10a2v5&recordschema=iso&startrecord=1&maximumrecords=10 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:dc=" xmlns:eo=" xmlns:gco=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gmd=" xmlns:gmi=" xmlns:gml=" xmlns:os=" xmlns:ows=" xmlns:sru=" xmlns:time=" <os:totalresults>162665</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> Page 63/116

64 <os:query count="10" dc:subject="myd10a2v5" role="request" sru:recordschema="iso" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - EO Product Search Response</title> <updated> t15:34:37z</updated> <link href=" Identifier=MYD10A2V5&recordSchema=iso&startRecord=1&maximumRecords=10" rel="self" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=iso&maximumRecords=10&startRecord=162661" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> 10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS&recordSchema=iso</id> <link href=" ject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs&recordschema=iso" rel="alternate" title="url for retrieving full details of the product: MYD10A2V5:G NSIDC_ECS" type="application/atom+xml"/> <published> t00:00:00z</published> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <title>myd10a2v5:g nsidc_ecs</title> <updated> t15:34:37z</updated> <georss:where> <gml:envelope> <gml:lowercorner> e-4</gml:lowercorner> <gml:uppercorner>5.0e </gml:upperCorner> </gml:envelope> </georss:where> <gmi:mi_metadata> <gmd:fileidentifier> <gco:characterstring>myd10a2v5:g nsidc_ecs</gco:characterstring> </gmd:fileidentifier> <gmd:language> <gco:characterstring>eng</gco:characterstring> </gmd:language> <gmd:characterset> <gmd:md_charactersetcode codelist="./resources/codelist.xml#md_charactersetcode" codelistvalue="utf8">utf8</gmd:md_charactersetcode> </gmd:characterset> <gmd:hierarchylevel> <gmd:md_scopecode codelist=" codelistvalue="dataset">dataset</gmd:md_scopecode> </gmd:hierarchylevel> <!--This is the CWIC point of contact.--> <gmd:contact> <gmd:ci_responsibleparty> <gmd:organisationname> <gco:characterstring>ceos WGISS Integrated Catalog (CWIC)</gco:CharacterString> </gmd:organisationname> <gmd:contactinfo> <gmd:ci_contact> Page 64/116

65 <gmd:address> <gmd:ci_address> <gmd:electronicmailaddress> </gmd:electronicmailaddress> </gmd:ci_address> </gmd:address> <gmd:onlineresource> <gmd:ci_onlineresource> <gmd:linkage> <gmd:url> </gmd:linkage> </gmd:ci_onlineresource> </gmd:onlineresource> </gmd:ci_contact> </gmd:contactinfo> <gmd:role> <gmd:ci_rolecode codelist=" codelistvalue="pointofcontact">cwic Contact</gmd:CI_RoleCode> </gmd:role> </gmd:ci_responsibleparty> </gmd:contact> <gmd:datestamp> <gco:date> </gco:date> </gmd:datestamp> <gmd:metadatastandardname> <gco:characterstring>geographic information - Metadata - Part 2: Extensions for imagery and gridded data</gco:characterstring> </gmd:metadatastandardname> <gmd:metadatastandardversion> <gco:characterstring>iso :2009(E)</gco:CharacterString> </gmd:metadatastandardversion> <!--This is the GCMD/IDN DIF Entry_ID for the dataset--> <gmd:dataseturi> <gco:characterstring>myd10a2v5</gco:characterstring> </gmd:dataseturi> <gmd:identificationinfo>... </gmd:identificationinfo> <gmd:distributioninfo>... </gmd:distributioninfo> <gmd:dataqualityinfo>... </gmd:dataqualityinfo> <gmi:acquisitioninformation>... </gmi:acquisitioninformation> </gmi:mi_metadata> </entry>... </feed> This response is visualised in Firefox as shown below. Page 65/116

66 Figure 9: CWIC search result in Atom format shown in Firefox. Example 20: CWIC dataset search request (DC metadata) Formatted for readability: httpaccept=application/atom+xml & parentidentifier = MYD10A2V5 & recordschema = dc & startrecord = 1 & maximumrecords = 10 URL-encoded: tidentifier=myd10a2v5&recordschema=dc&startrecord=1&maximumrecords=10 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:csw=" xmlns:dc=" xmlns:dct=" xmlns:eo=" xmlns:geo=" Page 66/116

67 /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:gml=" xmlns:os=" xmlns:ows=" xmlns:sru=" xmlns:time=" <os:totalresults>162665</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query count="10" dc:subject="myd10a2v5" role="request" sru:recordschema="dc" startindex="1"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - EO Product Search Response</title> <updated> t15:43:01z</updated> <link href=" Identifier=MYD10A2V5&recordSchema=dc&startRecord=1&maximumRecords=10" rel="self" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=11" rel="next" type="application/atom+xml"/> <link href=" Identifier=MYD10A2V5&recordSchema=dc&maximumRecords=10&startRecord=162661" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> 10A2V5&uid=MYD10A2V5%3AG NSIDC_ECS&recordSchema=dc</id> <link href=" ject=myd10a2v5&uid=myd10a2v5%3ag nsidc_ecs&recordschema=dc" rel="alternate" title="url for retrieving full details of the product: MYD10A2V5:G NSIDC_ECS" type="application/atom+xml"/> <published> t00:00:00z</published> <title>myd10a2v5:g nsidc_ecs</title> <updated> t15:43:01z</updated> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <georss:where> <gml:envelope> <gml:lowercorner>-5.0e </gml:lowercorner> <gml:uppercorner> E-4</gml:upperCorner> </gml:envelope> </georss:where> <srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema" xmlns:xsi=" xsi:schemalocation="info:srw/schema/1/dcschema <dc:title>sc:myd10a2.005: </dc:title> <dc:creator>metadata Creator: National Snow and Ice Data Center</dc:creator> <dc:subject>myd10a2v5</dc:subject> <dc:description>data granule returned from NASA's Earth Observing System Clearinghouse (ECHO)</dc:description> <dc:publisher>distributor: NSIDC USER SERVICES; Phone: +1 (303) ; Fax: +1 (303) ; nsidc at nsidc.org</dc:publisher> <dc:contributor>point of Contact: VINCE V. SALOMONSON; Role: INVESTIGATOR; Phone: ; vincent.salomonson at utah.edu</dc:contributor> <dc:date> t16:15:56z</dc:date> <dc:type>downloadabledata</dc:type> <dc:format>na</dc:format> <dc:identifier>myd10a2v5:g nsidc_ecs</dc:identifier> <dc:source>na</dc:source> <dc:language>en</dc:language> Page 67/116

68 <dc:relation>na</dc:relation> <dc:coverage>na</dc:coverage> <dc:rights>na</dc:rights> </srw_dc:dc> </entry>... </feed> Page 68/116

69 5.3 OGC Connector Dataset series metadata Dataset series metadata is currently only partly available through FedEO. It is accessible through the ISO Connector (See section 5.6.1). The missing metadata will be added in the future. The dataset series identifiers to be used as {dc:subject} or {eo:parentidentifier} in the corresponding dataset search can be found in the <gmd:fileidentifier> element of the ISO records returned by the ISO Connector (See section 5.6.1). They also correspond to the <dc:identifier> element of the corresponding entry returned by the ISO Connector Dataset metadata The dataset series identifiers, i.e. {dc:subject} or {eo:parentidentifier} supported by the FedEO dataset search are listed in the Explain document. They correspond to the parentidentifiers which can be found in the OGC capabilities as explained in OGC [RD.2]. Section 10.1 of OGC defines the convention for the parentidentifier as in "Definition identifier URNs in OGC namespace" [OGC r1] i.e. urn:ogc:def:objecttype:authority:version:code. where the registered namespace authority is ogc, the objecttype is EOP, the authority representing the Ground Segment i.e ESA, SPOT, EUM etc The version is optional. For convenience, FedEO accepts these long identifiers or their abbreviated version which starts with the object type, i.e. EOP Search Parameters The following OSDD lists the supported search parameters in the URL template section: It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:time=" xmlns:eo=" xmlns:sru=" /opensearch/extensions/sru/2.0/" xmlns:param=" /spec/opensearch/extensions/parameters/1.0/" xmlns:dc=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url type="application/opensearchdescription+xml" rel="self" template=" <Url type="application/atom+xml" template=" entifier=eop:vito:vgt_p&subject=eop:vito:vgt_p&query={searchterms?}&startrecord={startin dex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo: box?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={g eo:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&platfor mserialidentifier={eo:platformserialidentifier?}&instrument={eo:instrument?}&sensortype={eo: sensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&orb ittype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus?}&a Page 69/116

70 mp;acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={eo:or bitdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifier?} &cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquisitio nstation?}&imagequalitydegradation={eo:imagequalitydegradation?}&processorname={eo:processor Name?}&sensorMode={eo:sensorMode?}&archivingCenter={eo:archivingCenter?}&acquisitionSubT ype={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}&com pletiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle={eo: illuminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&polar isationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&antennalo okdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&max imumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&incid enceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <Url type="application/rss+xml" template=" ntifier=eop:vito:vgt_p&subject=eop:vito:vgt_p&query={searchterms?}&startrecord={startind ex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:b ox?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={ge o:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&platform SerialIdentifier={eo:platformSerialIdentifier?}&instrument={eo:instrument?}&sensorType={eo:s ensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&orbi ttype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus?}&am p;acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={eo:orb itdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifier?}& amp;cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquisition Station?}&imageQualityDegradation={eo:imageQualityDegradation?}&processorName={eo:processorN ame?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisitionsubty pe={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}&comp letiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle={eo:i lluminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&polari sationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&antennaloo kdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&maxi mumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&incide nceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <Url type="application/sru+xml" template=" ntifier=eop:vito:vgt_p&subject=eop:vito:vgt_p&query={searchterms?}&startrecord={startind ex?}&maximumrecords={count?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:b ox?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}&uid={ge o:uid?}&producttype={eo:producttype?}&platformshortname={eo:platformshortname?}&platform SerialIdentifier={eo:platformSerialIdentifier?}&instrument={eo:instrument?}&sensorType={eo:s ensortype?}&compositetype={eo:compositetype?}&processinglevel={eo:processinglevel?}&orbi ttype={eo:orbittype?}&resolution={eo:resolution?}&productionstatus={eo:productionstatus?}&am p;acquisitiontype={eo:acquisitiontype?}&orbitnumber={eo:orbitnumber?}&orbitdirection={eo:orb itdirection?}&track={eo:track?}&frame={eo:frame?}&swathidentifier={eo:swathidentifier?}& amp;cloudcover={eo:cloudcover?}&snowcover={eo:snowcover?}&acquisitionstation={eo:acquisition Station?}&imageQualityDegradation={eo:imageQualityDegradation?}&processorName={eo:processorN ame?}&sensormode={eo:sensormode?}&archivingcenter={eo:archivingcenter?}&acquisitionsubty pe={eo:acquisitionsubtype?}&starttimefromascendingnode={eo:starttimefromascendingnode?}&comp letiontimefromascendingnode={eo:completiontimefromascendingnode?}&illuminationazimuthangle={eo:i lluminationazimuthangle?}&illuminationelevationangle={eo:illuminationelevationangle?}&polari sationmode={eo:polarisationmode?}&polarisationchannels={eo:polarisationchannels?}&antennaloo kdirection={eo:antennalookdirection?}&minimumincidenceangle={eo:minimumincidenceangle?}&maxi mumincidenceangle={eo:maximumincidenceangle?}&dopplerfrequency={eo:dopplerfrequency?}&incide nceanglevariation={eo:incidenceanglevariation?}&recordschema={sru:recordschema?}"/> <param:parameter name="recordschema" value="{sru:recordschema}"> <param:option value="om" label="o&m"/> <param:option value="om11" label="o&m Version 1.1"/> </param:parameter> <param:parameter name="sensortype" value="{eo:sensortype}"> <param:option value="limb" label="limb Looking/Sounding Sensor"/> <param:option value="radar" label="radar Sensor"/> <param:option value="optical" label="optical Sensor"/> <param:option value="altimetric" label="altimetric Sensor"/> <param:option value="atmospheric" label="atmospheric Sensor"/> </param:parameter> <param:parameter name="orbittype" value="{eo:orbittype}"> <param:option value="leo" label="low Earth Orbit"/> <param:option value="geo" label="geosynchronous Earth Orbit"/> Page 70/116

71 </param:parameter> <param:parameter name="productionstatus" value="{eo:productionstatus}"> <param:option value="rejected" label="data acquisition has been rejected for whatever reason"/> <param:option value="potential" label="potential data acquisition"/> <param:option value="planned" label="data acquisition planned"/> <param:option value="failed" label="data acquisition failed"/> <param:option value="cancelled" label="data acquisition cancelled"/> <param:option value="acquired" label="data acquired"/> <param:option value="archived" label="data acquisition archived"/> </param:parameter> <param:parameter name="acquisitiontype" value="{eo:acquisitiontype}"> <param:option value="calibration" label="calibration"/> <param:option value="nominal" label="nominal"/> <param:option value="other" label="other"/> </param:parameter> <param:parameter name="orbitdirection" value="{eo:orbitdirection}"> <param:option value="ascending" label="ascending"/> <param:option value="descending" label="descending"/> </param:parameter> <param:parameter name="imagequalitydegradation" value="{eo:imagequalitydegradation}"> <param:option value="nominal" label="data acquisition passed a quality check with success"/> <param:option value="degraded" label="data acquisition passed a quality check and degradations were found"/> </param:parameter> <param:parameter name="polarisationmode" value="{eo:polarisationmode}"> <param:option value="s" label="single"/> <param:option value="d" label="dual"/> </param:parameter> <param:parameter name="polarisationchannels" value="{eo:polarisationchannels}"> <param:option value="hh" label="hh"/> <param:option value="vv" label="vv"/> <param:option value="hh,hv" label="hh,hv"/> <param:option value="vv,vh" label="vv,vh"/> </param:parameter> <param:parameter name="antennalookdirection" value="{eo:antennalookdirection}"> <param:option value="left" label="left"/> <param:option value="right" label="right"/> </param:parameter>... </OpenSearchDescription> Response Formats Response media type Comments application/atom+xml application/rss+xml application/sru+xml application/rdf+xml Available. Available. Available. Future work. Table 17: OGC Connector Supported Media Types Page 71/116

72 {sru:recordschema} Media type Comments - application/gml+xml Default. Returns a response with atom:links to different metadata formats including: EOP O&M format om application/gml+xml EOP O&M Version 1.0 embedded as foreign markup as defined in [AD.6]. om11 application/gml+xml EOP O&M Version 1.1 embedded as foreign markup as defined in [AD.7]. server-choice [RD.11]. Same as om. Table 18: OGC Connector Supported Record Schemas Examples The following is an example showing the use of a number of search parameters. Example 21: OGC dataset search request (Atom) Formatted for readability: httpaccept = application/atom+xml & parentidentifier = EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC & startdate = T00:00:00Z & enddate = T00:00:00Z & recordschema = om & orbitdirection = DESCENDING URL-encoded: tidentifier=eop:dlr:eoweb:geohazard.supersite.terrasar-x_ssc&startdate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&orbitDirection=DESCENDING An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" /opensearch/extensions/geo/1.0/" xmlns:georss=" xmlns:media=" xmlns:os=" xmlns:sru=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:wrs=" <os:totalresults>9</os:totalresults> <os:startindex>1</os:startindex> <os:itemsperpage>10</os:itemsperpage> Page 72/116

73 <os:query count="10" dc:subject="urn%3aeop%3adlr%3aeoweb%3ageohazard.supersite.terrasar-x_ssc" eo:orbitdirection="descending" eo:parentidentifier="urn:eop:dlr:eoweb:geohazard.supersite.terrasar- X_SSC" role="request" sru:recordschema="om" startindex="1" time:end=" t00:00:00z" time:start=" t00:00:00z"/> <author> <name>fedeo Clearinghouse</name> </author> <generator>fedeo Clearinghouse</generator> <id> <title>fedeo Clearinghouse - Search Response</title> <updated> t15:58:11z</updated> <link href=" Identifier=EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&orbitDirection=DESCENDING" rel="self" type="application/atom+xml"/> <link href=" Identifier=EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&orbitDirection=DESCENDING& startrecord=1" rel="first" type="application/atom+xml"/> <link href=" Identifier=EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&orbitDirection=DESCENDING& startrecord=1" rel="last" type="application/atom+xml"/> <link href=" rel="search" type="application/opensearchdescription+xml"/> <entry> <id> %3Aeop%3ADLR%3AEOWEB%3AGeohazard.Supersite.TerraSAR-X_SSC&uid=urn%3Aeop%3ADLR%3AEOWEB%3ATerraSAR -X_SSC%3A%2Fdims_nz_pl_dfd_XXXXB %2Fdims_op_pl_dfd_%2F%2FTerraSAR-X_SSC&recor dschema=om</id> <link href=" ject=urn%3aeop%3adlr%3aeoweb%3ageohazard.supersite.terrasar-x_ssc&uid=urn%3aeop%3adlr%3aeoweb%3a TerraSAR-X_SSC%3A%2Fdims_nz_pl_dfd_XXXXB %2Fdims_op_pl_dfd_%2F%2FTerraSAR-X_SSC&a mp;recordschema=om" rel="alternate" title="url for retrieving full details of the product: urn:eop:dlr:eoweb:terrasar-x_ssc:/dims_nz_pl_dfd_xxxxb /dims_op_pl_dfd_//terrasar -X_SSC" type="application/atom+xml"/> <published> t08:44:56z</published> <title>urn:eop:dlr:eoweb:terrasar-x_ssc:/dims_nz_pl_dfd_xxxxb /dims_op_pl_d fd_//terrasar-x_ssc</title> <updated> t15:58:11z</updated> <summary type="html"><![cdata[ <table>... </table>]]> </summary> <link href=" Sendai_D_Orbit042_ tar.gz" rel="enclosure" title="download" type="application/x-binary"/> <sar:earthobservation xmlns:sar=" xmlns:gml=" xmlns:atm=" xmlns:eop=" xmlns:gmlov=" xmlns:om=" xmlns:opt=" xmlns:ows=" xmlns:swe=" xmlns:xlink=" xmlns:xsi=" gml:id="idn10026" xsi:schemalocation=" <om:phenomenontime> <gml:timeperiod gml:id="tpn10026"> <gml:beginposition> t20:43:02.512</gml:beginposition> <gml:endposition> t20:43:10.511</gml:endposition> </gml:timeperiod> </om:phenomenontime> <om:resulttime> <gml:timeinstant gml:id="tin10026"> <gml:timeposition> t11:02:47.999</gml:timeposition> </gml:timeinstant> </om:resulttime> <om:procedure> <eop:earthobservationequipment gml:id="eoen10026"> Page 73/116

74 <eop:platform> <eop:platform> <eop:shortname>tx01</eop:shortname> <eop:serialidentifier>1</eop:serialidentifier> <eop:orbittype>leo</eop:orbittype> </eop:platform> </eop:platform> <eop:instrument> <eop:instrument> <eop:shortname>sar</eop:shortname> </eop:instrument> </eop:instrument> <eop:sensor> <eop:sensor> <eop:sensortype>radar</eop:sensortype> <eop:operationalmode codespace="urn:eop:phr:sensormode">sar_sm_</eop:operationalmode> <eop:swathidentifier>strip_010</eop:swathidentifier> </eop:sensor> </eop:sensor> <eop:acquisitionparameters> <sar:acquisition> <eop:orbitnumber>7056</eop:orbitnumber> <eop:orbitdirection>ascending</eop:orbitdirection> <eop:orbitduration uom="ms"> </eop:orbitduration> <eop:incidenceangle uom="deg"> </eop:incidenceangle> <sar:polarisationmode>s</sar:polarisationmode> <sar:polarisationchannels>hh</sar:polarisationchannels> <sar:antennalookdirection>right</sar:antennalookdirection> <sar:minimumincidenceangle uom="deg"> </sar:minimumincidenceangle> <sar:maximumincidenceangle uom="deg"> </sar:maximumincidenceangle> <sar:dopplerfrequency uom="deg">0.0</sar:dopplerfrequency> </sar:acquisition> </eop:acquisitionparameters> </eop:earthobservationequipment> </om:procedure> <om:observedproperty xlink:href="#phenom1"/> <om:featureofinterest> <eop:footprint gml:id="fpn10026"> <eop:multiextentof> <gml:multisurface gml:id="mulsfn10027" srsname="epsg:4326"> <gml:surfacemembers> <Polygon xmlns=" gml:id="pon10098" srsname="urn:ogc:def:crs:epsg:6.15:4326"> <exterior> <LinearRing> <pos> </pos> <pos> </pos> <pos> </pos> <pos> </pos> <pos> </pos> </LinearRing> </exterior> </Polygon> </gml:surfacemembers> </gml:multisurface> </eop:multiextentof> </eop:footprint> </om:featureofinterest> <om:result> <eop:earthobservationresult gml:id="eorn10026"> <eop:browse> <eop:browseinformation> <eop:type>quicklook</eop:type> <eop:subtype>ql</eop:subtype> Page 74/116

75 <eop:referencesystemidentifier codespace="epsg">epsg:4326</eop:referencesystemidentifier> <eop:filename> <ows:servicereference xlink:href=" mous/ "> <ows:requestmessage/> </ows:servicereference> </eop:filename> </eop:browseinformation> </eop:browse> <eop:browse> <eop:browseinformation> <eop:type>thumbnail</eop:type> <eop:subtype>ql</eop:subtype> <eop:referencesystemidentifier codespace="epsg">epsg:4326</eop:referencesystemidentifier> <eop:filename> <ows:servicereference xlink:href=" mous/ "> <ows:requestmessage/> </ows:servicereference> </eop:filename> </eop:browseinformation> </eop:browse> <eop:product> <eop:productinformation> <eop:filename> <ows:servicereference xlink:href=" <ows:requestmessage/> </ows:servicereference> </eop:filename> </eop:productinformation> </eop:product> <eop:parameter> <eop:parameterinformation> <eop:unitofmeasure uom="c"/> <eop:phenomenon> <swe:phenomenon xmlns:ns1=" ns1:id="phenom1"> <name xmlns=" </swe:phenomenon> </eop:phenomenon> </eop:parameterinformation> </eop:parameter> </eop:earthobservationresult> </om:result> <eop:metadataproperty> <eop:earthobservationmetadata> <eop:identifier>urn:eop:dlr:eoweb:terrasar-x_ssc:/dims_nz_pl_dfd_xxxxb /dims_op_pl_dfd_//TerraSAR-X_SSC:eop</eop:identifier> <eop:doi>terrasar-x_ssc:/dims_nz_pl_dfd_xxxxb /dims_op_pl_dfd_//te rrasar-x_ssc</eop:doi> <eop:parentidentifier>urn:eop:dlr:eoweb:geohazard.supersite.terrasar-x_ssc</eop:paren tidentifier> <eop:acquisitiontype>other</eop:acquisitiontype> <eop:producttype>geohazard.supersite.terrasar-x_ssc</eop:producttype> <eop:status>archived</eop:status> <eop:downlinkedto> <eop:downlinkinformation> <eop:acquisitionstation codespace="urn:eop:phr:stationcode">d</eop:acquisitionstation> <eop:acquisitiondate> t20:43:06.511</eop:acquisitiondate> </eop:downlinkinformation> </eop:downlinkedto> <eop:archivedin> <eop:archivinginformation> Page 75/116

76 <eop:archivingcenter codespace="urn:eop:phr:stationcode">dlr</eop:archivingcenter> <eop:archivingdate> t08:44:56.501</eop:archivingdate> </eop:archivinginformation> </eop:archivedin> <eop:imagequalitydegradation uom="%">-</eop:imagequalitydegradation> <eop:processing> <eop:processinginformation/> </eop:processing> </eop:earthobservationmetadata> </eop:metadataproperty> </sar:earthobservation> <georss:where xmlns:gml=" <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <media:group> <media:content medium="image" type="image/jpeg" url=" "> <media:category scheme=" </media:content> <media:content medium="image" type="image/jpeg" url=" "> <media:category scheme=" </media:content> </media:group> </entry>... </feed> This response is visualised in Firefox as shown below. Note that the actual dataset URL is shown as an enclosure Page 76/116

77 Figure 10: OGC search result in Atom format shown in Firefox. The following example is identical to the previous one, but the media type requested is RSS. In this case, a Web browser (e.g. Firefox) not only shows the dataset download link (enclosure), but also the thumbnail and browse image. Example 22: OGC dataset search request (RSS) Formatted for readability: httpaccept=application/rss+xml & parentidentifier = Page 77/116

78 EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC & startdate = T00:00:00Z & enddate = T00:00:00Z & recordschema = om & orbitdirection = D URL-encoded: Identifier=EOP:DLR:EOWEB:Geohazard.Supersite.TerraSAR-X_SSC&startDate= T00:00:00Z&endDate= T00:00:00Z&recordSchema=om&orbitDirection=D Figure 11: OGC search result in RSS format shown in Firefox. Limitations: Many of the dataset series will not return dataset metadata for searches which are too wide and would return too many results. It is recommended to use a small bounding box and limited time period to limit the number of search results. Page 78/116

79 5.4 G-POD Connector Dataset series metadata This connector provides access to ESA G-POD dataset series metadata served via the OpenSearch protocol. The EOP:ESA:GPOD-EO parentidentifier represents the full set of G-POD dataset series metadata in FedEO Search Parameters The following OSDD defines the supported search interface: It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" xmlns:semantic=" /opensearch/extensions/semantic/1.0/" xmlns:sru=" xmlns:time=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url rel="self" template=" type="application/opensearchdescription+xml"/> <Url indexoffset="0" pageoffset="0" template=" Identifier=EOP:ESA:GPOD-EO&subject=EOP:ESA:GPOD-EO&maximumRecords={count?}&startRecord={ startindex?}&query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={ geo:box?}&uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo: acquisitionstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&am p;lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/atom+xml"/> <Url indexoffset="0" pageoffset="0" template=" {count?}&startrecord={startindex?}&query={searchterms?}&startdate={time:start?}&endd ate={time:end?}&bbox={geo:box?}&uid={geo:uid?}&processingcenter={eo:processingcenter?}&a mp;acquisitionstation={eo:acquisitionstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/vnd.google-earth.kml+xml"/> <Url indexoffset="0" pageoffset="0" template=" OP:ESA:GPOD-EO&subject=EOP:ESA:GPOD-EO&maximumRecords={count?}&startRecord={startIndex?} &query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&am p;uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisitions tation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&lat={geo:l at?}&lon={geo:lon?}&radius={geo:radius?}" type="text/plain"/> <Url indexoffset="0" pageoffset="0" template=" dentifier=eop:esa:gpod-eo&subject=eop:esa:gpod-eo&maximumrecords={count?}&startrecord={s tartindex?}&query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={g eo:box?}&uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:a cquisitionstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&amp ;lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/rdf+xml"/> <Url indexoffset="0" pageoffset="0" template=" tidentifier=eop:esa:gpod-eo&subject=eop:esa:gpod-eo&maximumrecords={count?}&startrecord= {startindex?}&query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox= Page 79/116

80 {geo:box?}&uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo :acquisitionstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&a mp;lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/xhtml+xml"/> <Tags>FEDEO, ESA, Earth Observation, Digital Repository, HMA, HMA-S, HMA-SE</Tags>... </OpenSearchDescription> Response Formats The response formats supported are not generated by the FedEO Connector but by the backend system directly. Response media type application/atom+xml application/rss+xml application/sru+xml application/rdf+xml application/vnd.googleearth.kml+xml text/plain application/xhtml+xml Comments Available - as implemented by the backend system. Future work. Future work. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Table 19: EOP:ESA:GPOD-EO Supported Media Types (Dataset Series) {sru:recordschema} Media type Comments - application/rdf+xml Default. Returns a response with atom:links to different metadata formats including: RDF format iso Not supported - Future work server-choice application/gml+xml Not supported - Future work Table 20: EOP:ESA:GPOD-EO Supported Record Schemas (Dataset Series) Examples The following is an example showing the use of a number of search parameters. Page 80/116

81 Example 23: EOP:ESA:GPOD-EO dataset series search request Formatted for readability: httpaccept=application/atom+xml & query = MSG & parentidentifier = EOP:ESA:GPOD-EO & startrecord = 1 & maximumrecords = 10 & startdate = T00:00:00Z & enddate = T00:00:00Z URL-encoded: =MSG&parentIdentifier=EOP:ESA:GPOD- EO&startRecord=1&maximumRecords=10&startDate= T00:00:00Z&endDate= T00:00:00Z An extract of the response for this request is shown below. For each entry in the response, a <link> with rel= search gives access to the OSDD for the dataset series. The <dc:identifier> element identifies the dataset series identifier to be used in a subsequent dataset search, e.g. MSG_SEVIRI in the example below. <?xml version="1.0" encoding="utf-8"?> <feed xml:lang="en" xmlns=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:os=" xmlns:dc=" xmlns:georss=" xmlns:gml=" xmlns:geo=" <title>discovery feed for Search Services</title> <subtitle type="html">... </subtitle> <generator uri=" version="1.3.8">terradue CAS</generator> <updated> t15:12:38zz</updated> <id> &count=10&startpage=&startindex=0&sort=&q=msg&start= t00:00:00z&amp ;stop= t00:00:00z&ingested=&bbox=&geometry=&uid=&processingcenter=& processorversion=&acquisitionstation=&size=&orbitnumber=&tracknumber=</id> <link rel="self" type="application/atom+xml" href=" amp;start= t00:00:00z&stop= t00:00:00z"> </link> <link rel="first" type="application/atom+xml" href=" amp;start= t00:00:00z&stop= t00:00:00z"> </link> <link rel="last" type="application/atom+xml" href=" amp;start= t00:00:00z&stop= t00:00:00z"> </link> <link rel="search" type="application/opensearchdescription+xml" href=" </link> <os:totalresults>1</os:totalresults> <os:startindex>0</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query role="request" count="10" startindex="0" searchterms="msg" time:start=" t00:00:00z" time:end=" t00:00:00z"> Page 81/116

82 </os:query> <entry> <id> <title>msg SEVIRI L1 TOA</title> <published> t15:50:41.032z</published> <updated> t14:36:06.157z</updated> <dc:identifier>msg_seviri</dc:identifier> <dc:date> t01:00:00.000z/ t14:45:00.000z</dc:date> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link rel="alternate" type="application/atom+xml" title="atom feed" href=" </link> <link rel="search" type="application/opensearchdescription+xml" href=" title="search the MSG_SEVIRI"> </link> <link rel="via" type="application/rdf+xml" title="rdf metadata entry" href=" </link> <content type="html">... </content> </entry> </feed> Note 5 Note 6 Each entry element in the response contains an atom:link element with relation via. This link points to the dataset series metadata in RDF format. In future versions, alternate may be used instead to comply with OGC Each entry element in the response contains an atom:link element with relation search. This link currently points to the native OSDD document instead of the FedEO dataset series-specific OSDD. Figure 12: EOP:ESA:GPOD-EO dataset series search result shown in Firefox. Page 82/116

83 5.4.2 Dataset metadata The dataset series identifiers, i.e. {dc:subject} or {eo:parentidentifier} supported by the EOP:ESA:GPOD-EO dataset search are listed in the Explain document (See Appendix A). Examples include MIR_SC_F0_, MSG_SEVIRI etc Search Parameters The following OSDD lists the supported search parameters in the URL template section: It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" xmlns:semantic=" /opensearch/extensions/semantic/1.0/" xmlns:sru=" xmlns:time=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url rel="self" template=" type="application/opensearchdescription+xml"/> <Url indexoffset="0" pageoffset="0" template=" Identifier=MSG_SEVIRI&subject=MSG_SEVIRI&maximumRecords={count?}&startRecord={startIndex?}&query={searchTerms?}&startDate={time:start?}&endDate={time:end?}&bbox={geo:box?}& amp;uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisitio nstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&lat={geo :lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/atom+xml"/> <Url indexoffset="0" pageoffset="0" template=" mp;startrecord={startindex?}&query={searchterms?}&startdate={time:start?}&enddate={time: end?}&bbox={geo:box?}&uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisi tionstation={eo:acquisitionstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&nam e={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/vnd.google-earth.kml+xml"/> <Url indexoffset="0" pageoffset="0" template=" SG_SEVIRI&subject=MSG_SEVIRI&maximumRecords={count?}&startRecord={startIndex?}&query ={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&uid={geo :uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisitionstation?}&a mp;orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&lat={geo:lat?}&l on={geo:lon?}&radius={geo:radius?}" type="text/plain"/> <Url indexoffset="0" pageoffset="0" template=" dentifier=msg_seviri&subject=msg_seviri&maximumrecords={count?}&startrecord={startindex? }&query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?}&a mp;uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisition Station?}&orbitNumber={eo:orbitNumber?}&track={eo:track?}&name={geo:name?}&lat={geo: lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/rdf+xml"/> <Url indexoffset="0" pageoffset="0" template=" tidentifier=msg_seviri&subject=msg_seviri&maximumrecords={count?}&startrecord={startinde x?}&query={searchterms?}&startdate={time:start?}&enddate={time:end?}&bbox={geo:box?} &uid={geo:uid?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisiti onstation?}&orbitnumber={eo:orbitnumber?}&track={eo:track?}&name={geo:name?}&lat={ge o:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="application/xhtml+xml"/> <Tags>FEDEO, ESA, Earth Observation, Digital Repository, HMA, HMA-S, HMA-SE</Tags> Page 83/116

84 ... </OpenSearchDescription> Response Formats The response formats supported are not generated by the FedEO Connector but by the backend system directly. Response media type application/atom+xml application/rss+xml application/sru+xml application/rdf+xml application/vnd.googleearth.kml+xml text/plain application/xhtml+xml Comments Available - as implemented by the backend system. Future work. Future work. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Table 21: EOP:ESA:GPOD-EO Supported Media Types (Datasets) {sru:recordschema} Media type Comments - application/rdf+xml Default. Returns a response with atom:links to different metadata formats including: RDF format om Not supported - Future work server-choice application/gml+xml Not supported - Future work Table 22: EOP:ESA:GPOD-EO Supported Record Schemas (Datasets) Examples The following is an example showing the use of a number of search parameters. Example 24: EOP:ESA:GPOD-EO dataset search request Formatted for readability: Page 84/116

85 httpaccept = application/atom+xml & subject = MSG_SEVIRI & startdate = T00:00:00Z & enddate = T00:00:00Z & bbox = -74,17,-67,20.5 URL-encoded: ject=msg_seviri&startdate= t00:00:00z&enddate= T00:00:00Z&bbox=-74,17,-67,20.5 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xml:lang="en" xmlns=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:os=" xmlns:dc=" xmlns:georss=" xmlns:gml=" xmlns:geo=" <title>catalogue Search Feed for MSG SEVIRI L1 TOA</title> <subtitle type="html">... </subtitle> <generator uri=" version="1.3.8">terradue CAS</generator> <updated> t15:22:30zz</updated> <id> ol=&ce=&count=10&startpage=&startindex=0&sort=&q=&start= t00:00 :00Z&stop= T00:00:00Z&ingested=&bbox=-74,17,-67,20.5&geometry=&uid=&amp ;processingcenter=&processorversion=&acquisitionstation=&size=&orbitnumber=&trac knumber=</id> <link rel="self" type="application/atom+xml" href=" &start= t00:00:00z&stop= t00:00:00z&bbox=-74,17,-67,20.5"> </link> <link rel="first" type="application/atom+xml" href=" &start= t00:00:00z&stop= t00:00:00z&bbox=-74,17,-67,20.5"> </link> <link rel="next" type="application/atom+xml" href=" 0&start= T00:00:00Z&stop= T00:00:00Z&bbox=-74,17,-67,20.5"> </link> <link rel="last" type="application/atom+xml" href=" 10&start= T00:00:00Z&stop= T00:00:00Z&bbox=-74,17,-67,20.5"> </link> <link rel="search" type="application/opensearchdescription+xml" href=" </link> <link rel="search" type="application/opensearchdescription+xml" href=" </link> <os:totalresults>192</os:totalresults> <os:startindex>0</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query role="request" count="10" startindex="0" time:start=" t00:00:00z" time:end=" t00:00:00z" geo:box="-74,17,-67,20.5"> </os:query> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> Page 85/116

86 </gml:exterior> </gml:polygon> </georss:where> <entry> <id> -MSG1 - -PRO /atom</id> <title>h-000-msg1 -MSG1 - -PRO </title> <published> t18:36:13.000z</published> <updated> t00:00:00.000z</updated> <dc:date> t05:30:00.000z</dc:date> <gml:validtime> <gml:timeperiod> <gml:beginposition> t05:30:00.000z</gml:beginposition> <gml:endposition> t05:45:00.000z</gml:endposition> </gml:timeperiod> </gml:validtime> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link rel="alternate" type="application/atom+xml" title="atom entry link" href=" -MSG1 - -PRO /atom"> </link> <link rel="alternate" type="application/vnd.google-earth.kml+xml" title="kml file" href=" -MSG1 - -PRO /kml"> </link> <link rel="via" type="application/rdf+xml" title="rdf metadata entry" href=" -MSG1 - -PRO /rdf"> </link> <link rel="enclosure" type="application/x-binary" length="425551" title=" File H-000-MSG1 - MSG1 - -PRO in the application/x-binary format" href=" -MSG1 - - PRO "> </link> <content type="html">... </content> </entry>... </feed> Note 7 Each entry element in the response contains an atom:link element with relation via. This link points to the dataset series metadata in RDF format. In future versions, alternate may be used instead to comply with OGC Page 86/116

87 This response is visualised in Firefox as shown below. Figure 13: EOP:ESA:GPOD-EO dataset search result shown in Firefox. Page 87/116

88 5.5 Virtual Archive 4 Connector Dataset series metadata This connector provides access to ESA Virtual Archive 4 (VA4) dataset series metadata served via the OpenSearch protocol. The EOP:ESA:EO-VIRTUAL-ARCHIVE4 parentidentifier represents the full set of VA4 dataset series metadata in FedEO Search Parameters The following OSDD defines the supported search interface: VIRTUAL-ARCHIVE4 It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" xmlns:semantic=" /opensearch/extensions/semantic/1.0/" xmlns:sru=" xmlns:time=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url rel="self" template=" VIRTUAL-ARCHIVE4" type="application/opensearchdescription+xml"/> <Url indexoffset="0" pageoffset="0" template=" Identifier=EOP:ESA:EO-VIRTUAL-ARCHIVE4&subject=EOP:ESA:EO-VIRTUAL-ARCHIVE4&maximumRecords={c ount?}&startrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?} &startdate={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&amp ;acquisitionstation={eo:acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber ={eo:orbitnumber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifi er?}&polarisationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&amp ;lon={geo:lon?}&radius={geo:radius?}" type="application/atom+xml"/> <Url indexoffset="0" pageoffset="0" template=" OP:ESA:EO-VIRTUAL-ARCHIVE4&subject=EOP:ESA:EO-VIRTUAL-ARCHIVE4&maximumRecords={count?}&s tartrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startda te={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&acquisition Station={eo:acquisitionStation?}&orbitDirection={eo:orbitDirection?}&orbitNumber={eo:orbitNu mber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&pol arisationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lo n?}&radius={geo:radius?}" type="text/plain"/> <Url indexoffset="0" pageoffset="0" template=" entidentifier=eop:esa:eo-virtual-archive4&subject=eop:esa:eo-virtual-archive4&maximumrecords ={count?}&startrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:bo x?}&startdate={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}& amp;acquisitionstation={eo:acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnum ber={eo:orbitnumber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathident ifier?}&polarisationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}& amp;lon={geo:lon?}&radius={geo:radius?}" type="text/tab-separated-values"/> <Url indexoffset="0" pageoffset="0" template=" dentifier=eop:esa:eo-virtual-archive4&subject=eop:esa:eo-virtual-archive4&maximumrecords={co unt?}&startrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}& Page 88/116

89 amp;startdate={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}& acquisitionstation={eo:acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber= {eo:orbitnumber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifie r?}&polarisationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}& lon={geo:lon?}&radius={geo:radius?}" type="application/rdf+xml"/> <Url indexoffset="0" pageoffset="0" template=" P:ESA:EO-VIRTUAL-ARCHIVE4&subject=EOP:ESA:EO-VIRTUAL-ARCHIVE4&maximumRecords={count?}&st artrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startdat e={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&acquisitions tation={eo:acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:orbitnum ber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&pola risationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radius?}" type="text/html"/> <Tags>FEDEO, ESA, Earth Observation, Digital Repository, HMA, HMA-S, HMA-SE</Tags>... </OpenSearchDescription> Response Formats The response formats supported are not generated by the FedEO Connector but by the backend system directly. Response media type application/atom+xml application/rss+xml application/sru+xml application/rdf+xml text/plain text/html text/tab-separated-values Comments Available - as implemented by the backend system. Future work. Future work. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Table 23: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Media Types {sru:recordschema} Media type Comments - application/rdf+xml Default. Returns a response with atom:links to different metadata formats including: RDF format om Not supported - Future work server-choice application/gml+xml Not supported - Future work Table 24: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Record Schemas Page 89/116

90 Examples The following is an example showing the use of a number of search parameters. Example 25: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series search request Formatted for readability: httpaccept=application/atom+xml & parentidentifier = EOP:ESA:EO-VIRTUAL-ARCHIVE4 & query = ASAR & startrecord = 1 & maximumrecords = 10 & startdate = T00:00:00Z & enddate = T00:00:00Z URL-encoded: tidentifier=eop:esa:eo-virtual- ARCHIVE4&query=ASAR&startRecord=1&maximumRecords=10&startDate= T00:00:00Z&endDate= T00:00:00Z An extract of the response for this request is shown below. For each entry in the response, a <link> with rel= search gives access to the OSDD for the dataset series. The <dc:identifier> element identifies the dataset series identifier to be used in a subsequent dataset search, e.g. ASA_IM 0P in the example below. <?xml version="1.0" encoding="utf-8"?> <feed xml:lang="en" xmlns=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:os=" xmlns:dc=" xmlns:georss=" xmlns:gml=" xmlns:geo=" <title>discovery feed for Search Services</title> <subtitle type="html">... </subtitle> <generator uri=" version="1.4.0">terradue CAS</generator> <updated> t15:36:35zz</updated> <id> <link rel="self" type="application/atom+xml" href=" t= t00:00:00z&stop= t00:00:00z"> </link> <link rel="first" type="application/atom+xml" href=" t= t00:00:00z&stop= t00:00:00z"> </link> <link rel="last" type="application/atom+xml" href=" t= t00:00:00z&stop= t00:00:00z"> </link> <link rel="search" type="application/opensearchdescription+xml" href=" </link> <os:totalresults>3</os:totalresults> <os:startindex>0</os:startindex> <os:itemsperpage>10</os:itemsperpage> Page 90/116

91 <os:query role="request" count="10" startindex="0" searchterms="asar" time:start=" t00:00:00z" time:end=" t00:00:00z"> </os:query> <entry> <id> 0P/atom</id> <title>asar Image Mode source packets Level 0 (ASA_IM 0P)</title> <published> t11:05:29.511z</published> <updated> t02:01:45.177z</updated> <rights> </rights> <dc:identifier>asa_im 0P</dc:identifier> <dc:date> t08:07:37.387z/ t06:12:59.146z</dc:date> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link rel="alternate" type="application/atom+xml" title="atom feed" href=" 0P/atom"> </link> <link rel="search" type="application/opensearchdescription+xml" href=" 0P/description/" title="search the ASA_IM 0P"> </link> <link rel="via" type="application/rdf+xml" title="rdf metadata entry" href=" 0P/rdf?count=0"> </link> <content type="html">... </content> </entry>... </feed> Page 91/116

92 This response is visualised in Firefox as shown below. Figure 14: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series search result shown in Firefox. The search response contains a link to the RDF metadata of the dataset series. An example is included below. It should be noted that the <dc:identifier> element contains the dataset series identifier which can be used as value for {eo:parentidentifier} to perform dataset searches in this dataset series. Example 26: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset series metadata (extract) <?xml version="1.0" encoding="utf-8"?> <rdf:rdf > <rdf:description rdf:about=" 0P/rdf"> <os:totalresults>37073</os:totalresults> <os:startindex>0</os:startindex> <dc:creator>terradue CAS version 1.4.0</dc:creator> <dc:date> t14:02:32z</dc:date> <dc:sizeorduration>0.027 sec</dc:sizeorduration> <atom:link atom:rel="self" atom:type="application/rdf+xml" atom:href=" 0P/rdf/?startIndex=0&count=0"/> <atom:link atom:rel="search" atom:type="application/opensearchdescription+xml" atom:href=" 0P/description"/> <os:query os:role="request" count="0"/> </rdf:description> <dclite4g:series rdf:about=" 0P/rdf"> <dc:identifier>asa_im 0P</dc:identifier> <dc:description rdf:resource=" 0P/description/"/> Page 92/116

93 <atom:link atom:rel="search" atom:type="application/opensearchdescription+xml" atom:title="search the ASA_IM 0P Series" atom:href=" 0P/description/"/> <dc:title>asar Image Mode source packets Level 0 (ASA_IM 0P)</dc:title>... </dclite4g:series> </rdf:rdf> Dataset metadata The dataset series identifiers, i.e. {dc:subject} or {eo:parentidentifier} supported by the EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset search are listed in the Explain document (See Appendix A). They correspond to the identifiers used in the <dc:identifier> element of the dataset series metadata. Examples include ASA_IM 0P, ASA_IMS_1P, ER02_SAR_IM 0P etc Search Parameters The following OSDD lists the supported search parameters in the URL template section: 0P It contains the following information: <?xml version="1.0" encoding="utf-8"?> <OpenSearchDescription xmlns=" xmlns:dc=" xmlns:eo=" xmlns:geo=" xmlns:semantic=" /opensearch/extensions/semantic/1.0/" xmlns:sru=" xmlns:time=" <ShortName>FEDEO Clearinghouse</ShortName> <LongName>Earth Observation Catalogue</LongName> <Description>Provides interoperable access, following ISO/OGC interface guidelines, to Earth Observation metadata.</description> <Url rel="self" template=" 0P" type="application/opensearchdescription+xml"/> <Url indexoffset="0" pageoffset="0" template=" Identifier=ER02_SAR_IM 0P&subject=ER02_SAR_IM 0P&maximumRecords={count?}&startRecord={ startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startdate={time:sta rt?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo: acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:orbitnumber?}&f rame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&polarisationcha nnels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radi us={geo:radius?}" type="application/atom+xml"/> <Url indexoffset="0" pageoffset="0" template=" R02_SAR_IM 0P&subject=ER02_SAR_IM 0P&maximumRecords={count?}&startRecord={startIndex?} &query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startdate={time:start?}&end Date={time:end?}&processingCenter={eo:processingCenter?}&acquisitionStation={eo:acquisitionS tation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:orbitnumber?}&frame={eo:fra me?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&polarisationchannels={eo:po larisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radi us?}" type="text/plain"/> <Url indexoffset="0" pageoffset="0" template=" 0P&subject=ER02_SAR_IM 0P&maximumRecords={count?}& amp;startrecord={startindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&st artdate={time:start?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&acquis Page 93/116

94 itionstation={eo:acquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:or bitnumber?}&frame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&am p;polarisationchannels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={g eo:lon?}&radius={geo:radius?}" type="text/tab-separated-values"/> <Url indexoffset="0" pageoffset="0" template=" dentifier=er02_sar_im 0P&subject=ER02_SAR_IM 0P&maximumRecords={count?}&startRecord={s tartindex?}&query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startdate={time:star t?}&enddate={time:end?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:a cquisitionstation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:orbitnumber?}&fr ame={eo:frame?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&polarisationchan nels={eo:polarisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radiu s={geo:radius?}" type="application/rdf+xml"/> <Url indexoffset="0" pageoffset="0" template=" 02_SAR_IM 0P&subject=ER02_SAR_IM 0P&maximumRecords={count?}&startRecord={startIndex?}& amp;query={searchterms?}&uid={geo:uid?}&bbox={geo:box?}&startdate={time:start?}&endd ate={time:end?}&processingcenter={eo:processingcenter?}&acquisitionstation={eo:acquisitionst ation?}&orbitdirection={eo:orbitdirection?}&orbitnumber={eo:orbitnumber?}&frame={eo:fram e?}&track={eo:track?}&swathidentifier={eo:swathidentifier?}&polarisationchannels={eo:pol arisationchannels?}&name={geo:name?}&lat={geo:lat?}&lon={geo:lon?}&radius={geo:radiu s?}" type="text/html"/> <Tags>FEDEO, ESA, Earth Observation, Digital Repository, HMA, HMA-S, HMA-SE</Tags>... </OpenSearchDescription> Response Formats The response formats supported are not generated by the FedEO Connector but by the backend system directly. Response media type application/atom+xml application/rss+xml application/sru+xml application/rdf+xml application/vnd.googleearth.kml+xml text/plain application/xhtml+xml Comments Available - as implemented by the backend system. Future work. Future work. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Available - as implemented by the backend system. Table 25: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Media Types (Datasets) {sru:recordschema} Media type Comments - application/rdf+xml Default. Returns a response with atom:links to different metadata formats including: RDF format Page 94/116

95 om Not supported - Future work server-choice application/gml+xml Not supported - Future work Table 26: EOP:ESA:EO-VIRTUAL-ARCHIVE4 Supported Record Schemas (Datasets) Examples The following is an example showing the use of a number of search parameters. Example 27: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset search request Formatted for readability: httpaccept = application/atom+xml & parentidentifier = ER02_SAR_IM 0P & startrecord = 1 & maximumrecords = 10 & startdate = T00:00:00Z & enddate = T00:00:00Z & name = paris & radius = 1000 URL-encoded: tidentifier=er02_sar_im 0P&startRecord=1&maximumRecords=10&startDate= T00:00:00Z&endDate= T00:00:00Z&name=paris&radius=1000 An extract of the response for this request is shown below. <?xml version="1.0" encoding="utf-8"?> <feed xml:lang="en" xmlns=" xmlns:time=" /opensearch/extensions/time/1.0/" xmlns:os=" xmlns:dc=" xmlns:georss=" xmlns:gml=" xmlns:geo=" xmlns:metalink="urn:ietf:params:xml:ns:metalink" xmlns:xlink=" <title>catalogue Search Feed for ERS-2 SAR Image Mode source packets Level 0 (ER02_SAR_IM 0P)</title> <subtitle type="html">... </subtitle> <generator uri=" version="1.4.0">terradue CAS</generator> <updated> t15:46:51zz</updated> <id> 0P/atom/</id> <link rel="self" type="application/atom+xml" href=" 0P/atom//?startIndex=0&count=10&amp ;start= t00:00:00z&stop= t00:00:00z&bbox= , , , "> </link> <link rel="first" type="application/atom+xml" href=" 0P/atom//?startIndex=0&count=10&amp Page 95/116

96 ;start= t00:00:00z&stop= t00:00:00z&bbox= , , , "> </link> <link rel="next" type="application/atom+xml" href=" 0P/atom//?startIndex=10&count=10&am p;start= t00:00:00z&stop= t00:00:00z&bbox= , , , "> </link> <link rel="last" type="application/atom+xml" href=" 0P/atom//?startIndex=60&count=10&am p;start= t00:00:00z&stop= t00:00:00z&bbox= , , , "> </link> <link rel="search" type="application/opensearchdescription+xml" href=" 0P/description"> </link> <link rel="search" type="application/opensearchdescription+xml" href=" 0P/description"> </link> <os:totalresults>61</os:totalresults> <os:startindex>0</os:startindex> <os:itemsperpage>10</os:itemsperpage> <os:query role="request" count="10" startindex="0" time:start=" t00:00:00z" time:end=" t00:00:00z" geo:box=" , , , "> </os:query> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <entry> <id> 0P/ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000/atom</id> <title>er02_sar_im 0P_ T104548_ T104605_UPA_82484_0000</title> <published> t03:20:08.000z</published> <updated> t22:25:57.124z</updated> <dc:date> t10:45:48.000z</dc:date> <gml:validtime> <gml:timeperiod> <gml:beginposition> t10:45:48.000z</gml:beginposition> <gml:endposition> t10:46:05.000z</gml:endposition> </gml:timeperiod> </gml:validtime> <georss:where> <gml:polygon> <gml:exterior> <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:exterior> </gml:polygon> </georss:where> <link rel="alternate" type="application/atom+xml" title="atom entry link" href=" 0P/ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000/atom"> </link> <link rel="alternate" type="application/vnd.google-earth.kml+xml" title="kml file" href=" 0P/ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000/kml"> </link> Page 96/116

97 <link rel="alternate" type="text/html" title="html page" href=" 0P/ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000/html"> </link> <link rel="via" type="application/rdf+xml" title="rdf metadata entry" href=" 0P/ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000/rdf"> </link> <link rel="enclosure" type="ceos" length=" " title=" File ER02_SAR_IM 0P_ T104548_ T104605_UPA_82484_0000.CEOS.tar.gz in the CEOS format" href=" 0P_ T104548_ T _UPA_82484_0000.CEOS.tar.gz" metalink:priority="50"> </link> <content type="html">... </content> </entry>... </feed> This response is visualised in Firefox as shown below. Figure 15: EOP:ESA:EO-VIRTUAL-ARCHIVE4 dataset search result shown in Firefox. Page 97/116

98 The datasets are available as enclosures. When selecting the download link, you will have to provide your ESA EO SSO user name and password. Figure 16: Product downloads protected by the ESA EO Single Signon system. Page 98/116