All developed software is organized within the openEO GitHub organization.
Software that allows remote sensers and other users to access the openEO back-ends:
|Client software||Package Manager / Hosted Version||GitHub|
|Python library||PyPI: openeo||openeo-python-client|
|QGIS plugin||QGIS plugin repository: openeo-qgis-plugin-master||openeo-qgis-plugin|
|R library||CRAN: Not available yet||openeo-r-client|
|Web Editor||Hosted Version||openeo-web-editor|
Data and infrastructure providers can host their own instance of the openEO API:
- GeoPySpark (Geotrellis) (by VITO) - has integration tests, requires GeoTrellis extensions.
- Google Earth Engine (by WWU)
- GRASS GIS (by mundialis)
- JEODPP (by JRC)
- OpenDataCube (by EURAC, funded by ESA)
- RedHat OpenShift Origin (by EODC)
- Sentinel Hub (by Sinergise)
- WCPS (rasdaman) (by EURAC)
- R back-end (by WWU) - discontinued until further notice (last version: 0.3)
See the getting started guide for back-end providers for more information.
To start developing a new back-end driver, you may start with any of the common functionalities implemented in several programming languages:
- Java (Spring) API Commons
- Python API Commons
- Python Process Graph Parser
- Python Processes - many openEO processes implemented in Python
Our approach to tackle language-agnostic user-defined functions can be found in the following repositories:
- Back-end validator - Validation for back-end implementations. Image-based validation of EO processing results is also worked on.
- openEO Hub (GitHub) - The central platform for openEO services.
- Processes DocGen - A tool to generate a visual interface for openEO process definitions.
- Vue.js Components - Common Vue.js 2 components for openEO