openeo-python-client
openeo-python-client copied to clipboard
Open-EO
Python client API for OpenEO
when passing a string as `polygon` argument to `ImageCollectionClient.mask`: https://github.com/Open-EO/openeo-python-client/blob/b5f3b4725ed54a7ab1522992b330221c07f6f287/openeo/rest/imagecollectionclient.py#L777-L784 or in _get_geometry_argument: https://github.com/Open-EO/openeo-python-client/blob/2ce9d3be823ff2201e55d2e96e82811714164e9a/openeo/rest/datacube.py#L900 this implementation assumes process `read_vector` which is currently a VITO specific process and I'm not aware...
Some backends have middleware to throttle the number of concurrent requests, returning a `429 Too Many Requests` if some limit is exceeded. The python client could provide automatic retry with...
@soxofaan looks like something we can merge easily as this is mostly about using functionality from requests?
When the arguments of e.g. `apply_datacube` to not match, the error states "No UDF found." This could be made clearer and more specific to point a user in the right...
a user tried to use `Connection.upload_file()` but that failed with `[404] NotFound: ...` Client should not even attempt to do `/files` requests if these are not reported in capabilities (e.g....
Feature idea from @EmileSonneveld : have a way to automatically generate a job description with some desired metadata (current git commit, used python source code, ...). e.g. very rough concept:...
I'm trying to run ```py data = connection.load_collection( "ERA5", spatial_extent = None, temporal_extent = ["2000-01-01", "2000-01-02"], bands = ["u10", "v10"] ) data = data ** 2.01 # also tried data.power(2.01)...
job progress reports in a jupyter notebook can take quite some vertical space, e.g. ``` 0:00:00 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': send 'start' 0:00:20 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A) 0:00:28 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued...
I have a backend with the following response to GET /credentials/oidc: ```json { "providers":[ { "id":"google", "issuer":"https://accounts.google.com", "title":"Google", "description":"Login with your Google Earth Engine account.", "scopes":[ "openid", "email", "https://www.googleapis.com/auth/earthengine" ],...
Add some kind of hook to `Connection` that allows users to inspect the process graph that is sent from a `cube.download()` or `cube.create_job()`. Would be handy for example in testing/CI...