Product & ADF structure and format

EOPF Product and
Auxiliary Data Files structure
format definition

EOPF Products are a harmonized representation of Copernicus Sentinel mission data, acting as the successor to the SAFE format.

Auxiliary Data Files (ADF) provide the necessary supporting data for processing and are governed by a specific framework strategy.

Common Product Structure and Format
(EOPF Data Model)

The EOPF data model is the harmonized successor to the SAFE format for Copernicus missions (Sentinel-1, -2, and -3). Derived from the Unidata Common Data Model (CDM), it organizes data into a hierarchy of groups, variables, dimensions, simple attributes, and organized metadata. It defines both the in-memory representation and storage representations using standard formats like Zarr, COG, and NetCDF4/HDF5.

Documentation

Utility:

Cloud-Optimized:
The storage format is specifically designed for cloud object storage, supporting concurrent processing and selective access to data.
Python-Native Integration:
It is optimized for the Python ecosystem, working seamlessly with libraries such as Dask, Numpy, and Xarray for high-performance processing.
Self-Explaining:
It incorporates structured metadata required for data interpretation directly within the product, using the STAC specification for root-level metadata and Climate and Forecast (CF) conventions for variable attributes.
Harmonization:
It provides a common structure for all Sentinel missions and data types, facilitating interoperability across the framework

Common Auxiliary Data Files
Structure and Format

The Common ADF Structure and Format defines the strategy, naming conventions, and technical specifications for Auxiliary Data Files within the EOPF framework.

It categorizes auxiliary data into static legacy types (e.g., DEMs, Geoids, Climatological data) and dynamic legacy types (e.g., ECMWF/CAMS, Sea Ice Concentration, Sea Surface Temperature).

Documentation

Utility:

Standardized Sharing Strategy:
It establishes clear methods for sharing legacy auxiliary data across different missions and processing components, ensuring efficient data management.
Access and Consistency:
By defining a common File Name Convention and internal structure, it ensures that all processors access auxiliary data in a consistent and predictable manner.
Technical Specifications:
It provides unified format and structure specifications for both static and dynamic data, reducing errors and duplication in data handling.