[gdal-dev] gdalwarp does not apply source nodata value to destination
etourigny.dev at gmail.com
Fri May 17 07:33:07 PDT 2013
I have created a ticket and attached a patch to resolve this.
On Wed, May 15, 2013 at 11:12 AM, Etienne Tourigny
<etourigny.dev at gmail.com>wrote:
> I have just noticed that destination nodata value is not set when
> -dstnodata option is not used in gdalwarp.
> This can be problematic when warping a dataset with no data values, as the
> result can be different from expected, if -dstnodata is not set.
> gdalwarp does use source nodata pixels if -srcnodata is not used.
> I consider this as a bug (or at the very least a limitation), because one
> cannot warp a dataset in an automatic fashion and get expected output (with
> same nodata value as input).
> Would it be OK to copy them over if -dstnodata is not used, or would there
> be problems with doing this? Or perhaps a new argument -copynodata could be
> added if there is fear of disruption.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gdal-dev