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 Product Entity Properties, the Product Attributes and the corresponding metadata elements that shall be catalogued and queryable for Sentinel products. This document provides the mapping and packaging format for the Sentinel-2 product items.

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

1.5 Definitions

Auxiliary Data – Data which enhance processing and utilization of remote sensing instrument data. The auxiliary data are not necessarily captured by the same data collection process as the instrument data. Auxiliary data include data collected by any other platform or process (e.g. meteorological data from ECWMF or NCEP), data providing processing configuration information typically for data calibration and or instrument characterisation (e.g. processing auxiliary files), and data providing information on satellite position and velocity (orbit auxiliary files). Auxiliary data help in data processing, but are also data sets in their own right and may be relevant for end-users in specific User Level Data exploitation scenarios.

2 Sentinel-2 Products and Auxiliary Data

2.1 Sentinel-2 Product Items

[AD-1] describes the list of Sentinel-2 product items which are required to be circulated within the Copernicus Space Component (CSC) GS elements (e.g. from Systematic Production to Long Term Archiving or Data Access systems).

Each Sentinel-2 PDI will be packaged independently of other related PDIs (e.g. of the same datatake), and it is these PDIs that will be circulated between the various CSC GS elements. Each Granule and Datastrip PDI is a tar file consisting of data and metadata. The structures of these Granules and Datastrip PDIs are defined in [RD-1].

A Sentinel-2 Granule PDI contains among its metadata the “Parent_ID” / “DATASTRIP_ID” (corresponding to the “datastripId” attribute, Table 4-1) related to the corresponding Datastrip PDI linked to the Granule. This link establishes the hierarchy between Granule and Datastrip, thus maintaining the relationship at metadata level. Moreover, each Datastrip PDI contains among its metadata the “Group_ID” (“productGroupId” attribute) and this link establishes the hierarchy between Granule/Datastrip and the Datatake.

Level-1C True Colour Image products will be generated and archived independently as well. A Level-1C TCI product will consist of a JPEG 2000 file (jp2), which will have the product metadata embedded in the jp2 file structure.

The Level-1C and Level-2A Granule PDIs represent ortho-images/tiles of 100x100km² in UTM/WGS84 projection, the Granule is in this case a Tile.

Sentinel-2 Level-1 and Level-2 products disseminated via the Data Access service are currently not included in this document. These products will not be disseminated as PDIs, instead, they will be assembled into final User Level Data.

The specifications and structures of all Sentinel-2 Product Data Items and User Products are defined in the Sentinel-2 Products Specification Document [RD-1].

2.2 Sentinel-2 Auxiliary Data

[AD-1] and Table 2-2 presents the list of Sentinel-2 Auxiliary Data which are required to be circulated between the CSC GS elements.

Table 2-2 – Sentinel-2 Auxiliary Data list

Some Sentinel-2 Auxiliary Products come as separate files, one for each spectral band. These are indicated in the last column in Table 2-2 and concern the following products: GIP_VIEDIR, GIP_R2EQOG, GIP_R2DEFI, GIP_R2WAFI, GIP_R2L2NC, GIP_R2DENT, GIP_R2DECT and GIP_R2EOB2. Each of these products shall be indexed separately, by spectral band. The productType attribute of these products (Table 4-1) shall be concatenated by extracting the “File Type” (e.g. GIP_R2DECT) and the band number (e.g. B01) from the product filename and then joining them together, separating them by an underscore: <File_Type>_<Band Number> (e.g. GIP_R2DECT_B01).

2.3 Sentinel-2 OLQC Reports

The On-Line Quality Control (OLQC) performs essential quality checks on each product generated by the processing chain. The results of the quality checks are presented as XML reports. OLQC reports may be issued for each Checklistname for each Sentinel-2 PDI and the contents of each report are configurable. These files are described in detail in [RD-1].

The OLQC reports will be exposed by the Production Service on the Production Interface delivery Point (PRIP).

3 Sentinel-2 product entity properties mapping

[RD-2] defines the Generic CSC Common Entity Properties. Table 3-1, below, provides the mapping between these Generic Product Entity Properties and the Sentinel-2 product metadata. Most of the properties defined in [RD-2] are generated by the CSC services. The following table describes the properties that map directly to the Sentinel-2 product metadata.

Table 3-1 – Product Entity Properties mapping to Sentinel-2 metadata

4 Sentinel-2 Product Attributes Mapping

All relevant metadata elements of the Sentinel-2 products 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 Attribute Names. In case an attribute is not defined in [RD-3] the naming used in the mission specific metadata files, harmonised across the Sentinel missions, is preferred. The Product Attributes mapping for all Sentinel-2 products is described in the Excel file “Sentinel-2 Product Attributes Mapping”, which is packaged with this document. A summary of the Sentinel-2 Product Attributes mapping across all products is presented in Table 4-1. 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 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.

Table 4-1 – Sentinel-2 Product Attributes Mapping