Bug report #19409: [processing] GDAL fillnodata gets wrong mask - QGIS Application - QGIS Issue Tracking

Bug report #19409

[processing] GDAL fillnodata gets wrong mask

Added by David Arango over 6 years ago. Updated over 6 years ago.

Status:	Closed
Priority:	Normal
Assignee:	Luigi Pirelli
Category:	Processing/GDAL
Affected QGIS version:	3.3(master)	Regression?:	No
Operating System:	everyone	Easy fix?:	Yes
Pull Request or Patch supplied:	Yes	Resolution:
Crashes QGIS or corrupts data:	No	Copied to github as #:	27237

Description

Using the processing gdal.fillnodata algorithm the input mask is different from the selected raster mask.

The command line doesn't use the correct mask and it uses the following mask: "-mask /home/cartolab/Escritorio/resultados/4_out_Z_heights.tif"
gdal_fillnodata.py -md 10 -b 1 -mask /home/cartolab/Escritorio/resultados/4_out_Z_heights.tif -of GTiff /home/cartolab/Escritorio/resultados/4_out_Z_heights.tif /home/cartolab/Escritorio/out_fill_4.tif

This bug is reported by Geomove project, developed by Cartolab

Associated revisions

Revision 95246e76
Added by Luigi Pirelli over 6 years ago

Mask parameter was wrongly set. Fixes #19409

Revision e2a740be
Added by Luigi Pirelli over 6 years ago

Merge pull request #7408 from luipir/fix_gdalfillnodata_issue19409

[processing] Fix wrongly set mask in gdal:fillnodata Fixes #19409

Revision b9e5f4a2
Added by Luigi Pirelli over 6 years ago

Mask parameter was wrongly set. Fixes #19409

History

#1 Updated by Luigi Pirelli over 6 years ago

seems the algorithm is affected of different problems

~~1) mask is not passed correctly~~ (wrong intepretation of the parameter use)
~~2) result is not loaded automatically (if set)~~ (not confirmed)

btw seems that mask is not used correctly by gdal command, but this can be a gdal problem that have to be investigated

#2 Updated by Luigi Pirelli over 6 years ago

Easy fix? changed from No to Yes

#3 Updated by Luigi Pirelli over 6 years ago

Pull Request or Patch supplied changed from No to Yes

PR https://github.com/qgis/QGIS/pull/7408
with tests

#4 Updated by Luigi Pirelli over 6 years ago

Luigi Pirelli wrote:

seems the algorithm is affected of different problems

1) mask is not passed correctly
~~2) result is not loaded automatically (if set)~~ (not confirmed)

btw seems that mask is not used correctly by gdal command, but this can be a gdal problem that have to be investigated

mask is processed correctly because they are the selection of nodatavalue areas that have to be processed