since my office grassdata/ becomes huge, I wonder if I should
change to zlib compression.
From the "variables.html" page I get (btw: no mention of this in
the r.compress manual!):
GRASS_INT_ZLIB
[libgis]
if the environment variable GRASS_INT_ZLIB exists, new compressed
rasters will be compressed using zlib instead of RLE compression. Such
rasters will have a compressed value of 2 in the cellhd file.
Obviously, decompression is controlled by the raster's compressed
value, not the environment variable.
I wonder what the performance penalty of zlib could be. Does
anyone have experience? An advantage of stronger compression
could be that the data traffic on NFS on a cluster becomes less...
On Sun, Dec 11, 2011 at 10:39 PM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
since my office grassdata/ becomes huge, I wonder if I should
change to zlib compression.
From the "variables.html" page I get (btw: no mention of this in
the r.compress manual!):
I have now updated the manual page.
GRASS_INT_ZLIB
[libgis]
if the environment variable GRASS_INT_ZLIB exists, new compressed
rasters will be compressed using zlib instead of RLE compression. Such
rasters will have a compressed value of 2 in the cellhd file.
Obviously, decompression is controlled by the raster's compressed
value, not the environment variable.
I wonder what the performance penalty of zlib could be. Does
anyone have experience? An advantage of stronger compression
could be that the data traffic on NFS on a cluster becomes less...
If anything, I would expect that the difference in file size would be
less for GRASS rasters than for typical files because of the small
chunk sizes (each row is compressed separately).