Support option to materialize one file per-layer instead of per-item-group#464
Open
Support option to materialize one file per-layer instead of per-item-group#464
Conversation
…group. This adds a new RasterStorage abstraction that is responsible for accessing raster data stored at a window. Window.get_raster_dir is deprecated and instead all raster access should go through RasterStorage. The default RasterStorage, PerItemGroupStorage, is compatible with our existing datasets, while PerLayerStorage can be used to do the one-file-per-layer mode. Note that completed files will still be created per-item-group; we will need a db-backed WindowMetadata implementation to avoid that.
favyen2
commented
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a new RasterStorage abstraction that is responsible for accessing raster data stored at a window. Window.get_raster_dir is deprecated and instead all raster access should go through RasterStorage. The default RasterStorage, PerItemGroupStorage, is compatible with our existing datasets, while PerLayerStorage can be used to do the one-file-per-layer mode.
Note that completed files will still be created per-item-group; we will need a db-backed WindowMetadata implementation to avoid that.