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

Empty point extraction job results should not be downloaded #250

Closed
3 tasks
kvantricht opened this issue Jan 17, 2025 · 1 comment
Closed
3 tasks

Empty point extraction job results should not be downloaded #250

kvantricht opened this issue Jan 17, 2025 · 1 comment
Assignees
Milestone

Comments

@kvantricht
Copy link
Contributor

kvantricht commented Jan 17, 2025

We have quite a few empty parquet files resulting from point extraction jobs. The reason for this is that currently we have to buffer point-based extractions because occasional single-point jobs are not yet supported in openEO (Open-EO/openeo-geopyspark-driver#996)

Very small buffers sometimes do not contain any pixel center of a collection and the resulting extraction is nodata for all observations. These get dropped, finally resulting in an empty dataframe.

Things to do:

  • Change post-job action to detect empty dataframes and don't download these (they give downstream issues)
  • Make sure current point-extractions have square 5m buffer for the actual extraction, avoiding this getting dropped
  • waiting for final fix in openEO, after which none of the above should be essential anymore (load_stac: support Point features Open-EO/openeo-geopyspark-driver#996)
@kvantricht kvantricht self-assigned this Jan 17, 2025
@kvantricht kvantricht added this to the System V2 milestone Jan 20, 2025
@kvantricht
Copy link
Contributor Author

Should be addressed by #266

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