ESA UNCLASSIFIED - For ESA Official Use Only

1 Introduction

1.1 Purpose and Scope

The scope of this document is to be used as an annex for the CSC Common Entity Definition Document [RD-2] in order to describe the POD files packaging, as well as the Product Entity Properties, the Product Attributes and the corresponding metadata elements that shall be catalogued and queryable, in order to support nominal operations, as well as any other kind of activities (e.g. Reprocessing campaigns, Cal/Val, etc.), for all POD files circulating through the Copernicus Space Component (CSC) Ground Segment (GS) [AD-1]. Additionally, the document describes the format of the POD products’ packages and the applicability to each Sentinel constellation.

1.2 Applicable Documents

Table 1-1 – Applicable Documents

1.3 Reference Documents

Table 1-2 – Reference Documents

1.4 Acronyms, Definitions and Abbreviations

Table 1-2 – Acronyms and Abbreviations

2 POD Products Overview

This section presents an overview of the products and auxiliary files used or generated by the Sentinels POD Service with indication on the Sentinel Mission applicability.

The POD Service generates the following products:

1.POD Orbit Files, i.e. orbit state vectors (OSV) from the orbit determination performed by the Copernicus POD Service based on the GPSR input data.

2.Auxiliary Files, i.e. products requested by the Production Service to be used in support to the Mission data processing. These include attitude data files.

3.GNSS L1b files for all Sentinels. These are disseminated via the Data Access (DA) Service.

4.Quaternions Files for all Sentinels. These are disseminated via the Data Access Service.

The file naming convention, the file formats and the specifications for the files used or generated by the POD Service are described in detail in [RD-1].

Table 2-1 – POD Service Products and Auxiliary Data Files Overview vs. Sentinels mission

3 POD File entity properties mapping

[RD-2] defines the Generic CSC Common Entity Properties. Error! Reference source not found., below, provides the mapping between these Generic Product Entity Properties and the Sentinels POD products metadata. Most of the Product Entity Properties do not map directly to the POD File metadata as they are generated by the CSC services.

Table 3-1 – POD File Entity Properties mapping

4 POD Files Attributes Mapping

All relevant metadata elements of the POD Files shall be indexed in the Product Attributes, additional metadata elements may also be identified if appropriate. In order to provide a harmonised model across the Sentinel missions the JSON property naming from [RD-3] is preferred for the Attributes Names. In case an attribute is not defined in [RD-3] the native naming used in the metadata is preferred. The Product Attributes mapping for the relevant POD Files is described in the Excel file “POD Product Attributes Mapping_v1.0”, which is packaged together with this document. A summary of the POD Product Attributes mapping is presented in Table 4-1 below. It should be highlighted that, in order to harmonise the metadata model across the Sentinel missions, in some cases an “alias” for the value defined in the POD Files metadata is mapped to a standardised value to be used by the CSC GS elements, in other cases a standard value is defined where it is otherwise unavailable from the product.

The External Auxiliary Data follow the data structure presented in section 3.2 of [RD-1]. The attributes for these files are mapped to the xfdumanifest.xml metadata file that is generated when these files are converted to the Sentinel-3 format. Therefore, they follow the structure and metadata of the Sentinel-3 Auxiliary data.

Table 4-1 – POD File Attributes Mapping Summary