-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openEO API v0.4.0 #170
openEO API v0.4.0 #170
Conversation
…(originally authored by @christophfriedrich).
…es for 0.3.1 into 0.4.0)
…ocesses`) follows the general schema for openEO errors. Removed numeric openEO error codes from error list and replaced numeric error codes with textual error codes in error responses.
…200 for valid and invalid process graphs and responds with a list of errors. #144
…ersion` was renamed to `api_version`.
…ST /validation without authentication (#151).
…s and the `job_id` of jobs has changed to `id` in responses (#130). The `status` property of jobs is now required.
…tput format properties in `POST /preview`, `POST /jobs`, `PATCH /jobs` and `GET /jobs/{job_id}` requests removed in favor of export processes. (#153)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I scanned through the docs and API and didn't find major issues.
Co-Authored-By: m-mohr <[email protected]>
…arth Observation.
The examples, especially https://open-eo.github.io/openeo-api/v/0.4.0/jobs/, needs to be updated. |
Last chance to review this and point out problems before the 0.4 release. All issues are solved now. |
openEO API v0.4.0 (Release candidate, actual release is planned for 28/02/2019)
Currently, #158 may bring in some additional minor changes to the data discovery part. Also, processes may change slightly depending on feedback. Lastly, I still need to update several examples in the documentation. Nevertheless, I'd highly appreciate if you could give it a final review before releasing it.
Note: Single source of truth are the actual sources for the rendered version (e.g. openapi.json, JSON files for processes, ...). For example,
cube:dimensions
in the collections is currently not shown in the rendered API documentation due to a bug in ReDoc, but it is still required to be implemented!