-
Notifications
You must be signed in to change notification settings - Fork 42
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
load_collection: support shapely geometry input #678
Comments
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 10, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 10, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 10, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 13, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 16, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Dec 19, 2024
ElienVandermaesenVITO
added a commit
that referenced
this issue
Jan 2, 2025
ElienVandermaesenVITO
added a commit
that referenced
this issue
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See this TODO:
openeo-python-client/openeo/rest/datacube.py
Line 193 in ced3faa
The official load_collection process allows geojson and vector cube as input, but it seems that the python client doesn't allow that.
This is very annoying, because it means we need tedious conversion to the 'spatial_extent' format everywhere.
Also a shapely bbox can be expressed rather easily as box(1.0,2.0,3.0,4.0), following the commonly used minx,miny,maxx,maxy notation that is found on tools like bbox finder.
There's already a helper function that might be of use:
openeo-python-client/openeo/rest/datacube.py
Line 1061 in ced3faa
The text was updated successfully, but these errors were encountered: