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
Le 19/03/2024 à 22:56, Rahkonen Jukka via gdal-dev a écrit :
Hi,
I suppose that something similar than with gdalwarp
https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken
happens but with gdal_rasterize I think there are no tricks that could
help.
Actually th
2024 18.09
Vastaanottaja: Rahkonen Jukka
Kopio: gdal-dev@lists.osgeo.org
Aihe: Re: [gdal-dev] gdal_rasterize processed GTiff filesize question
Yes, the target files already exists. Yes, I’ve tried to investigate this issue
on some small and medium files. For example:
original hillshade.tif size is
@lists.osgeo.org > Puolesta Andrey VI
>via gdal-dev
>Lähetetty: tiistai 19. maaliskuuta 2024 14.43
>Vastaanottaja: gdal-dev@lists.osgeo.org
>Aihe: [gdal-dev] gdal_rasterize processed GTiff filesize question
>
>Hello.
>
>I’m using gdal_rasterize to remove som
Rahkonen-
Lähettäjä: gdal-dev Puolesta Andrey VI via
gdal-dev
Lähetetty: tiistai 19. maaliskuuta 2024 14.43
Vastaanottaja: gdal-dev@lists.osgeo.org
Aihe: [gdal-dev] gdal_rasterize processed GTiff filesize question
Hello.
I’m using gdal_rasterize to remove some data from DEM (Int16) and
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
