Reduce the STAC calls made by PlanetaryComputer during ingestion/materialization #148
Conversation
This file contains 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
…rialization. During direct materialization in particular, we previously would make 3 STAC calls to get STAC item by ID: once in get_raster_bands, once in get_raster_bounds, and once in read_raster. Now we expose a cache_dir option so we save the asset URLs during preparing, so we don't need any of these calls. Although the asset URLs are now saved with the item, the cache_dir is still needed because we don't currently have access to the item objects when materializing with a TileStore interface. This speeds up direct materialization substantially since previously the STAC API calls were a bottleneck.
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.
Reduce the STAC calls made by PlanetaryComputer during ingestion/materialization.
During direct materialization in particular, we previously would make 3 STAC calls to get STAC item by ID: once in get_raster_bands, once in get_raster_bounds, and once in read_raster.
Now we expose a cache_dir option so we save the asset URLs during preparing, so we don't need any of these calls. Although the asset URLs are now saved with the item, the cache_dir is still needed because we don't currently have access to the item objects when materializing with a TileStore interface.
This speeds up direct materialization substantially since previously the STAC API calls were a bottleneck.