publications

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 6.2 Networking Report - Pilot

Between August 2016 and June 2017, individual project partners and the EarthServer-2 consortium as a whole were involved in multiple outreach activities to reach domain-specific audiences, policymakers, industry experts and the general public. Dissemination of EarthServer-2 project activities as well as the exploitation of project results play an integral part to increase the project’s impact and to disseminate project outcomes.

D 5.2 Standardization Report - Full

EarthServer-2 WP5 addresses “datacube” standardization in relevant bodies and, additionally, outreach work in the Research Data Alliance (RDA). 

In this report, we summarize progress made in the reporting period from M2 (August 2016) through M3 (June 2017). During this period spanning about one year Earth-Server-2 standardization work has led continued producing significant and inter¬nat-ion¬ally visible results in OGC, ISO, and INSPIRE. Also in RDA substantial and visible results have been accomplished. 

D 4.4 Data Management Plan – Update 2

Data management is a major focus of the EarthServer-2 project, which addresses problems such as searching, filtering and analyzing huge (100TB+) datasets that, due to their size, cannot be processed on the client side. The tools and standards developed during EarthServer-2 will improve the accessibility and reuse of these datasets.

D 4.3 Service Operation Report - Full

Service development is an integral part of the EarthServer-2 project, as services implement the Rasdaman technology for a specific scientific community, give feedback to advance the software, gather user and domain-specific requirements of web services in general and do outreach to promote project outcomes. A total of four main services are being developed during the EarthServer-2 project. The services span multiple scientific domains.

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.

The EarthServer Federation: State, Role, and Contribution to GEOSS

The intercontinental EarthServer initiative has established a European datacube platform with proven scalability: known databases exceed 100 TB, and single queries have been split across more than 1,000 cloud nodes. Its service interface being rigorously based on the OGC "Big Geo Data" standards, Web Coverage Service (WCS) and Web Coverage Processing Service (WCPS), a series of clients can dock into the services, ranging from open-source OpenLayers and QGIS over open-source NASA WorldWind to proprietary ESRI ArcGIS.

Datacubes as a Service Paradigm

Spatio-temporal data sets often can be represented conveniently through datacubes as a common unifying paradigm. Flexible, scalable services can be offered based on the concept of a datacube query language while hiding the technicalities, thereby allowing user-friendly visual data interaction.

EarthServer: the Global Datacube Federation

One of today's most influential initiatives in Big Geo Data is EarthServer which is paving the way for flexible, scalable datacube services based on innovative NewSQL technology. Researchers from Europe, the US and recently Australia have teamed up to rigorously materialize the datacube paradigm for Earth Observation, ocean, meteorological, and planetary science.

"Science SQL" as a Building Block for Flexible, Standards-based Data Infrastructures

We have learnt to live with the pain of separating data and metadata into non-interoperable silos. For metadata, we enjoy the flexibility of databases, be they relational, graph, or some other NoSQL. Contrasting this, users still "drown in files" as an unstructured, low-level archiving paradigm. It is time to bridge this chasm which once was technologically induced, but today can be overcome.

Pages