Odd NODATA selection for rasters
|Branch - Raster Transparency
|Must Fix for Release:
|Awaiting user input:
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.