A summary of the work performed and results achieved per work package is given below:
WP1: Project and innovation management
- Set-up and coordination of a project advisory board
- Establishment of an innovation management roadmap for exploitation of the project’s results, including the continuous dialogue with the Entrusted Entities and various Copernicus Data and Information Access Service (DIAS) providers.
WP2: Platform services and operations
- Establishment of an App Lab cloud architecture supporting operational deployment scenarios of the docker-based AppLab back-end components, to be operated on one or more DIAS.
- DAP deployment for CGLS data products also tested and benchmarked on DIAS providers, to prepare the App Lab consortium with the management of failover and Content Delivery Network optimizations. Measured performance is on-par compared to commercial Cloud infrastructure providers.
- Cost-benefit analysis on DAP implementation for CGLS as well as user uptake statistics showing popularity of CGLS products, and of the Leaf Area Index in particular.
WP3: Tools for enhancing, cataloguing, and publishing geospatial data-streams from the Copernicus Services
- +40 Copernicus services datasets have been semantically-enriched, published on the Streaming Data Library (SDL) and made available as linked data.
- Published online facilities to explore and discover datasets
- Published the App Lab Analytics SDK providing downstream service providers with a broad range of analytical functions in creating added-value products (e.g. enabling on-the-fly spatial and temporal aggregations or the execution of advanced analytical functions, such as anomaly detection, detect (the strength of) correlations between raw Copernicus data, etc.).
- Created several use cases, illustrating the use of raw Copernicus data as well as (derived) added-value products for societal relevant benefit areas (e.g. city marketing, ballast water management, etc.).
- Published VISual and RESTful Maps-APIs for popular Mobile App Developer-frameworks (e.g. Android, iOS, JavaScript, Node.js) to obtain (derived) datasets. Also, the linked data tools of WP4 have been integrated such that developers can seamlessly consume subsets of relevant Copernicus data as LOD.
WP4: Tools for linked EO data
- Constructed ontologies to convert Copernicus data in the RDF model
- Converted Copernicus Services data into linked EO data and interlinking them with other open geospatial data
- Created (GeoSPARQL) endpoints so that EO data can be accessed as linked data using Web standards. These endpoints also contain other relevant linked geospatial data (e.g. administrative boundaries, OpenStreetMap data) so that users can pose enriched queries against the combination of these datasets
- Search engines like Google have been enabled to treat datasets produced by Copernicus as “entities” in their own right and store knowledge about them in their internal knowledge graph.
WP5: Dissemination and user uptake
- Created and implemented a communication plan (incl. CI, project logo, website, press releases, flyers, mailings, social media etc.)
- Organised beta-testing activities such as user engagement during ESA Space App Camp 2017 and 2018, ActInSpace Hackathon 2018, Phi-Week 2018 and other workshops and paper presentations. In addition feedback was gathered via an online beta testing phase and through the engagement of LOD experts.
- Validated the feedback received, leading to further evolvements and improvements of the platform.
- Extensive outreach and dissemination: 30 conference presentations and workshops, 9 scientific papers published and almost 40 media and other online publications.
