Embedded Files
Integration with Copernicus
We will establish the interface between the RemoTrees platform and Copernicus Services, in particular with the in-situ component and the Copernicus Land GBOV (Ground Based Observation for Validation) service, as well as with the CEOS land product validation community.
We will establish the interface between the RemoTrees platform and Copernicus Services, in particular with the in-situ component and the Copernicus Land GBOV (Ground Based Observation for Validation) service, as well as with the CEOS land product validation community.
Calibration and Validation activities of Copernicus Land Vegetation Products are based on a wide range of in-situ monitoring networks. However, some spatial and temporal requirements for in-situ data are still not fully achieved, particularly over hard-to-reach areas. Compared to the existing initiatives and networks for in-situ validation, the RemoTrees would imply an order of magnitude lower costs for site infrastructures, while filling current existing geographical gaps in key environmental areas.
Calibration and Validation activities of Copernicus Land Vegetation Products are based on a wide range of in-situ monitoring networks. However, some spatial and temporal requirements for in-situ data are still not fully achieved, particularly over hard-to-reach areas. Compared to the existing initiatives and networks for in-situ validation, the RemoTrees would imply an order of magnitude lower costs for site infrastructures, while filling current existing geographical gaps in key environmental areas.
We will customise the RemoTrees data to fit the Copernicus calibration and validation needs. Furthermore, we will upscale TT raw data to generate ground-based vegetation products using Sentinel-2 data and advance calibration methods in the RemoteTrees network. Lastly, we will carry out a test-delivery of the customised in-situ RemoTrees data to the Copernicus Services and the international land product validation community.
We will customise the RemoTrees data to fit the Copernicus calibration and validation needs. Furthermore, we will upscale TT raw data to generate ground-based vegetation products using Sentinel-2 data and advance calibration methods in the RemoteTrees network. Lastly, we will carry out a test-delivery of the customised in-situ RemoTrees data to the Copernicus Services and the international land product validation community.
Progress Update (June 2025, Month 18 of the Project)
Progress Update (June 2025, Month 18 of the Project)
During the first reporting period, the requirements for in-situ observations in the Copernicus context as well as in the other Calibration/Validation initiatives has been reviewed. The work performed included:
During the first reporting period, the requirements for in-situ observations in the Copernicus context as well as in the other Calibration/Validation initiatives has been reviewed. The work performed included:
Analysis of existing satellite-based remote sensing products and their validation needs.
Analysis of existing satellite-based remote sensing products and their validation needs.
Our analysis indicated that these satellite-based products can benefit from RemoTrees observations related to LAI, fAPAR, soil moisture (SM), and albedo. We compiled actions of the Global Climate Observing System (GCOS) Implementation Plan related to in-situ observations of land Essential Climate Variables, which are partly addressed by RemoTrees.
Our analysis indicated that these satellite-based products can benefit from RemoTrees observations related to LAI, fAPAR, soil moisture (SM), and albedo. We compiled actions of the Global Climate Observing System (GCOS) Implementation Plan related to in-situ observations of land Essential Climate Variables, which are partly addressed by RemoTrees.
Generic requirements for in-situ observations
Generic requirements for in-situ observations
We identified requirements for in-situ observations coming from ecosystem networks (e.g., ICOS, TERN, NEON), as well as best practices from baseline GCOS in-situ networks. These include specifications on data description, metadata, measurement protocols, traceability, uncertainty, quality control, data formats, data access, and accessibility.
We identified requirements for in-situ observations coming from ecosystem networks (e.g., ICOS, TERN, NEON), as well as best practices from baseline GCOS in-situ networks. These include specifications on data description, metadata, measurement protocols, traceability, uncertainty, quality control, data formats, data access, and accessibility.
Requirements for the Copernicus in-situ component
Requirements for the Copernicus in-situ component
We identified requirements for the Copernicus in-situ component, including those related to horizontal resolution, timeliness, and update frequency; however, no requirement was established for uncertainty. The approach to engaging with the Copernicus in-situ component was evaluated, and a dialogue with Copernicus in-situ has been initiated.
We identified requirements for the Copernicus in-situ component, including those related to horizontal resolution, timeliness, and update frequency; however, no requirement was established for uncertainty. The approach to engaging with the Copernicus in-situ component was evaluated, and a dialogue with Copernicus in-situ has been initiated.
Diagram of the Copernicus In-Situ component and Entrusted Entities. EEA coordinates the In-Situ component.
Diagram of the Copernicus In-Situ component and Entrusted Entities. EEA coordinates the In-Situ component.
Requirements for the Copernicus Ground-Based Observations for Validation (GBOV)
Requirements for the Copernicus Ground-Based Observations for Validation (GBOV)
We identified requirements for the Copernicus GBOV component based on the disseminated datasets, including data definitions, metadata information, data formats, and upscaling procedures. It is important to note that GBOV is an operational service based on long-term monitoring sites. RemoTrees data will be customized to GBOV specifications, including upscaling procedures.
We identified requirements for the Copernicus GBOV component based on the disseminated datasets, including data definitions, metadata information, data formats, and upscaling procedures. It is important to note that GBOV is an operational service based on long-term monitoring sites. RemoTrees data will be customized to GBOV specifications, including upscaling procedures.
Requirements of the international Calibration/Validation community
Requirements of the international Calibration/Validation community
We compiled requirements of the international Calibration/Validation community, including those from the CEOS WGCV Land Product Validation Subgroup related to data collection, as well as broader requirements to meet CEOS Fiducial Reference Measurement (FRM) standards. These include, among others, traceability, uncertainty, documented protocols, representativeness, accessibility, and utility. We also defined the approach to engaging with the Cal/Val community.
We compiled requirements of the international Calibration/Validation community, including those from the CEOS WGCV Land Product Validation Subgroup related to data collection, as well as broader requirements to meet CEOS Fiducial Reference Measurement (FRM) standards. These include, among others, traceability, uncertainty, documented protocols, representativeness, accessibility, and utility. We also defined the approach to engaging with the Cal/Val community.
Lead
Fernando Camacho
Fernando Camacho
EOLAB
Contact: fernando.camacho@eolab.es
Page updated
Report abuse