ESA EO Framework (EOF) – CSC – Sentinel-1 Product Unit Definition and Metadata ICD
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-4] 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-1 products.
1.2 Applicable Documents
ID | Document Reference | Document Title |
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 |
S1PD.SP.00110.ASTR | Sentinel-1 Level-0 Product Format Specifications | |
S1-RS-MDA-52-7441 | Sentinel-1 Product Specification | |
S1-RS-MDA-52-7443 | Sentinel-1 IPF Auxiliary Product Specification | |
ESA-EOPG-EOPGC-IF-5 | Copernicus Space Component Ground Segment - Common Entity Definition Document | |
OGC 17-003r2 | OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard | |
[RD-6] | OGC 10-157r4 | OGC Earth Observation Metadata profile of Observations & Measurements |
ESA-EOPG-EOPGC-SP-5 | Sentinels POD Files Definition and Metadata ICD |
Table 1-2 – Reference Documents
1.4 Acronyms, Definitions and Abbreviations
Acronym | Description |
ADG | Auxiliary Data Gathering |
AIS | Automatic Identification System |
AUX | Auxiliary |
CSC | Copernicus Space Component |
DA | Data Access |
FOS | Flight Operations Service |
GS | Ground Segment |
ICD | Interface Control Document |
JSON | JavaScript Object Notation |
LTA | Long Term Archiving |
MPC | Mission Performance Cluster |
ODP | On-Demand Processing |
OLQC | On Line Quality Control |
PDGS | Payload Data Ground Segment |
PR | Systematic Production |
SAFE | Standard 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-1 Products and Auxiliary Data
2.1 Sentinel-1 Product List
[AD-1] describes the list of Sentinel-1 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).
2.2 Sentinel-1 Product Packaging
All Sentinel-1 products follow the corresponding Product Format Specifications and are packaged as compressed ‘zip’ files.
2.3 Sentinel-1 Auxiliary (AUX) Data List
[AD-1] presents the list of Sentinel-1 Auxiliary Data which are required to be circulated between the CSC GS elements.
2.4 Sentinel-1 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 are provided by the Production Service on the Production Interface delivery Point (PRIP).
3 Sentinel-1 Product Entity Properties Mapping
[RD-4] defines the Generic CSC Common Entity Properties.
Table 3-1, below, provides the mapping between these Generic Product Entity Properties and the Sentinel-1 product metadata. Most of the properties defined in [RD-4] are generated by the CSC services. The following table describes the properties that map directly to the Sentinel-1 product metadata.
OData Product Entity Properties | Type | Description | Cardinality | Corresponding Sentinel-1 Metadata | Example | ||||||
L0 Std, Ann, Cal, Noise | L0 GPS | AIS L0 AIS AUX | L1 & L2 | ETAD | AUX | ___OBS__SS |
| ||||
Name | String | Data file name (according to the Sentinel file naming conventions) plus the file extension | 1 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | S1A_IW_SLC__1SDV_ 20160117T103451_ 20160117T103518_ 009533_ 00DD94_D46A.zip |
ContentDate | TimeRange | The sensing range period. Compound property with start and end times in UTC in the format YYYY-MM-DDThh:mm:ss.sssZ | 1 | acquisitionPeriod/ | acquisitionPeriod/ | acquisitionPeriod/ | safe:acquisitionPeriod/ | safe:acquisitionPeriod/ | s1auxsar:standAloneProductionInformation/ | obsProduct/ processingInformation/ referenceANXTime | "ContentDate": |
Footprint | Geography | Footprint of the product expressed as Edm.GeographyPolygon | 0..1 | frameSet/ | n/a | frameSet/ | safe:frameSet/ | safe:frameSet/ | n/a | n/a | geography'SRID=4326; Polygon((),(-41.15749 66.766701,-31.740927 67.629135,-31.479883 66.860405,-40.616844 66.011871,-41.15749 66.766701))' |
GeoFootprint | Geography | Footprint of the product following the GeoJSON format | 0..1 | frameSet/ | n/a | frameSet/ | safe:frameSet/ | safe:frameSet/ | n/a | 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-1 Product Entity Properties mapping to Sentinel-1 metadata
*n/a = not available
4 Sentinel-1 Product Attributes Mapping
All relevant metadata elements of the Sentinel-1 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-5] is preferred for the Attributes Ids. In case an attribute is not defined in [RD-5] the SAFE naming is preferred. The Product Attributes mapping for all Sentinel-1 products is described in the Excel file “Sentinel-1 Product Attributes Mapping”, which is packaged together with this document. A summary of the Sentinel-1 Product Attributes mapping across all Sentinel-1 products is presented in Table 4-1. It should be highlighted that, in order to harmonise the metadata model across the Sentinels, in some cases an “alias” for the value defined in the Sentinel-1 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-1 Product Attributes Mapping | Applicability | |||||||||||||||||
L0 Std / | L0 Cal | L0 Noise | L0 | L0 HKTM | L1 | L2 | ETAD | AUX | OLQC Report | ___OBS__SS | AIS L0 | AIS AUX | PR | ADG | MPC | POD | LTA | DA | |
beginningDateTime | x | x | x | x | x | x | x | 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 | x | x | x | x | x | x | x |
startTimeFromAscendingNode | x | x | x | x |
| x | x | x |
|
|
| x |
| x |
|
|
| x | x |
completionTimeFromAscendingNode | x | x | x | x |
| x | x | x |
|
|
| x |
| x |
|
|
| x | x |
platformShortName | x | x | x | x | x | x | x | 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 | x | x | x | x | x | x | x |
instrumentShortName | x | x | x | x |
| x | x | x | x |
|
| x | x | x | x | x |
| x | x |
operationalMode | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
swathIdentifier | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
productClass | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
productConsolidation | x | x | x |
|
|
|
|
|
|
|
|
|
| x |
|
|
| x |
|
productComposition |
|
|
|
|
| x | x | x |
|
|
|
|
| x |
|
|
| x |
|
productType | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x |
productGeneration |
|
|
|
|
|
|
|
| x2 |
|
|
|
| x | x | x |
| x | x |
timeliness |
|
|
|
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
instrumentConfigurationID | x | x | x |
|
| x | x | x | x2 |
|
|
|
| x | x | x |
| x |
|
datatakeID | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x |
|
sliceProductFlag | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x |
|
segmentStartTime |
|
|
|
|
| x | x | x |
|
|
|
|
| x |
|
|
| x |
|
sliceNumber | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
totalSlices | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x |
|
polarisationChannels | x | x | x |
|
| x | x | x |
|
|
|
|
| x |
|
|
| x | x |
orbitNumber | x | x | x | x | x | x | x | x |
|
| x | x |
| x |
|
|
| x | x |
relativeOrbitNumber | x | x | x | x | x | x | x | x |
|
| x | x |
| x |
|
|
| x | x |
cycleNumber | x | x | x | x | x | x | x | x |
|
|
| x |
| x |
|
|
| x | x |
orbitDirection | x | x | x | x |
| x | x | x |
|
|
| x |
| x |
|
|
| x | x |
processingDate | x | x | x | x | x | x | 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 | x | x | x | x | x |
processorName | x | x | x | x | x | x | x | x | x2 |
|
| x | x | x | x | x |
| x | x |
processorVersion | x | x | x | x | x | x | x | x | x |
|
| x | x | x | x | x | x | x | x |
checklistResult |
|
|
|
|
|
|
|
|
| x |
|
|
| x |
|
|
|
|
|
inspectedProduct |
|
|
|
|
|
|
|
|
| x |
|
|
| x |
|
|
|
|
|
inspectedProductType |
|
|
|
|
|
|
|
|
| x |
|
|
| x |
|
|
|
|
|