This document is the first release of the report describing the elements needed to design the Pilots of SDGsEYES, in practice those requirements identified to start feeding the platform and tools’ design in WP4. After briefly recalling – as summarized from Deliverable D3.1 (Copernicus Datasets and Algorithm Theoretical Basis Documentation) and also according the initial user requirements (described in Deliverable D2.2) – the context of SDGs’ indicators addressed, their state-of-the-art methodologies, and the expected improvements in data and/or methods, here the Pilots’ needs in terms of data, possible preparation and processing steps, and results presentation to end-users are described, taking into consideration the top-down (science-driven) side, waiting for more in-depth engagement of stakeholders through WP2 (bottom-up approach -user driven under co-design).

SDGs-EYES has five Pilots that cover seven SDGs indicators in the biosphere realm (SDG13, SDG14, SDG15). Information to describe requirements to conduct these Pilots have been collected among Pilots’ (co-)leaders, via a survey, facilitated by tabular format, and they will remain internally available as “in progress” documentation and possibly released as Supplementary Material in the second and final version of this Deliverable at month 18 (M18). At this stage, in particular the possible datasets to feed indicators calculation algorithms were screened. Extended information on these datasets is in the survey tables while in this Deliverable the main aspects regarding formats and ways to access are reported. In total 72 datasets were considered valuable for now, 30 from Copernicus-related sources, 30 from other authoritative international portals, 12 from national archives for the Pilot domain countries (Romani and Italy). Not all of these datasets will be direct input to algorithms, this will depend on information soon examined about their resolution, accuracy, quality evaluation: some will serve as complementary information to extend periods of availability or to fill gaps for example, some other will act as reference dataset for validation or cross-comparison.

More indicative is, for now inevitably, information on data preparation, as for example the final Area of Interest (AoIs) need to be confirmed in some cases or the availability of a few additional datasets is under confirmation. For the processing steps, the review of the most appropriate and promising algorithms is ongoing in WP3, so that high-level processing has been for now identified. The same applies for the ways in which the results can be made available to end-users, whose preferences will be investigated in the next period in cooperation with WP2.

Finally, Deliverable tried to identify common steps in the Pilot conduction that will be monitored in Task 5.2.

In case you are interested to learn more about the report, please contact us.