gdal_fillnodata.py does not remember the nodata value

[cgsbob]

I have one grid (which is too large to share) with a nodata value of -999999. When I do this:

gdal_fillnodata.py pga.tif pga_fillnodata.tif
gdalinfo -mm pga_fillnodata.tif

I see the min value is now -999999 and the metadata for nodata is now gone.

I've tried to reproduce this error with a small grid (attached), but the min/max values are good, but the metadata for nodata is still gone.

I've noticed this problem in both OSGEO4W and GDAL svn.

[cgsbob]

test geotiff to demonstrate the loss of nodata after running gdal_fillnodata.py

[Kyle Shannon]

there is a patch on #4539 that may fix this.

[Jukka Rahkonen]

The issue seems to be the same with GDAL 2.0-dev: Gdalinfo -mm of the attached source image is Band 1 Block=34x30 Type=Float64, ColorInterp=Gray

Computed Min/Max=0.233,0.518

NoData Value=-9999

Gdalinto -mm of the target created with the gdal_fillnodata.py: Band 1 Block=34x30 Type=Float64, ColorInterp=Gray

Computed Min/Max=0.233,0.518

So the NoData row does not exist.

[Kyle Shannon]

Fixed in r28149: FillNodata: copy no data value to destination band when creating a dataset (if available), #4625

[Kyle Shannon]

test added in r28150