This document presents CURE stakeholder needs and requirements to shape the development of CURE cross-cutting applications.
This deliverable is informed by state-of-the-art specifications of user requirements in urban resilience and spatial planning,
supported by general requirements from a wider stakeholder group, all providing prime focus on requirements gathering from the
CURE front-runner pilot cities. The aims here are to: a) identify various user needs and requirements to develop an understanding
of different user expectations of Copernicus based data, and b) to identify commonalities that can be useful for the development of
generic products applied to other European cities.
This document provides a comprehensive review of existing Copernicus services, with main focus on CAMS (Copernicus Atmosphere Monitoring Service),
CLMS (Copernicus Land Monitoring Service), C3S (Copernicus Climate Change Service) and EMS (Emergency Management Service). In particular, key information
is collected for each service product in terms of scope/variables, spatial and temporal extent, spatial and temporal resolution and update frequency, along
with a link to the source webpage. Given the vast number of products, to ease the browsing, the collection is organized in four different spreadsheets (*.xlsx),
to each of the abovementioned services.
This document provides a review of current methodologies, which can be of use in the implementation of the proof-of-concept / prototype
(as well as for benchmarking activities) for each intended CURE application. Here, major focus is given to previous FP7 and H2020 projects,
especially those addressing urban resilience topics.
This document presents a consolidated summary of CURE cross-cutting applications data needs and describes the CURE
Interface concept to be implemented as part of the CURE services automation. It is based on detailed analysis of stakeholder
needs and requirements, further reflecting these findings and providing detailed guidance both on: a) content side, providing
detailed specification of each relevant data source for each particular CURE application implementation for particular front-runner
pilot cities; and b) technical side, outlining concept of CURE Interface providing support by means of automation of insertion of data
resources needed by each CURE application.
This document presents a technical description of the CURE Copernicus Core Services Interface (CCSI) and its implementation.
The aim of this development activity is to provide a unified interface to streamline search and locate Copernicus services
products and other resources as requested by CURE cross-cutting applications. This will help to automate the process of data
input into CURE applications and the CURE System, which will significantly enhance their replication potential for the future.
The CCSI is stored in this GitHub repository: https://github.com/gisat/cure_core_interface, and it
will constantly be updated in order to allow the efficient development of the CURE System.
This document aims to describe in more detail the CURE cross-cutting applications and to summarize the preparatory
activities for the individual applications development, following the first description in Methodology Review and
Selection Deliverable (D1.3). The purpose of each CURE application, the data and methodology used, as well as the
output features and characteristics are presented. Preliminary results of some applications for the front-runner
cities are demonstrated, where possible, and feedback is provided on the stakeholder needs, as identified in Summary
of User Requirements Deliverable (D1.1).
This document focuses on the aspects of the services that are relevant to a potential uptake of the CURE System
in the Copernicus architecture. In the context of this Deliverable, a) the structure of Copernicus is analysed,
aiming at elements defining a typical Copernicus service; b) the current status of the CURE applications is assessed
in light of the elements required for uptake as a Copernicus service; and c) a pathway is presented towards a mature
CURE service portfolio that would fit perfectly in the Copernicus program through 3 alternative scenarios.
This document contains information required for the management of all data and products to be collected and generated
during the project. The document outlines, how data will be handled during the CURE implementation phase and after it;
describing the kind of data to be collected, processed or generated, the standards to be followed and their compliance
with FAIR principles (Findable, Accessible, Interoperable and Re-usable). A sound data management is pivotal for fully
realising CURE, as well as for allowing the wider research and user communities to access and further assess the project achievements.