Add RasterReader
and RasterStackReader
implementations
#188
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.
Some timing results on a test where I had
(80, 2160, 3600)
.bin
: flat binary/ENVI.h5
: HDF5 with gzip.lzf.h5
: HDF5 with lzf compression.tif
: geotiff with dolphin default compression optionsHDF5StackReader:
BinaryReader:
Raster:
Comparing to the current VRT stack method for reading, there's a pretty wide range of times based on the file format.
Note that the "keep_open" and "num_threads" here dont matter, because i was reading all bands for a block so, which uses
ds.ReadAsArray
to let gdal read all bands.For input HDF5 files:
geotiff inputs are much faster, and seem to beat the other readers:
and the binary ENVI files are slower with GDAL (likely from the block shape which doesnt match
(1, ncols)