Opened 9 years ago
Closed 9 years ago
#6036 closed defect (invalid)
Enable NODATA to be set to -nan
Reported by: | hrz | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | default | Version: | 2.0.0 |
Severity: | normal | Keywords: | |
Cc: |
Description
The attached TIFF with Float32
datatype contains values that are negative not a number (-nan
):
gdallocationinfo negative-nan-example.tif 0 0 Report: Location: (0P,0L) Band 1: Value: -nan
It does not appear to be possible to set specify -nan
as the NODATA value e.g:
gdal_translate -a_nodata '-nan' -of VRT negative-nan-example.tif negative-nan-example.vrt
The resulting NODATA value is always unsigned nan
.
Attachments (1)
Change History (4)
by , 9 years ago
Attachment: | negative-nan-example.tif added |
---|
comment:2 by , 9 years ago
I have generated rasters using both r.external.out
and r.out.gdal
built with the GRASS fix referenced above (commit r65602
). These create nan
values that are successfully interpreted as NODATA
by GDAL - thank you!
Interestingly r.out.gdal
still outputs the following message which talks about -nan
:
Input raster map contains cells with NULL-value (no-data). The value -nan will be used to represent no-data values in the input map. You can specify a nodata value with the nodata option.
comment:3 by , 9 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
I understand we can close this ticket.
Note:
See TracTickets
for help on using tickets.
TIFF file containing
-nan
values.