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
[AD-1]	ESA-EOPG-EOPGC-TN-58	ESA EO Framework (EOF) – CSC - Data Flow Configuration

Table 1-1 – Applicable Documents

1.3 Reference Documents¶

ID	Document Reference	Document Title
[RD-1]	S1PD.SP.00110.ASTR	Sentinel-1 Level-0 Product Format Specifications
[RD-2]	S1-RS-MDA-52-7441	Sentinel-1 Product Specification
[RD-3]	S1-RS-MDA-52-7443	Sentinel-1 IPF Auxiliary Product Specification
[RD-4]	ESA-EOPG-EOPGC-IF-5	CSC Common Entity Definition Document
[RD-5]	OGC 17-003r2	OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard
[RD-6]	OGC 10-157r4	OGC Earth Observation Metadata profile of Observations & Measurements
[RD-7]	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
EOF	ESA Earth Observation Framework
FOS	Flight Operations Service
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 through the ESA EO Framework (EOF) Copernicus Space Component (CSC).

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 ESA EOF CSC services.

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
OData Product Entity Properties	Type	Description	Cardinality	L0 Std, Ann, Cal, Noise	L0 GPS L0 HKTM	AIS L0 AIS AUX	L1 & L2	ETAD	AUX	___OBS__S S
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	acquisitionPeri od/ startTime acquisitionPeri od/ stopTime	acquisitionPeri od/ startTime acquisitionPeri od/ stopTime	acquisitionPeri od/ startTime acquisitionPeri od/ stopTime	safe:acquisitio nPeriod/ safe:startTime safe:acquisitio nPeriod/ safe:stopTime	safe:acquisitio nPeriod/ safe:startTime safe:acquisitio nPeriod/ safe:stopTime	s1auxsar:stand AloneProducti onInformation / s1auxsar:valid ty	obsProduct/ processingInfo rmation/ referenceANX Time	"ContentDate": { "Start":"2016-01- 17T10:34:51.922Z", "End":"2016-01- 17T10:35:18.872Z" }
Footprint	Geography	Footprint of the product expressed as Edm.GeographyPolygon	0..1	frameSet/ frame/ footPrint/ coordinates	n/a	frameSet/ frame/ footPrint/ coordinates	safe:frameSet/ safe:frame/ safe:footPrint/ gml:coordinat es	safe:frameSet/ safe:frame/ safe:footPrint/ gml:coordinat es	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/ frame/ footPrint/ coordinates	n/a	frameSet/ frame/ footPrint/ coordinates	safe:frameSet/ safe:frame/ safe:footPrint/ gml:coordinat es	safe:frameSet/ safe:frame/ safe:footPrint/ gml:coordinat es	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 EOF CSC services, 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 Ann

L0 Cal

L0
Noise

L0
GPS

L0
HKTM

L1

L2

ETAD

AUX

OLQC
Report

___OBS
__SS

AIS L0

AIS
AUX

PR

ADG

MPC

POD

LTA

DA

beginningDateTime

x

endingDateTime

x

x¹

x

startTimeFromAscendingNode

x

completionTimeFromAscendingNode

x

platformShortName

x

platformSerialIdentifier

x

instrumentShortName

x

x²

x

operationalMode

x

swathIdentifier

x

productClass

x

productConsolidation

x

productComposition

x

productType

x

productGeneration

x²

x

timeliness

x

instrumentConfigurationID

x

x²

x

datatakeID

x

sliceProductFlag

x

segmentStartTime

x

sliceNumber

x

totalSlices

x

polarisationChannels³

x

orbitNumber

x

relativeOrbitNumber

x

cycleNumber

x

orbitDirection

x

processingDate

x

processingCenter

x

processorName

x

x²

x

processorVersion

x

checklistResult

x

inspectedProduct

x

inspectedProductType

x

Table 4-1 – Sentinel-1 Product Metadata Mapping Summary

¹ Only applicable to Sentinel-1 Auxiliary products in EOF format

² Only applicable to Sentinel-1 Auxiliary products in SAFE format

³ In case of double polarisation, both channels shall be valued as a single string, separated by a comma