The EOPF Software Development Environment (SDE) documentation describes a shared development platform created to support the design, implementation and maintenance of Earth Observation data processors within the Copernicus programme. The SDE has been conceived to provide a consistent and harmonised way of working for distributed development teams, reducing fragmentation and encouraging the adoption of common tools, workflows and quality standards across projects.
The SDE is built around GitLab and integrates a wide range of services that guide users through the entire software lifecycle, from initial planning to final release. The platform supports the structured organisation of development activities, collaborative coding, automated building and testing, and controlled distribution of software artefacts.
The documentation explains how the SDE embodies modern DevOps principles in a pragmatic way, combining automation, traceability and quality control with ease of use. It also highlights the role of web-based development tools, continuous integration pipelines and standard packaging mechanisms in supporting cloud-ready and reproducible software solutions. Overall, the document serves both as a practical user guide and as a reference framework that promotes transparency, consistency and long-term maintainability in the development of Copernicus Earth Observation processing software.

The EOPF Core Python Modules (CPM) documentation describes a common software library that provides the core building blocks for the development of Earth Observation data processors within the Copernicus programme. The CPM offers a harmonised set of Python modules that encapsulate essential functionalities needed to handle satellite data, enabling processors to be developed in a consistent, reusable and mission-independent manner.
The document introduces the underlying data model and abstractions used to represent Earth Observation products, including a unified product structure that supports both legacy Sentinel formats and modern, cloud-optimised representations. It explains how these core modules facilitate data access, transformation and computation, while supporting scalable and parallel processing through established open-source technologies. Overall, the documentation serves as a practical reference for understanding how the CPM underpins the technical consistency and interoperability of EOPF‑compliant processing software, complementing the development environment with a shared and well‑defined software foundation.

The ASGARD documentation describes a reusable and open-source geometry library developed within the Earth Observation Processing Framework (EOPF) to support sensor geometry modelling for Copernicus Sentinel missions. ASGARD provides a common and extensible foundation for performing geolocation and other geometry-related computations required during the generation of Level-1 and Level-2 Earth Observation products.
The document explains how ASGARD replaces or complements existing mission-specific and non-open legacy geometry libraries by offering a unified, Python-based approach. It introduces a set of abstract and sensor‑specific geometry models that encapsulate orbital, attitude and pointing information, allowing consistent handling of geometry across different sensors and missions. By defining clear interfaces and reusable components, the documentation highlights how ASGARD contributes to improved transparency, maintainability and interoperability of geometry processing within the EOPF ecosystem, while remaining compatible with current and future Copernicus missions.