Skip to content
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: proper geometry spatial_extent support #768

Open
soxofaan opened this issue Apr 30, 2024 · 0 comments
Open

load_collection: proper geometry spatial_extent support #768

soxofaan opened this issue Apr 30, 2024 · 0 comments

Comments

@soxofaan
Copy link
Member

soxofaan commented Apr 30, 2024

(reported by @VictorVerhaert / @VincentVerelst)
load_collection supports GeoJSON/Vector cubes as spatial_extent and the spec mentions that this should involve masking (in the sense of mask_polygon/filter_spatial):

For raster data, all pixels inside the bounding box that do not intersect with any of the polygons will be set to no data (null).

Experiments of @VictorVerhaert however show that the geopyspark implementation just takes the bounding box of the geometries and does not apply masking.

Side-observation: the geopyspark implementation also supports feature collections containing only points (in the sense that the total bounding box is used), while the spec does not list point support. Related issue: Open-EO/openeo-processes#502

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant