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

store gdalinfo to separate asset #352

Open
jdries opened this issue Nov 28, 2024 · 0 comments
Open

store gdalinfo to separate asset #352

jdries opened this issue Nov 28, 2024 · 0 comments
Assignees

Comments

@jdries
Copy link
Contributor

jdries commented Nov 28, 2024

For LCFM, certain quality checks rely on the gdalinfo output rather than the stac metadata. (Gdalinfo has a few extra fields, like block size.)
The request is to dump that output to a file, and retain it together with the other assets.
If we do this dump on the executors, and upload also to S3 (if applicable), then it also solves the issue of avoiding a (more expensive) gdalinfo on the driver.
I would not add the gdalinfo dump as an asset (yet), just keep it on the storage. We can then consider to export it to workspace perhaps based on feature flag. (Trying to keep this an internal thing, avoiding that users really depend on it.)

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

2 participants