The openEO (core) API is currently released in version 0.3.
Note: The specification is currently still an early version, with the potential for some major things to change. The core is now fleshed out, so implementors are encouraged to try it out and give feedback. But the goal is to actually be able to act on that feedback, which will mean changes are quite possible. A solid basis is specified right now, but best practices, extensions and specification details will emerge with implementation.
|Version / Branch||Status||Description|
|0.0.1 (Spec)||legacy||First draft with basic ideas, loosely implemented.|
|0.0.2 (Spec)||legacy||Proof of concept, implemented.|
|0.3.0 (Spec)||current||Currently in implementation by clients and back-ends. Major rework.|
|0.3.1 (Spec)||planned||Fixing minor issues, see the changelog.|
|0.4.0 (Spec)||planned||Planned to add data set and process descriptions and an extension concept.|
See also the milestones for a rough roadmap based on GitHub issues.
This repository contains a set of files formally and technically describing the openEO API, each with a human-readable and easily browseable version:
- openapi.json (browseable version) provides the openAPI 3.0 definition of the openEO API.
- processes.json (browseable version) defines pre-defined core processes back-ends may implement for best interoperability.
- subscriptions.json (browseable version) provides the AsyncAPI 1.2 definitions for the WebSocket-based subscriptions and notifications API for openEO.
- docs/ (browseable version) contains all additional written documentation, including 'getting started' guides, the architecture, feature descriptions, development guidelines and more.