Explore the words cloud of the openEO project. It provides you a very rough idea of what is the project "openEO" about.
The following table provides information about the project.
Coordinator |
TECHNISCHE UNIVERSITAET WIEN
Organization address contact info |
Coordinator Country | Austria [AT] |
Project website | http://openeo.org/ |
Total cost | 1˙989˙001 € |
EC max contribution | 1˙989˙001 € (100%) |
Programme |
1. H2020-EU.2.1.6.3. (Enabling exploitation of space data) 2. H2020-EU.2.1.6.1.2. (Boost innovation between space and non-space sectors) |
Code Call | H2020-EO-2017 |
Funding Scheme | RIA |
Starting year | 2017 |
Duration (year-month-day) | from 2017-10-01 to 2020-09-30 |
Take a look of project's partnership.
# | ||||
---|---|---|---|---|
1 | TECHNISCHE UNIVERSITAET WIEN | AT (WIEN) | coordinator | 388˙981.00 |
2 | WESTFAELISCHE WILHELMS-UNIVERSITAET MUENSTER | DE (MUENSTER) | participant | 359˙977.00 |
3 | VLAAMSE INSTELLING VOOR TECHNOLOGISCH ONDERZOEK N.V. | BE (MOL) | participant | 339˙992.00 |
4 | WAGENINGEN UNIVERSITY | NL (WAGENINGEN) | participant | 319˙993.00 |
5 | EODC EARTH OBSERVATION DATA CENTREFOR WATER RESOURCES MONITORING GMBH | AT (WIEN) | participant | 200˙015.00 |
6 | MUNDIALIS GMBH & CO KG | DE (BONN) | participant | 90˙016.00 |
7 | SINERGISE LABORATORIJ ZA GEOGRAFSKEINFORMACIJSKE SISTEME DOO | SI (LJUBLJANA) | participant | 80˙027.00 |
8 | ACCADEMIA EUROPEA DI BOLZANO | IT (BOLZANO) | participant | 80˙010.00 |
9 | SOLENIX SCHWEIZ GMBH | CH (HARKINGEN) | participant | 79˙988.00 |
10 | JRC -JOINT RESEARCH CENTRE- EUROPEAN COMMISSION | BE (BRUSSELS) | participant | 49˙998.00 |
The capabilities of the latest generation of Earth observation satellites to collect large volumes of diverse and thematically rich data are unprecedented. For exploiting these valuable data sets, many research and industry groups have started to shift their processing into the cloud. Although the functionalities of existing cloud computing solutions largely overlap, there are all custom-made and tailored to the specific data infrastructures. This lack of standards not only makes it hard for end users and application developers to develop generic front-ends, but also to compare the cloud offerings by running the same analysis against different cloud back-ends. To solve this, a common interface that allows end- and intermediate users to query cloud-based back offices and carry out computations on them in a simple way is needed. The openEO project will design such an interface, implement it as an open source community project, bind it to generic analytics front-ends and evaluate it against a set of relevant Earth observation cloud back offices. The openEO interface will consist of three layers of Application Programming Interfaces, namely a core API for finding, accessing, and processing large datasets, a driver APIs to connect to back offices operated by European and worldwide industry, and client APIs for analysing these datasets using R, Python and JavaScript. To demonstrate the capability of the openEO interface, four use cases based chiefly on Sentinel-1 and Sentinel-2 time series will be implemented. openEO will simplify the use of cloud-based processing engines, allow switching between cloud-based back office providers and comparing them, and enable reproducible, open Earth observation science. Thereby, openEO reduces the entry barriers for the adaptation of cloud computing technologies by a broad user community and paves the way for the federation of infrastructure capabilities.
Data Warehouse request 2019 | Documents, reports | 2020-03-06 18:34:20 |
Hackathon report | Documents, reports | 2020-03-06 18:34:20 |
Proof of Concept (Python) | Demonstrators, pilots, prototypes | 2020-03-06 18:34:20 |
Overview document about back offices metadata standards and interfaces | Documents, reports | 2020-03-06 18:34:20 |
Report assessing back-end driver variability | Documents, reports | 2020-03-06 18:34:20 |
Two early prototype back-ends (file-based, SciDB) | Demonstrators, pilots, prototypes | 2020-03-06 18:34:20 |
openEO core API prototype including Proof of Concept | Demonstrators, pilots, prototypes | 2020-03-06 18:34:20 |
Data Warehouse use 2018 | Documents, reports | 2020-03-06 18:34:20 |
Preliminary User Requirements report (incl. Use Case Workshop report 1) | Documents, reports | 2020-03-06 18:34:20 |
Operative online dissemination portals (website, social media, GitHub) | Websites, patent fillings, videos etc. | 2020-03-06 18:34:20 |
First overview of needed processes from use cases | Documents, reports | 2020-03-06 18:34:20 |
openEO architecture specification, first version | Documents, reports | 2020-03-06 18:34:20 |
Take a look to the deliverables list in detail: detailed list of openEO deliverables.
year | authors and title | journal | last update |
---|---|---|---|
2017 |
Pebesma, Edzer; Wagner, Wolfgang; Schramm, Matthias; Von Beringe, Alexandra; Paulik, Christoph; Neteler, Markus; Reiche, Johannes; Verbesselt, Jan; Dries, Jeroen; Goor, Erwin; Mistelbauer, Thomas; Briese, Christian; Notarnicola, Claudia; Monsorno, Roberto; Marin, Carlo; Jacob, Alexander; Kempeneers, Pieter; Soille, Pierre OpenEO - a Common, Open Source Interface Between Earth Observation Data Infrastructures and Front-End Applications published pages: , ISSN: , DOI: 10.5281/zenodo.1065474 |
2020-03-06 | |
2018 |
Pebesma, Edzer; Mohr, Matthias; Dries, Jeroen; Schramm, Matthias; Wagner, Wolfgang; Verbesselt, Jan; Briese, Christian openEO D04: core API prototype including Proof of Concept published pages: , ISSN: , DOI: 10.5281/zenodo.2540674 |
2020-03-06 | |
2018 |
Busch, Gunnar; Dries, Jeroen; Briese, Christian; Wagner, Wolfgang; Verbesselt, Jan; Pebesma, Edzer; Mistelbauer, Thomas; Foresta, Luca; Mohr, Matthias; Voumard, Yann; Schramm, Matthias; Ng, Tim openEO D10: Hackathon report published pages: , ISSN: , DOI: 10.5281/zenodo.2542824 |
2020-03-06 | |
2018 |
Miksa, Tomasz; Wagner, Wolfgang; Gößwein, Bernhard; Pebesma, Edzer; Mohr, Matthias; Dries, Jeroen; Schramm, Matthias; Briese, Christian openEO D13: openEO architecture specification, first version published pages: , ISSN: , DOI: 10.5281/zenodo.2542829 |
2020-03-06 | |
2018 |
Pebesma, Edzer; Jacob, Alexander; Dries, Jeroen; Briese, Christian; Wagner, Wolfgang; Neteler, Markus; Kadunc, Miha; Mohr, Matthias; Schramm, Matthias openEO D05: Overview document about back offices metadata standards and interfaces published pages: , ISSN: , DOI: 10.5281/zenodo.2540684 |
2020-03-06 | |
2017 |
Pebesma, Edzer; Schramm, Matthias; von Beringe, Alexandra; Wagner, Wolfgang openEO D03: Operative online dissemination portals published pages: , ISSN: , DOI: 10.5281/zenodo.2540663 |
2020-03-06 | |
2018 |
Briese, Christian; Neteler, Markus; Dries, Jeroen; Kadunc, Miha; Jacob, Alexander; Pebesma, Edzer; Wagner, Wolfgang; Busch, Gunnar; Mistelbauer, Thomas; Foresta, Luca; Mohr, Matthias; Schramm, Matthias; Lahn, Florian; Ng, Tim openEO D14: Report assessing back-end driver variability published pages: , ISSN: , DOI: 10.5281/zenodo.2542830 |
2020-03-06 | |
2018 |
Carter, Sarah; Verbesselt, Jan; Dostalova, Alena; Wagner, Wolfgang; Schramm, Matthias; Mohr, Matthias openEO D08: Preliminary User Requirements report published pages: , ISSN: , DOI: 10.5281/zenodo.2542805 |
2020-03-06 | |
2018 |
Dries, Jeroen; Gößwein, Bernhard; Wagner, Wolfgang; Schramm, Matthias; Pebesma, Edzer; Masiliunas, Dainius; Verbesselt, Jan openEO D07: Proof of Concept (Python) published pages: , ISSN: , DOI: 10.5281/zenodo.2542792 |
2020-03-06 | |
2018 |
Schramm, Matthias; Wagner, Wolfgang; Jacob, Alexander; Dries, Jeroen; Dostalova, Alena; Carter, Sarah; Verbesselt, Jan; Neteler, Markus openEO D09: First overview of needed processes from use cases published pages: , ISSN: , DOI: 10.5281/zenodo.2542822 |
2020-03-06 | |
2018 |
Busch, Gunnar; Briese, Christian; Jacob, Alexander; Kadunc, Miha; Dries, Jeroen; Neteler, Markus; Wagner, Wolfgang; Mohr, Matthias; Lahn, Florian; Pebesma, Edzer; Schramm, Matthias openEO D06: Two early prototype back-ends published pages: , ISSN: , DOI: 10.5281/zenodo.2540697 |
2020-03-06 |
Are you the coordinator (or a participant) of this project? Plaese send me more information about the "OPENEO" project.
For instance: the website url (it has not provided by EU-opendata yet), the logo, a more detailed description of the project (in plain text as a rtf file or a word file), some pictures (as picture files, not embedded into any word file), twitter account, linkedin page, etc.
Send me an email (fabio@fabiodisconzi.com) and I put them in your project's page as son as possible.
Thanks. And then put a link of this page into your project's website.
The information about "OPENEO" are provided by the European Opendata Portal: CORDIS opendata.