Opened 13 years ago
Closed 13 years ago
#4292 closed defect (fixed)
gdal_rasterize sometimes doesn't use -a_nodata correctly
| Reported by: | Alister | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.9.0 |
| Component: | Algorithms | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
By default geotiffs created by gdal_rasterize are Float64. Create a geotiff with gdal_rasterize, setting the nodata value to something large e.g. -a_nodata 2147483647 The nodata value will be set to what you specify, but any areas which should be nodata will actually be 2147483648.
Is there something I'm missing here?
I have gdal1.8.1 from osgeo4w, although I think this behaviour has been around for a while.
Change History (1)
comment:1 by , 13 years ago
| Component: | Utilities → Algorithms |
|---|---|
| Milestone: | → 1.9.0 |
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
r23250 /trunk/gdal/alg/gdalrasterize.cpp: rasterize: use double instead of float to avoid precision issue with big nodata values (#4292)