[Sprint Topic] <Mapping of EOPF data model to STAC model> #58
Description
🧠 Topic
Discuss and improve the current mapping of EOPF data model concepts to STAC concepts.
In terms of product representation, the EOPF data model defines the concepts of EOContainer, EOProduct, EOGroup and EOVariable. In the STAC metadata created by the Sample Service, the following mapping of these concepts into STAC has been applied:
- EOVariable -> Zarr array -> STAC asset
- EOGroup -> Zarr group -> STAC asset
- EOProduct -> Zarr store -> STAC item
- EOContainer -> Zarr store -> STAC item referencing the EOProducts in the container as STAC assets
The issue here is to discuss this approach and gather feedback from the community as well as to identify possbile improvements.
🧩 What problem or opportunity does this sprint address?
This sprint provides a good opportunity to review the current approach together with STAC community members, Sentinel data users, Zarr experts and ESA.
🌍 Why is this relevant to the CNG community?
Its about defining standardized STAC patterns for EOPF Zarr products which are also aligned with the best practices for STAC & Zarr integration in general.
👥 Who should participate?
all members interested in EOPF
🎯 Desired Outcomes or Deliverables
EOPF & STAC integration guidelines as part of Zarr Best Practices or as separate document.
📎 Links
EOPF data model documentation: