Re: [gdal-dev] gdal_rasterize processed GTiff filesize question

2024-03-19 Thread Andrey VI via gdal-dev
Hi, Even.   Using both options "-optim raster" and "-optim vector" results in the same size files. This is expected, since, as follows from the option description, it only affects the rasterization algorithm.   >Wednesday, March 20, 2024 1:04 AM +03:00 from Even Rouault >: >  >  >Le 19/03/20

Re: [gdal-dev] gdal_rasterize processed GTiff filesize question

2024-03-19 Thread Andrey VI via gdal-dev
so simple to update already compressed data in place. Have you tried what >happens if you re-write the results into new files > >gdal_translate -co tiled=yes -co compress=LZW hillshade.tif >final_hillshade.tif. >  >-Jukka Rahkonen- >  >Lähettäjä: gdal-dev < gdal-dev-boun...

[gdal-dev] gdal_rasterize processed GTiff filesize question

2024-03-19 Thread Andrey VI via gdal-dev
Hello.   I’m using gdal_rasterize to remove some data from DEM (Int16) and hillshade (Byte) rasters with shape-file, like this: gdal_rasterize -burn -32768 shape.shp dem.tif and gdal_rasterize -burn 0 shape.shp hillshade.tif Both DEM and hillshade GTiffs created with -co COMPRESS=LZW -co TILED=Y