You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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.)
The text was updated successfully, but these errors were encountered: