Carsten,
gdal_rasterize definitely supports burning into existing files.
I'm not sure about the configuration of your raster -- some formats are not
updatable-in-place, but the limitation isn't in gdal_rasterize.
Best regards,
Frank
On Tue, Mar 19, 2024 at 8:42 AM Carsten Lockenkötter <
Why not just trying?
Demo:
$ gdal_create -outsize 10 10 -burn 255 test.tif -a_srs EPSG:4326 -a_ullr
0 10 10 0
$ gdal_rasterize -burn 0
'{"type":"Polygon","coordinates":[[[2,2],[2,4],[4,4],[4,2],[2,2]]]}'
test.tif
$ gdal_translate test.tif /vsistdout/ -of aaigrid
ncols 10
nrows
Thomas,
Le 19/03/2024 à 08:26, thomas bonfort via gdal-dev a écrit :
I have a side-question concerning the update-in-place behavior of the
gtiff driver in this case: given that a compressed strile will nearly
always be smaller after this update (due to better compression ratios
on the uniform
I have a side-question concerning the update-in-place behavior of the gtiff
driver in this case: given that a compressed strile will nearly always be
smaller after this update (due to better compression ratios on the uniform
area), will libtiff overwrite the previous strile in place also, or will
Carsten,
The gdal_rasterize command allows you to "burn in" polygons from an OGR
supported datasource into an existing raster. If your raster is a 3 band
RGB file, you could use --burn 100 150 200 to burn in the RGB value
(100,150,200). This will only work if the raster format you are using
