Sign In

Copernicus Ground Segment

EOF for Copernicus

ESA EO Framework (EOF) – CSC – Common Entity Definition Document

The  purpose of this  document is  to provide a common  definition  for  basic  entities  managed by  Copernicus Space  Component Ground Segment service elements. These definitions are used  to  derive  the  RESTful Application  Programming  Interfaces  (API)  of  the  GS elements through  which  production,  archival  and distribution of Copernicus Sentinel mission data products may be coordinated.

This  specification drives  the  definition  of the  OData  v4  standard  for  RESTful  APIs for  the  GS  elements, evolving from the v2 standard successfully adopted within the Copernicus Sentinel Data Distribution Service (DHuS) put in place by ESA for the initial missions operations. OData entities and enumerations are detailed, including  applicability  to  GS  elements  and  commonalities.  In  addition,  a  generic  Reporting  interface  is described, intended for the collection of reporting parameters which are expected from each GS element.

The document is intended to compliment the lower-level ‘per-GS element’ ICDs, which describe in more detail the specifics of the OData APIs as applicable to each GS element and any intended sequencing expected to achieve the API objectives. This document is intended to capture the common definition for the basic entities, and is presented as a guideline for the evolution of the lower level ICDs.  In case the APIs within the lower-level ICDs are considered to be further evolved the definitions in this document should be preferred in order to  ensure  a  harmonized  approach  in  the  overall  GS  management avoid  any ad-hoc implementation of  the interfacing between GS elements.

ESA EO Framework (EOF) – CSC – Mission Planning Interface Point ICD

The main purpose of this document is to provide the details of the Mission Planning Interface Point usage by multiple services involved in Copernicus Ground Segment.

This document is applicable to the Mission Planning Interface Point (MPIP) system, both HTTPS, FTPS, and SFTP servers and to all the MPIP clients.

It describes the relevant policies for data transfer initiators, new data availability, and error handling for each entity interfacing the MPIP.

ESA EO Framework (EOF) – CSC – Sentinel-2 Product Unit Definition and Metadata ICD

The scope of this document is to be used as an annex for the ESA EO Framework (EOF) – CSC – Common Entity Definition Document 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-2 product items.

ESA EO Framework (EOF) – CSC – Sentinel-3 Product Unit Definition and Metadata ICD

The scope of this document is to be used as an annex for the ESA EO Framework (EOF) – CSC – Common Entity Definition Document in order to describe:

  • the Product Entity Properties,
  • the Product Attributes
  • the corresponding metadata elements that shall be catalogued and queryable for Sentinel products.

This document provides the mapping and packaging format for the Sentinel-3 products.

ESA EO Framework (EOF) – CSC – Production Interface Delivery Point Specification

The purpose of this document is to specify an https RESTful Application Programming Interface (API) through which Sentinel (or Auxiliary) data products may be discovered and downloaded by authorised users from a Production Interface delivery Point (PRIP). PRIPs are intended as the standard pick-up points for systematically-produced Sentinel data products from within the PDGSs, replacing the diverse interfaces currently in place inside each Sentinel PDGS. The API is (optionally) extended to manage on-demand production, whereby an order triggers a production that is delivered through the Interface delivery Point. In this case the API is referred to within this document as the On-Demand Production Interface delivery Point (ODPRIP).

The specification of this API is intended for:

  • The discovery and download of systematically produced data products
  • The discovery of the processing services available for a given type of parent product
  • The submission of on-demand processing requests for pre-identified parent products
  • Monitoring of on-demand processing requests

ESA EO Framework (EOF) – CSC – Long Term Archive Interface Control Document

The purpose of this document is to specify the interfaces of the Long Term Archive (LTA) within the Copernicus Space Component (CSC) Ground Segment (GS) as part of the overall CSC ESA Operations Framework. 

In particular this document aims to specify an https RESTful Application Programming Interface (API) of the LTA through which Copernicus Sentinel data products may be queried and downloaded by authorised users. This specification uses the latest OData v4 standard for RESTful.

ESA EO Framework (EOF) – CSC – Glossary

This document provides the definition of terms and acronyms commonly used as part of the European Space Agency Copernicus Space Component Ground Segment Operations.

It has been created in response to the need of harmonising the use of terms in the different projects and services.

ESA EO Framework (EOF) – CSC – Data Flow Configuration

This document describes the data flow configuration within the Copernicus Ground Segment, identifying the Sentinel products and auxiliary data files managed by each Ground Segment Service and indicating for each type of data managed by a given Service,
whether the Service acts as a Provider (P) or as a Consumer (C) of the data.

Possible changes in the operational data flow configuration will be reflected in future updates of this document.

ESA EO Framework (EOF) – CSC – System Technical Budget

The system budget scope is to provide an estimate of the expected operations load and the sizing of the general operations.
The budget provides an end-to-end global view on the operational data flows within the EOF Ground Segment for the period 2023 – Q1 2030.

These estimations are made on the basis of current operation volumes. The budget should support the sizing of the critical elements.

ESA EO Framework (EOF) – CSC – Architecture

The overall system architecture for the Copernicus Space Component (CSC) and its evolution have been defined on the basis of user requirements coordinated by the European Commission. The Long-Term Scenario (LTS) describes the main elements of this architecture and is maintained and evolved in an iterative process in close interaction with the European Commission (COM), EUMETSAT and Copernicus Participating States. 

ESA needs to guarantee the continuity of the on-going operations with the maximum level of performances for the flying Copernicus Sentinels while facing the technical and financial challenges to adapt to the evolutions of the CSC architecture. 

The CSC Ground Segment (GS) is based on a service-based architecture and a clear set of operations management principles (management and architectural) hereafter referred as the ESA Earth Observation Framework (EOF).

The EOF encompasses all the activities necessary to successfully deliver the expected level of CSC operations entrusted to ESA (i.e. establishment and maintenance of the new baseline, procurement actions, operations management, reporting, etc.).

The EOF-CSC is documented throughout a complete package describing and specifying the applicable operational concepts as well as the architecture and procurement evolutions to be adopted for establishing the future CSC operations baseline (in particular with respects to the future Expansion Missions, associated with the necessary cost information to size the proposed approach and potential trade-offs). 

The EOF-CSC implementation is based on service architecture with well-identified components that exchange data through Internet respecting defined interfaces. A service presents a simple interface to its consumer that abstracts away the underlying complexity.  Combined with deployments on public cloud infrastructure, the service approach shall offer large adaptability to evolution of the operational scenarios in particular for what regards scalability.

Since the transformation process which started in 2019, the operational CSC Mission and Data management activities have been transferred to cloud based environments (in anticipation of the enlargement of the Copernicus Sentinel missions and in response to the ever-increasing demand for Copernicus data) and the service-oriented approach for each component of the CSC operations has been strengthened to enhance competitiveness, prevent industrial and technical lock-in and introduce the necessary operational flexibility and transparency to allow the adaptation of the Copernicus Space Component activities managed by ESA to future challenges.

Within this context, this document outlines the EOF-CSC Architecture as targeted and as implemented following the Ground Segment transformation phase during the period 2019-2022. This transformed architecture is referred as EOF Copernicus Space Component Architecture in this document or simply as EOF-CSC Architecture. 

This Architecture is a representation of the overall CSC operations in terms of functional decomposition and operational data flows views. The high level architecture corresponds to the first layer of implementation and supports the implementation and the execution of all the activities related to the corresponding operational services and related procurements. The architecture reflects the fundamental principles supporting all aspects of the system, making it robust, scalable, efficient in cost and sustainable for the next 10 years without relying on unknown technological progress whilst being sufficiently flexible to benefit from any relevant future evolutions.

EOF for Destination Earth Platform and Digital Twin Earth

No documents available in this category.

EOF for ESA EO Science missions (Coming Soon)

Categories

Need Support?

Can’t find the answer you’re looking for?
Don’t worry we’re here to help!

Learn More