Bug report #6786

Poor handling of float nodata value

Added by Rudi von Staden about 3 years ago. Updated almost 3 years ago.

Status:Closed Start Date:11/29/2012
Priority:Normal Due date:
Assigned to:- % Done:


Target version:-
Platform:ubuntu Patch supplied:No
Platform version:12.10 Affected version:master
Status info: Causes crash or corruption:No
Resolution:wontfix Tag:


I am trying to process some bioclimatic raster files, such as can be downloaded from http://www.worldclim.org/current (bioclim set). They seem to have nodata values set to -3.4e+38 according to QGIS (looking at the output of gdalinfo, it's -3.39999999999999996e+38).

QGIS picks up the nodata value (attached nodata_dialog.jpg), but does not apply it. In the layer styling, there's an entry for -3.4e+38 set to 100% transparent, but it still displays such values, even though the "Identify features" picker shows them as having value -3.4e+38 (nodata.jpg).

A workaround was to first use gdalwarp to change the nodata value to an integer, or to use gdal_translate to convert from a float to integer raster file. See discussion at http://gis.stackexchange.com/questions/42555/what-to-do-with-3-4e38-nodata-values/ for more.

nodata_dialog.jpg (45.5 kB) Rudi von Staden, 11/29/2012 08:10 am

nodata.jpg (38.8 kB) Rudi von Staden, 11/29/2012 08:10 am


Updated by Giovanni Manghi almost 3 years ago

  • Status changed from Open to Feedback

rasters have been overhauled in qgis master, have you tested it?

Updated by J├╝rgen Fischer almost 3 years ago

  • Status changed from Feedback to Closed
  • Resolution set to wontfix

closing for the lack of feedback

Also available in: Atom