-
Notifications
You must be signed in to change notification settings - Fork 4
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
VectorCubes: fix/improve Point
handling in aggregate_spatial
#239
Comments
soxofaan
added a commit
that referenced
this issue
Oct 13, 2022
soxofaan
added a commit
that referenced
this issue
Oct 13, 2022
soxofaan
added a commit
that referenced
this issue
Oct 14, 2022
soxofaan
added a commit
that referenced
this issue
Oct 14, 2022
soxofaan
added a commit
that referenced
this issue
Oct 14, 2022
rows apparently run from north to south
soxofaan
added a commit
that referenced
this issue
Oct 14, 2022
rows apparently run from north to south
soxofaan
added a commit
that referenced
this issue
Oct 14, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
load_collection projected_polygons: the special case for Point handling can be removed without other changes apparently
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
Point specifics are now covered in to_projected_polygons
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
soxofaan
added a commit
that referenced
this issue
Oct 18, 2022
Point specifics are now covered in to_projected_polygons
soxofaan
added a commit
that referenced
this issue
Oct 19, 2022
- `to_projected_polygons` now also handles point buffering - related to #239
soxofaan
added a commit
to Open-EO/openeo-geopyspark-integrationtests
that referenced
this issue
Oct 19, 2022
cases are now covered directly in openeo-geopyspark-driver just kept 2 cases (simplest and most complex) in integration tests related to Open-EO/openeo-geopyspark-driver#239
soxofaan
added a commit
that referenced
this issue
Oct 19, 2022
Fixed/address various issues in various projects now time to close this one |
soxofaan
added a commit
to Open-EO/openeo-python-driver
that referenced
this issue
Oct 20, 2022
soxofaan
added a commit
that referenced
this issue
Oct 20, 2022
soxofaan
added a commit
to Open-EO/openeo-python-driver
that referenced
this issue
Oct 20, 2022
soxofaan
added a commit
that referenced
this issue
Oct 20, 2022
soxofaan
added a commit
to Open-EO/openeo-python-driver
that referenced
this issue
Oct 24, 2022
replaced by `GeometryBufferer` helper related to #141, Open-EO/openeo-geopyspark-driver#239, #148
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spin off from Open-EO/openeo-python-driver#141 :
using
DriverVectorCube
by default inaggregate_spatial
surfaced some issues related toPoint
geometry handling.As a quick fix,
Point
geometry handling was reverted to non-DriverVectorCube
behavior (see Open-EO/openeo-python-driver@2ec255e and Open-EO/openeo-python-driver@4927eee).But this special case code path has to be eliminated again, and
Point
geometries should be supported properly in the vector cube wayThe text was updated successfully, but these errors were encountered: