Deliverables

D 1.1 Management Report

The project passed M1 and M2 reaching Pilot status and progressing towards Full software and service deployment. Results of project-related activities have been presented at major conferences, workshops and events in the field of Earth Science.

Overall progress is in line with DoA, the project is well on track. All partners advanced in the planned work plan and contributing to the project advancement.

D 1.2 Management Report

The EarthServer-2 project reached its end on April 30th, 2018. The three-year H2020 project, building on its FP7 predecessor EarthServer advanced substantially. Three milestones were passed, with incremental updates of both software backend and services through respectively Pilot, Full and Consolidate stages. The progress at project end is in line with DoA.

D 2.1 Requirements Analysis Report

This Requirements Analysis Report summarises the identified requirements to implement and operate successfully these spatial-temporal Big Data Analytics services for a wide range of stakeholders. These stakeholders represent today’s major scientific domains, which are challenged by overly large volumes of geospatial data. These include the Earth-Observation, Climate/Meteorology, Marine and Planetary domains. The stakeholders require services that involve usage, deployment and administration of this data.

D 2.2 Data Management Plan

This document will set out the Data Management Plan (DMP) for the EarthServer-2 project. The DMP will include a data register which will be maintained as a “live” document and updated as new data become available to the project. Periodic iterations of the DMP will be produced, providing a snapshot of the latest data register.

D 2.4 Initial Deployment Report

This document outlines the current state of the project’s partner’s data services. This includes the version of the rasdaman software that has been installed as well as the operating system used. All partners now have a running instance of rasdaman with published endpoints. The installations include both Community Edition and Enterprise versions of rasdaman.

D 3.1 Development Report - Pilot

This development report is the first of a series of documents that will be produced in the context of the WP3 work package. This document summarises the achievements and the progress made on tasks in WP3. Development is set within the context of the requirements set by the service partners in the WP4 work package and advances the EarthServer platform, rasdaman, in terms of functionality, scalability and usability.

D 3.2 Development Report - Full

This development report is the second document produced in the context of the WP3 work package. It summarises the achievements and the progress made on tasks in WP3 during the last period. Development is set within the context of the requirements set by the service partners in the WP4 work package and advances the EarthServer platform, rasdaman, and the xWCPS language in terms of functionality, scalability and usability.

D 3.3 Development Report - Full

This report summarises all the developments and the progress that took place between M3 and M4 and documents the enhancements and additional functionality to the previously reported work of WP3, described in detail in the D3.2 report.

D 4.1 Service Operation Report - Pilot

This document outlines the domain specific data services created during the EarthServer-2 project utilizing the underlying software stack are being created. The services span multiple scientific domains. Plymouth Marine Laboratory (PML) has created the Marine Science Data Service, European Centre for Medium-Range Weather Forecasts (ECMWF) has created the Climate Science Data Service, Meteorological Environmentas Earth Observation (MEEO) has created the Earth Observation Data Service, Jacobs University Bremen has created the Planetary Data Service.

D 4.2. Data Management Plan – Update 1

This document sets out the Data Management Plan (DMP) for the EarthServer-2 project. The DMP includes a data register that will be maintained as a “live” document and updated as new data become available to the project. Periodic iterations of the DMP will be produced, providing a snapshot of the latest data register.