Specifications & Architecture
Explore the detailed specifications and architectural design that define the EOF foundation and functionalities.
This document is part of the DestinE Platform technical baseline and complements the Onboarding process in the DestinE platform framework.
This document describes the Data Model of DestinE Platform services, and its guidelines related to the “Destination Earth – DestinE Core Service Platform (DestinE Platform) Framework – Platform & Data Management Services”. This document proposes a well-defined data-entity schema for describing DestinE Platform data assets exposed by services specifying metadata, properties, and attributes related to their main characteristics and functionalities. They serve not only to shape how information is presented to end users but also to establish guidelines for organizing inputs from relevant stakeholders. The data model depicted in this document outlines the context of the DestinE Service Registry, providing a comprehensive schema for describing services registered to the platform. The audience of this document is DestinE Platform Administrators and Service Providers. This document will undergo periodic revisions to incorporate new metadata and requirements, enhancing our ability to identify services and data in accordance with the evolution roadmap.
The Operations Concept Document (OCD) declares the operational concepts applicable to DestinE Platform and provides the associated operational scenarios and information on the system configuration. The purpose of the operational concept is to provide a full picture of how the DestinE Platform is operated.
This System Design Document (SDD) provides a comprehensive view on the design and overall architecture of the DestinE Core Service Platform and in particular on the Platform Management Services (section 4).
The purpose of this document is to provide an exhaustive list of all data operationally produced by the CSC Ground Segment for all Sentinel missions.
The data generated by the CSC Ground Segment is classified as belonging to one of the following categories:
- Sentinel User Level Data: Sentinel payload data generated by the CSC Ground Segment from instrument observations and available to users.
- Sentinel Engineering Level Data: Sentinel payload data generated by the CSC Ground Segment for instrument performance monitoring, calibration activities or as input for the processing of User Level Data. This data is used for operational purposes and is typically not available to users.
- Satellite Housekeeping Telemetry: Sentinel satellite data generated by the CSC Ground Segment for satellite telemetry monitoring purposes. This data is not available to users.
Note: Auxiliary Data (used in support to the generation of the User Level Data, Engineering Level Data or Housekeeping Telemetry) are not within the scope of this 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.
The scope of this document is to be used as an annex for the 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-1 products.
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.
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.
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.
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 applicability for Sentinel-5P products.
The purpose of this document is to specify https RESTful Application Programming Interfaces (APIs) through which CADU data may be discovered and downloaded by authorised users following the patterns and principles defined in the other CSC GS interface delivery points.
The CADU Interface delivery Points (CADIP) describes a standard pick-up point for all Sentinel CADU data collected or generated by the Acquisition Services Ground Stations to be interfaced by the CSC Production Services. This specification uses the latest OData v4 standard for REST-ful APIs.
The API interface is intended to be compliant with the OData v4 standard, however, it is not necessary to fully implement the OData v4 standard.
Compliance to the ICD can be considered as an API contract with a set of API OData v4 style calls, which have to be supported, that shall follow OData query conventions such as URL syntax, filter syntax, content accessing conventions, etc.
The Auxiliary Data Interface Delivery Point (AUXIP) is the pick-up point for Sentinel Auxiliary products. The AUXIP allows clients to straightforwardly discover and retrieve available products through standard interfaces, in this case an OData RESTful API. Clients of the AUXIP are intended to be downloaders whose principal use case requires systematic (or at least regular) retrieval of published Sentinel Auxiliary data products. Examples of AUXIP clients include Production services (both systematic and on-demand), which use the Auxiliary data for the generation of products, Long Term Archives (LTAs), Sentinel Data Hubs (which in turn make the Auxiliary products available to end users), end-to-end Operations Performance monitoring, Reference System, and possibly clients requiring data for Instrument and Product Performance investigations.
The AUXIP is the point of retrieval for newly published Sentinel Auxiliary data products and, as such, it is managed by the various services delivering Auxiliary data. These include the Auxiliary Data Gathering Service the POD Service and the Cal/Val Service. Auxiliary products are supplied on a rolling archive, retention period for the Auxiliary data is specified in the technical specifications for each service, the main purpose of the rolling archive is to provide a buffer allowing the recovery of data in case of unavailability. The API and standard use scenario allow authorized users to discover, with a simple set of filters, the list of products which need to be retrieved in batches, for example since the last check, and then to perform the downloads.
In common with the other Interface Delivery Points, data published by authorized services are to be also registered with the Traceability Service to ensure a long term record the authenticity of all data within the CSC GS.
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 POD files packaging,
- The Product Entity Properties,
- The Product Attributes,
- The corresponding metadata elements that shall be catalogued and queryable, in order to support nominal operations, as well as any other kind of activities (e.g. Reprocessing campaigns, Cal/Val, etc.), for all POD files circulating through the Copernicus Space Component (CSC) Ground Segment (GS), as described by CSC GS Data Flow Configuration.
Additionally, the document describes the format of the POD products’ packages and the applicability to each Sentinel constellation.
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
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.
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.
This document describes the organization of the Copernicus Sentinel data quality functions (calibration, validation, algorithms) funded by the EU Copernicus programme and under the responsibility of the Sensor Performance, Products and Algorithms(SPPA) section of the Earth Observation Mission Management and Product Quality Division (EOP-GM) in the EO Mission Management and Ground Segments Department (EOP-G).
The document is part of the Copernicus Technical Baseline package and complements the other documents providing the Copernicus operations baseline. It is applicable to all EO Copernicus Sentinel missions operated by ESA.
The document does not provide the specific mission data quality requirements, which can be found in other documents, in particular in the Sentinel product list document [RD-5].
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.
The purpose of this document is to list the Auxiliary data managed as part of the CSC Ground Segment for all Sentinel missions. It also indicates which Auxiliary Data Files are to be distributed via the Copernicus Data Access Service and whether access to these will be restricted or not.
This document defines the interface of the Traceability Service as part of the Copernicus Data Space Ecosystem. As such, it will outline the general design principles behind the service, document the interaction through APIs and command line tools, give recommendations for its usage, and ultimately provide guidance for additional integrations with the service.
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.
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.
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 EU Member States 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 EOF-CSC is based on a service-based architecture and a clear set of operations management principles (management and architectural) hereafter referred as the ESA EO Framework (EOF) for the Copernicus Space Component.
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 operations procurement approach adopted for establishing and evolving the 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 a 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 EOF-CSC operations 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 EOF-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 to future challenges.
Within this context, this document outlines the organization and principles of the CSC ESA operations. This Operations Concept describes the overall Sentinels operations set-up, from satellite commanding to the data acquisition, production, archiving and data access. The Operations Concept defines also the process for the operations implementation, procurement and management as well as the approach for maximising the operations performance for mission exploitation in adequacy with the needs and the available resources.
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 EU Member States 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 approach adopted for establishing and evolving the 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 a 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 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 operational activities managed by ESA to future challenges.
Within this context, this document contains the specifications of the EOF for the CSC operational activities entrusted to ESA by the European Commission. The specifications establish the traceability with the current baseline of requirements issued by the European Commission. This document is planned to undergo regular revisions in accordance with possible evolutions of the LTS scenario and the Copernicus Contribution Agreement.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Sentinel Data Access System operated on behalf of ESA, and analyses the trends visible in the public uptake of Copernicus Sentinel data.
This is the ninth and final such report released by the data access service provider, Serco Italia Spa, and covers the period 1 January 2023 to 31 October 2023.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Data Access System operated by ESA during 2022 and analyses the trends visible in the public uptake of Copernicus Sentinel data. This is the eighth such report released by the data access service provider, Serco Italia SpA.
This year ESA has decided to align the reporting year with the calendar year, in order to coincide better with the reporting needs of the European Commission. Whereas in previous years the annual report covered the period 1 December to 30 November, therefore, this year the reporting year runs from 1 January 2022 to 31 December 2022.
As a result, statistics for the month of December 2021 are not included in the figures for the year 2022. They are, however, included in all cumulative statistics, unless explicitly stated otherwise.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Data Access System operated by ESA during the year 1 December 2020 to 30 November 2021 (referred to throughout this report as ‘Y2021’), and analyses the trends visible in the public uptake of Copernicus Sentinel data.
This is the sixth such report released by the data access service provider, Serco Italia SpA.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Sentinel Data Access System operated by ESA during the year 1 December 2019 to 30 November 2020 (referred to throughout this report as ‘Y2020’), and analyses the trends visible in the public uptake of Copernicus Sentinel data.
This is the sixth such report released by the data access service provider, Serco Italia SpA.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Data Access System operated by ESA during the year 1 December 2018 to 30 November 2019 (referred to throughout this report as ‘Y2019’), and analyses the trends visible in the public uptake of Copernicus Sentinel data.
This is the fifth such report released by the data access service provider, Serco Italia SpA.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by the Serco Gael consortium for ESA as part of the Copernicus programme.
This Annual Report presents the performance of the Copernicus Data Access System operated by ESA during the year 1 December 2017 to 30 November 2018 (Y2018), and analyses the trends visible in the public uptake of Copernicus Sentinel data.
This is the fourth such report released by the data access service provider, Serco SpA, and covers a year in which a significant milestone was reached: following the successful launches of Sentinel-5P on 13 October 2017 and Sentinel-3B on 25 April 2018, the full set of seven Copernicus Sentinel satellites
(Sentinels-1, -2, -3 A&B and -5P) which the Data Access System was designed to serve were in orbit and their data was being made available to the public on a systematic basis.
The Sentinel Data Access Annual Report 2016 is a deliverable of the “Sentinels Rolling Archive User Access, Operations, Maintenance and Evolutions” contract (n.: 4000116830/16/I-BG) between the European Space Agency (ESA) and the consortium led by Serco S.p.A as Prime Contractor.
This document provides an annual report of the Sentinel Data Access Service operated by the consortium as part of the Copernicus programme.
On 27 April 2016, the data access service provider Serco SpA released an annual report, analysing the performance of the Data Access System since the start of operations and public uptake of Copernicus Sentinel data1.
This 2016 annual report takes up from where the 2015 report left off, and tracks the system’s performance and user activity during the period 1 December 2015 to 30 November 2016. Throughout this document, Y2016 will be used to refer to the current reporting period of 1 December 2015 to 30 November 2016; and
Y2015 will be used to refer to the previous reporting period of 3 October 2014 to 30 November 2015.
A deliverable of the Sentinels Rolling Archive, Operations Maintenance and Evolution contract, this document provides an annual look at the Sentinel Data Access Service operated by Serco, Gael, NOA and GRNET consortium for ESA in the Copernicus programme.
The current annual report is the third such report released by the data access service provider, Serco SpA, analysing the performance of the Data Access System and the public uptake of Copernicus Sentinel data.
This 2017 annual report takes up from where the 2016 report left off, and tracks the system’s performance and user activity during the period 1 December 2016 to 30 November 2017.
This document describes the Environmental Sustainability activities to be undertaken and the deliverables required by the European Space Agency (“ESA” or the “Agency”) in relation to the delivery of the Service.
There is a need to understand, measure and reduce the environmental footprint of ESA’s activities. ESA’s Agenda 2025 sets the objectives of reducing the Agency’s greenhouse gases emissions by 28% by 2030 for downstream activities (Scope 3) compared to 2019.
This also supports the goal to reach European climate neutrality by 2050, by cooperating on activities contributing to this target, such as assessing the footprint of the activities implemented in the Service, avoiding and reducing emissions of greenhouse gas, switching to green electricity, implementing best environmental practices, promoting environmentally friendly technologies and supporting innovation. The European Climate Law writes into law the goal set out in the European Green Deal for Europe’s economy and society to achieve climate-neutrality by 2050. The law also sets the intermediate target of reducing net greenhouse gas emissions by at least 55% by 2030, compared to 1990 levels.
The European Commission applies a policy of continuous improvement of its environmental impacts through EMAS (Environmental Management and Audit Scheme).