Opened 9 years ago
Closed 9 years ago
#6151 closed defect (fixed)
gdalbuildvrt and gdal_translate unable to handle large INT32 nodata values
| Reported by: | pauldzy | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.11.4 |
| Component: | GDAL_Raster | Version: | 1.11.2 |
| Severity: | normal | Keywords: | gdalbuildvrt gdal_translate mosaic nodata |
| Cc: |
Description
I have INT32 single band rasters created by US EPA where the nodata values are set to -2147483647.
When these rasters are run through gdalbuildvrt the VRTRasterBand is set as "-2.14748364700000E+009" and the individual rasters are set as "-2.14748e+009". When gdal_translate operates upon the vrt to mosaic the two rasters, the nodata values are not respected. Manually changing the vrt values to be the full "-2147483647" makes no difference.
Does this suggests that nodata values cannot be larger than a float32 with gdal? I see previous bug reports which suggest this type of thing but nothing definitive. Perhaps this is a documentation issue?
Thanks, Paul
Attachments (1)
Change History (2)
by , 9 years ago
| Attachment: | example.vrt added |
|---|
comment:1 by , 9 years ago
| Keywords: | nodata added |
|---|---|
| Milestone: | → 1.11.4 |
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
trunk r31002, branches/2.0 r31003, branches/1.11 r31004 "VRT: serialize NODATA and NoDataValue items with %.16g, e.g. so as to be able to hold large int32 nodata values (#6151)"