We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Implementing an openEO compliant back-end for processing data cubes on the JEODPP

Formal Metadata

Title
Implementing an openEO compliant back-end for processing data cubes on the JEODPP
Title of Series
Number of Parts
295
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Funded be the European Commission as a H2020 project, openEO aims for a new web service standard to process Earth Observation data cubes. At its core, openEO provides an http application programming interface (API) that defines how users can discover Earth observation data cubes and process them on compliant cloud back-ends. The back-ends run their own API instance, translating the http requests to their environment. The front end API implementation can serve different languages (R, Python, Javascript) on the client side. The openEO project has foreseen that APIs are implemented with an open source license (Apache 2.0). A number of back-ends are already available that are compatible with this suggested openEO standard. For instance, within the Joint Research Centre (JRC) of the European Commission, an API implemented in Python is being developed that can discover and process geospatial data collections available in the JRC Earth Observation Data and Processing Platform (JEODPP). For the back-end, an in-house library is being developed under the European Union Public Licence (EUPL). In this presentation, we will highlight the openEO concepts and focus in particular on the JRC back-end implementation details.
Keywords