[GRASS-dev] Re: [GRASS GIS] #73: r.out.gdal tiff output does not
work
GRASS GIS
trac at osgeo.org
Sat Aug 23 11:21:18 EDT 2008
#73: r.out.gdal tiff output does not work
--------------------------+-------------------------------------------------
Reporter: helena | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: critical | Milestone: 6.4.0
Component: Raster | Version: svn-trunk
Resolution: | Keywords: r.out.gdal, tiff
Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by mmetz):
Replying to [comment:14 neteler]:
> Great work!
Thanks!
> Would you mind to also test back-import into GRASS?
All GeoTIFFs previously exported with the test version of r.out.gdal were
back-imported to GRASS-6.4.svn (snapshot_2008_08_23)
GeoTIFF files:[[BR]]
elevation.Byte.clrtbl.tif[[BR]]
elevation.Byte.noclrtbl.tif[[BR]]
elevation.UInt16.clrtbl.tif[[BR]]
elevation.UInt16.noclrtbl.tif[[BR]]
elevation.Int32.noclrtbl.tif[[BR]]
elevation.Float32.noclrtbl.tif
display: all ok, very slow for the UInt16 back-import with
colortable[[BR]]
colortable: all ok[[BR]]
cell values: all ok[[BR]]
nodata: all ok
Back-importing elevation.UInt16.clrtbl.tif is pretty slow. Display takes
quite some time too. It is a colortable with 65535 entries, one for each
potential cell value, an exact copy of the GeoTIFF colortable. Removing
the colortable with r.colors -r, then copying the colortable of the back-
import of elevation.Byte.clrtbl.tif results in the same display, but now
fast on refresh, as expected.
Back-import of all other GeoTIFF files is fast, as is display in GRASS.
I would prefer to use r.out.gmt to get the GRASS color rules into an extra
file (GMT .cpt). This would also be a workaround for export file types
other than Byte and UInt16 where GDAL does not support writing out a
colortable. But then I don't know how widely GMT .cpt files are supported.
Markus
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/73#comment:15>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list