Opened 16 years ago
Closed 16 years ago
#806 closed defect (fixed)
Odd NODATA selection for rasters
| Reported by: | warmerdam | Owned by: | ersts |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | Branch - Raster Transparency |
| Component: | Rasters | Version: | Trunk |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | Linux |
| Platform Version: | Awaiting user input: | no |
Description
I have build from the raster_transparency_branch as of last week.
I loaded a raster which gdalinfo does not report as having a nodata value.
But the raster layer seems to have defaulted to treating pixel value "0" as nodata, and made it transparent. Is this intentional? Shouldn't the decision to have an initial nodata value depend on what GDAL reports (with the option for the user to override)?
Let me know if more detail is needed.
Note:
See TracTickets
for help on using tickets.
I believe this was due to not verifying if the NoDataValue being returned by GDAL was valid. There is a check in place now that will set the NoDataValue to -9999 if GDAL reports that there is no NoDataValue. The user can always change the NoDataValue to what every they like on the 'Transparency Tab' (raster_transparency_branch specific)
This has been addressed in r7406. I will leave the ticket open until it is verified that it is an acceptable solution, then the same can be applied to the trunk.