Open-EO / Open-EO/openeo-python-client
follow `/processing_options` for specifying job options in `create_job`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Depends on PR https://github.com/Open-EO/openeo-api/pull/471 (currently planned for API 1.3.0)
Python client currently adds all "additional" job options under a "job_options" field, which is non-standard
https://github.com/Open-EO/openeo-python-client/blob/c4d809fc9ecd4995f823a1e21e1b67340096aef3/openeo/rest/connection.py#L1471-L1473
PR https://github.com/Open-EO/openeo-api/pull/471 standardizes how job/service options should be specified and client should follow that when available
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in openeo/rest/connection.py at the referenced lines around create_job, and read API PR 471 for the standardized option format. Compare the current job_options handling with /processing_options once that API change is available; done means create_job follows the standardized format rather than the non-standard job_options field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100