#158 closed defect (fixed)
loading a float raster layer returns an integer when the no-data value is an integer.
| Reported by: | Owned by: | timlinux | |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | |
| Component: | Rasters | Version: | 0.8 |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | Windows |
| Platform Version: | Awaiting user input: | no |
Description
If you have an AAIGrid raster layer no-data value set to -9999, such as when you export an AAIGrid from ArcMAP, the layer will viewed as an integer layer, even if the values are floating points. If you do a fine and replace and change -9999 to -9999.5 or -1.#QNAN it will be displayed as a floating point appropriately.
Change History (4)
comment:1 by , 18 years ago
| Milestone: | → Version 0.8 Release |
|---|
comment:2 by , 18 years ago
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is a problem in GDAL. It has been fixed (see http://lists.maptools.org/pipermail/gdal-dev/2006-July/009572.html and http://bugzilla.remotesensing.org/show_bug.cgi?id=1071), but missed the 1.3.2 release of GDAL (the latest).
Note:
See TracTickets
for help on using tickets.
Can you attach an example file that has this problem?