[gdal-dev] gdal_rasterize expected behaviour

[Sean Gillies]

Hi Hug,

GDALRasterizeGeometries takes an array of geometries and iterates over them
from start to end, burning them into the raster one at a time. With a
strictly ordered vector layer, you can expect the later shapes to be burned
over the earlier ones.

On Mon, Mar 8, 2021 at 7:00 AM Hugues François <hugues.francois at inrae.fr>
wrote:

> Hello,
>
> I don't know exactly where I should ask this question and I wasn't able to
> find the answer when searching on the internet (maybe I didn't use the
> right keywords).
>
> I have to rasterize a vector layer, made of polygons, which resolution is
> finer than the destination raster I have to use so that I want to use the
> "all_touched" option. But since my the raster resolution is coarser than
> the vector one, it may happens sometimes that a single pixel is touched by
> several polygons (and sometime none of them encompass the pixel center
> point). In this case, how does the value burned to the raster is chosen
> among the candidates?
>
> Best regards,
> Hug
>
>

-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210308/e634d936/attachment.html>