id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 5077,Pixels with NODATA value in a PostGISRaster get reset to 0.0 by gdal_translate,kempisty,warmerdam,"I have some 32BF raster datasets stored in a PostGIS 2.0 database. Their NODATA values are all set to 9999.0 `gdalinfo`, using the ""PG:"" format for the source raster, correctly reports NODATA Value=9999. `gdallocationinfo` correctly returns 9999.0 when I probe a location that has a NODATA value. When I attempt to translate the PostGIS rasters to a raw floating point file (`gdal_translate -of Ehdr` will do the job), the resulting output has zeroes where the NODATA pixels are supposed to be. It does not matter if I use `-a_nodata 9999`; I still get 0.0 substituted at all NODATA locations. This also has the side effect of breaking Mapserver. Instead of drawing transparent pixels, NODATA areas are now colored as if they contain a perfectly valid data point with a value of 0.0. FWIW, I did not experience this problem in in GDAL 1.9. Could this actually be a bug somewhere in VRTRasterBand? ",defect,closed,normal,closed_because_of_github_migration,default,1.10.0,normal,wontfix,PostGISRaster gdal_translate NODATA,