> It makes sense that the order in which the data is written/stored affects
> the performance of the compression, but i don't get why it would be
> different for integers as compared to floats?
Floats are larger than Int8 and Int16, so for the same amount of
GDAL_CACHEMAX, you can cache less blo
Even,
Thanks for the suggestions, the first two work well. I'll have a look at the
ds.WriteRaster, that seems an interesting way, since it also prevents
unnecessary looping over the bands.
Writing per block is what i usually do, maybe that's why i never noticed it
before. I now ran into it whil
Le mercredi 03 juin 2015 15:21:07, Rutger a écrit :
> Dear list,
>
> When i try to write a floating point Geotiff from Python (both 32 or 64
> bit), the resulting file size is significantly larger compared to the
> output of gdal_translate. I wrote a small test script which tests this it
> for var
Dear list,
When i try to write a floating point Geotiff from Python (both 32 or 64
bit), the resulting file size is significantly larger compared to the output
of gdal_translate. I wrote a small test script which tests this it for
various creation options like compression and block-sizes. It seems
