On Monday 06 June 2016 02:23:24 jramm wrote:
> This is my mistake.
> I had not truly created a sparse raster! I keep forgetting that the gdal
> tools (gdal_translate) will still write the sparse blocks and the sparse
> creation option is just to indicate that FillEmptyBlocks should be skipped.
> Cr
This is my mistake.
I had not truly created a sparse raster! I keep forgetting that the gdal
tools (gdal_translate) will still write the sparse blocks and the sparse
creation option is just to indicate that FillEmptyBlocks should be skipped.
Creating the sparse file by hand correctly sets the blo
Hi
I am having a few problems with using this (via python).
I have a test dataset with a 16 x 16 blocksize. In the below examples, bnd =
ds.GetRasterBand(1)
First, I try getting the blocksizes using the metadata:
This gives:
None of the first 10 blocks are empty - this is strange as it is
Le vendredi 19 février 2016 10:48:50, jramm a écrit :
> We are storing large raster datasets (~500,000 x 500,000) in geotiff files.
> The array data is typically very sparse (density is 0.02% or less) and
> compression greatly reduces the geotiff size.
>
> However, when processing data we read the
We are storing large raster datasets (~500,000 x 500,000) in geotiff files.
The array data is typically very sparse (density is 0.02% or less) and
compression greatly reduces the geotiff size.
However, when processing data we read the data in chunks, which are
automatically decompressed..this mean
