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-3] 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-3 products.

1.2 Applicable Documents

ID Document Reference Document Title
[AD-1] ESA-EOPG-EOPGC-TN-58 Copernicus Ground Segment Sentinels Data Flow Configuration

Table 1-1 – Applicable Documents

1.3 Reference Documents

ID Document Reference Document Title
[RD-1] S3IPF PDS 008 - i3r8 Sentinel-3 Metadata Specification
[RD-2] GMES-S3GS-EOPG-TN-09-0009 Sentinel-3 PDGS File Naming Convention
[RD-3] ESA-EOPG-EOPGC-IF-5 Copernicus Space Component Ground Segment - Common Entity Definition Document
[RD-4] OGC 17-003r2 OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard
[RD-5] OGC 10-157r4 OGC Earth Observation Metadata profile of Observations & Measurements
[RD-6] ESA-EOPG-EOPGC-TN-13 Copernicus Space Component Ground Segment Operations Glossary
[RD-7] ESA-EOPG-CSCOP-TN-0043 Sentinel-3 LAND PDGS Product Units Configuration
[RD-8] ESA-EOPG-CSCOP-TN-0054 Sentinel-3 Level-0 and Level-1 Product Units Configuration

Table 1-2 – Reference Documents

1.4 Acronyms and Abbreviations

Acronym Description
ADFAuxiliary Data File
ADGAuxiliary Data Gathering
AUXAuxiliary
CSCCopernicus Space Component
DAData Access
FOSFlight Operation Segment
GSGround Segment
ICDInterface Control Document
IPFInstrument Processing Facility
JSONJavaScript Object Notation
LTALong Term Archiving
MPCMission Performance Cluster
PDGSPayload Data Ground Segment
PODPrecise Orbit Determination
PRSystematic Production
SAFEStandard Archive Format for Europe

Table 1-3 – 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-3 PRODUCTS AND AUXILIARY DATA

2.1 Sentinel-3 Product List

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

Products that are disseminated are cut in accordance with “Product Dissemination Units” as described in the Product Units Configuration documentation [RD-7] and [RD-8].

2.2 Sentinel-3 Product Packaging

All Sentinel-3 products follow the corresponding Product Format Specifications and are packaged as non-compressed ‘zip’ packages.

2.3 Sentinel-3 Auxiliary Data List

[AD-1] presents the list of Sentinel-3 Auxiliary Data which are required to be circulated between the CSC GS elements. It must be noted that Sentinel-3 Auxiliary files data set content may change with new processing baselines and therefore, the list provided in [AD-1] is subject to change over time.

3 SENTINEL-3 PRODUCT ENTITY PROPERTIES MAPPING

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

OData Product Entity Properties Type Description Cardinality Corresponding Sentinel-3 Metadata Example
L0, L1 & L2AUX
NameStringData file name (according
to the Sentinel file naming
conventions) plus the file
extension		1n/a
Based on file name		n/a
Based on file name		S3A_OL_2_LFR____20180714T09
0502_20180714T090802_201807
15T133132_0179_047_050_2340
_LN1_O_NT_002.SEN3.zip
ContentDateTimeRangeThe sensing range period.
Compound property with
start and end times in UTC
in the format YYYY-MM-
DDThh:mm:ss.ssssssZ		1sentinel-
safe:acquisitionPeriod/
sentinel-safe:startTime
sentinel-
safe:acquisitionPeriod/
sentinel-safe:stopTime		sentinel3aux:generalP
roductInformation/
sentinel3aux:validity
StartTime
sentinel3aux:generalP
roductInformation/
sentinel3aux:validity
StopTime		"ContentDate":
{
"Start":"2019-07-
23T09:29:46.667482Z",
"End":"2019-07-
23T09:32:46.667482Z"
}
FootprintGeographyFootprint of the product0..1sentinel-safe:frameSet/
sentinel-safe:footPrint/
gml:posList		n/ageography'SRID=4326;
Polygon((),(-41.15749
66.766701,-31.740927
67.629135,-31.479883
66.860405,-40.616844
66.011871,-41.15749
66.766701))'
GeoFootprintGeographyFootprint of the product
following the GeoJSON
format		0..1sentinel-safe:frameSet/
sentinel-safe:footPrint/
gml:posList		n/a"GeoFootprint":{
"type": "Polygon",
"coordinates": [
[
[-59.3169, 2.6367],
[-63.105, -14.0539],
[-60.8506, -14.4245],
[-57.1309, 2.3269],
[-59.3169, 2.6367]
]
]
}

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

*n/a = not available

4 SENTINEL-3 PRODUCT ATTRIBUTES MAPPING

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

OData Attribute Name Sentinel-3 Product Attributes Mapping Applicability
L0 Products MWR OLCI SRAL SLSTR SYNERGY AUX PR ADG POD LTA DA
beginningDateTime x x x x x x x x x x x x
endingDateTime x x x x x x x x x x x x
platformShortName x x x x x x x x x x x x
platformSerialIdentifier x x x x x x x x x x x x
instrumentShortName x x x x x x x x x
operationalMode x x x x x x x x x
productType x x x x x x x x x x x x
timeliness x x x x x x x x x x x x
baselineCollection x x x x x x x x x x x x
brightCover x x x x
snowOrIceCover x x x x
salineWaterCover x x 1 x x x x
coastalCover x x 1 x x x x
freshInlandWaterCover x x 1 x x x x
tidalRegionCover x x 1 x x x x
landCover x x x 1 x x x x
closedSeaCover x x x x
continentalIceCover x x x x
openOceanCover x x x x
cloudCover x x 1 x x x
orbitNumber x x x x x x x x x
lastOrbitNumber x x x x x x x x x
orbitDirection x x x x x x x x x
lastOrbitDirection x x x x x x x x x
relativeOrbitNumber x x x x x x x x x
lastRelativeOrbitNumber x x x x x x x x x
cycleNumber x x x x x x x x x
processingLevel x x x x x x x x x
processingDate x x x x x x x x x x x x
processingCenter x x x x x x x x x x x x
processorName x x x x x x x x x x x x
processorVersion x x x x x x x x x x x x
processingBaseline x x x x x x x x x x
nbFire x 2 x x

Table 4-1 – Sentinel-3 Product Attributes mapping

  1. For SLSTR Products only the metadata reported for the 1 km grid shall be considered.

  2. Only applicable to FRP products (SL_2_FRP___)