<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.msonormalmrcssattr, li.msonormalmrcssattr, div.msonormalmrcssattr
{mso-style-name:msonormal_mr_css_attr;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.Shkpostityyli20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FI" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I suppose that something similar than with gdalwarp
<a href="https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken">
https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken</a> happens but with gdal_rasterize I think there are no tricks that could help.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">-Jukka Rahkonen-<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>Lähettäjä:</b> Andrey VI <andrey_vi@list.ru> <br>
<b>Lähetetty:</b> tiistai 19. maaliskuuta 2024 18.09<br>
<b>Vastaanottaja:</b> Rahkonen Jukka <jukka.rahkonen@maanmittauslaitos.fi><br>
<b>Kopio:</b> gdal-dev@lists.osgeo.org<br>
<b>Aihe:</b> Re: [gdal-dev] gdal_rasterize processed GTiff filesize question<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div id="style_17108603221275315526">
<div id="style_17108603221275315526_BODY">
<div>
<div>
<div>
<p class="MsoNormal">Yes, the target files already exists. Yes, I’ve tried to investigate this issue on some small and medium files. For example:<br>
original hillshade.tif size is 11469 bytes, after gdal_rasterize its size is 26465 bytes, and after gdal_translate - 15426 bytes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">original - 7477 K, gdal_rasterize - 8705 K, gdal_translate - 5964 K,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">original - 39110 K, gdal_rasterize - 39112 K, gdal_translate - 446 K.<br>
So, <span lang="EN">it depends on the content of the raster.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN">I would like to avoid intermediate processing if possible. This will require additional time for processing and space for the data. Moreover, in some cases a lot of space needs to be allocated for intermediate files.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Andrey<o:p></o:p></p>
</div>
<div>
<blockquote style="border:none;border-left:solid #0857A6 1.0pt;padding:0cm 0cm 0cm 8.0pt;margin-left:7.5pt;margin-top:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt">
<p class="MsoNormal">Tuesday, March 19, 2024 4:25 PM +03:00 from Rahkonen Jukka <<a href="/compose?To=jukka.rahkonen@maanmittauslaitos.fi">jukka.rahkonen@maanmittauslaitos.fi</a>>:<br>
<o:p></o:p></p>
<div>
<div id="">
<div>
<div>
<div id="style_17108547490217322390_BODY_mr_css_attr">
<div>
<div>
<p class="msonormalmrcssattr"><span style="mso-fareast-language:EN-US">Hi,</span><o:p></o:p></p>
<p class="msonormalmrcssattr"><span style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="msonormalmrcssattr"><span lang="EN-US" style="mso-fareast-language:EN-US">So the target files dem.tif and hillshade.tif exist already? Maybe it is not so simple to update already compressed data in place. Have you tried what happens if you re-write
the results into new files<br>
<br>
gdal_translate -co tiled=yes -co compress=LZW hillshade.tif final_hillshade.tif.</span><o:p></o:p></p>
<p class="msonormalmrcssattr"><span lang="EN-US" style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="msonormalmrcssattr"><span lang="EN-US" style="mso-fareast-language:EN-US">-Jukka Rahkonen-</span><o:p></o:p></p>
<p class="msonormalmrcssattr"><span lang="EN-US" style="mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="msonormalmrcssattr"><b>Lähettäjä:</b> gdal-dev <<a href="mailto:gdal-dev-bounces@lists.osgeo.org">gdal-dev-bounces@lists.osgeo.org</a>>
<b>Puolesta </b>Andrey VI via gdal-dev<br>
<b>Lähetetty:</b> tiistai 19. maaliskuuta 2024 14.43<br>
<b>Vastaanottaja:</b> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<b>Aihe:</b> [gdal-dev] gdal_rasterize processed GTiff filesize question<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="msonormalmrcssattr"> <o:p></o:p></p>
<div>
<div id="style_17108518540727893310_BODY_mr_css_attr">
<div>
<div>
<p class="msonormalmrcssattr">Hello.<o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr"> <o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr">I’m using gdal_rasterize to remove some data from DEM (Int16) and hillshade (Byte) rasters with shape-file, like this:<o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr">gdal_rasterize -burn -32768 shape.shp dem.tif and gdal_rasterize -burn 0 shape.shp hillshade.tif<o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr">Both DEM and hillshade GTiffs created with -co COMPRESS=LZW -co TILED=YES options. After processing with gdal_rasterize the
<span lang="EN">size of GTiffs becomes 1.5 times larger</span>. Why it happens? <span lang="EN">
I assumed that it should be the other way around, because a significant portion of the data is replaced with the same values and should be compressed well.</span><o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr"> <o:p></o:p></p>
</div>
<div>
<p class="msonormalmrcssattr">Andrey<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>