You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For products generated in the framework of the Copernicus earth observation programme, ESA requires the generation of so-called "traces", which document generation time, processing site, consistency information and other product metadata depending on a mission's specific requirement.
While the content of a trace is inherently mission-dependent, the interface as such is mission-independent. It is therefore proposed to create a generic client API implementation for the Copernicus Data Space Ecosystem (CDSE) Traceability Service as documented in the CDSE Traceability Service ICD [CDSE-TRC-TSY] (last known issue: 1.2, 2024-09-20).
The text was updated successfully, but these errors were encountered:
For products generated in the framework of the Copernicus earth observation programme, ESA requires the generation of so-called "traces", which document generation time, processing site, consistency information and other product metadata depending on a mission's specific requirement.
While the content of a trace is inherently mission-dependent, the interface as such is mission-independent. It is therefore proposed to create a generic client API implementation for the Copernicus Data Space Ecosystem (CDSE) Traceability Service as documented in the CDSE Traceability Service ICD [CDSE-TRC-TSY] (last known issue: 1.2, 2024-09-20).
The text was updated successfully, but these errors were encountered: