Open
Conversation
…cleanup based on configured policies, e.g. file age of 30 minutes.
…or "GDAL_MOSAIC_BAND_INDEX".
…ing testing `afterAll`.
…rings and text, may break build.
…tile' in strings and text.
… on device" on remote build
…ed "finalTableFuse" handling.
…ileRecords" and "stepTessellate" options.
…pe or after writing to BinaryType.
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
1 participant
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.
In preparation for upcoming transition to dblabs spatial-utils (follow-on to dblabs mosaic but for DBR 14.3+, adjusted for various enhancements relating to our productized geospatial APIs):
Datasethandling to include "hydrating" (loading the object) more lazilyMosaicRasterTile,MosaicRasterGDAL, andMosaicRasterBandGDAL.RasterTileobjects can store the tile payload (BinaryType|StringType|GDAL Dataset) to the configured fuse checkpoint dir (see below); raster tiles generated in 0.4.1 and 0.4.2 can be loaded as-is (structure was different prior to that).Additionally, there are various maintenance commits, see [DRAFT] CHANGELOG for more.