openeo-python-client
openeo-python-client copied to clipboard
Open-EO
Python client API for OpenEO
general ticket for VectorCube support and related improvements
A couple of issues with current (experimental) implementation of `fit_class_random_forest` and `fit_regr_random_forest` - [x] Add `fit_regr_random_forest` - [ ] python client defines default `max_variables=null` , while that's not the case...
Upcoming API/spec updates: - https://github.com/Open-EO/openeo-api/pull/492 - https://github.com/Open-EO/openeo-processes/pull/439 This is central/epic ticket to follow up necessary coverage of these changes in the python client
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...
related to #401, https://github.com/Open-EO/openeo-processes/issues/334, https://github.com/Open-EO/openeo-processes/pull/401 `DataCube.save_result` returns a DataCube, while it technically should return `true` (wrapped in `_ProcessGraphAbstraction`, to allow calling `.download()`, `.create_job`, ...)
FeatureCollection in the `openeo.udf.feature_collection` package was a direct copy of https://github.com/Open-EO/openeo-udf/blob/master/src/openeo_udf/api/feature_collection.py, including some things that look over-engineered or are unused as far as I know: - constructor requires a `id`...
`DataCube.dimension_labels()` now seems to return a DataCube in the python client: [DataCube.dimension_labels](https://open-eo.github.io/openeo-python-client/api.html#openeo.rest.datacube.DataCube.dimension_labels) I think it should return an array of strings (e.g. the band names for dimension "bands"). According to...
Documentation idea: add a cheat sheet page with snippets of essentials: - connect and auth - start cube from `load_collection` - sync download a cube - start/track batch job a...
I wanted to ask, if it would be possible to add a .sen2like() to the openeo-python-client? The process would be used directly on a SENTINEL2_L1C datacube using data.sen2like(spatial_extent = ?bounding-box:object...
(see `Connection.list_processes`)