Also: (using -init 255 will produce a TIFF with suitable nodata values in the second scenario I described, as a workaround.
However, gdal_rasterize still does not produce correct command line output in this situation, and also it should not be necessary for users to manually add a -init option and manually synchronise the value with the -a_nodata value to ensure valid output from gdal_rasterize) On Jun 12, 2013, at 7:50 PM, Graeme Bell <[email protected]> wrote: > > Summary: > > I noticed that gdal_rasterize invents data values instead of burning nodata > values, incorrectly, in what is probably a common situation - a valid query > returning geometry columns but zero polygon rows. > > Command line output suggests that nothing is being done, yet a GeoTIFF with > data values is silently rendered in the background. _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
