[Gdal-dev] GDAL error exporting grass raster to Gtiff
Yves Jacolin
yjacolin at free.fr
Tue Nov 7 06:42:11 EST 2006
Le Lundi 6 Novembre 2006 19:45, Markus Neteler a écrit :
> On Mon, Nov 06, 2006 at 05:01:41PM +0100, Yves Jacolin wrote:
> > Le Lundi 6 Novembre 2006 16:53, Frank Warmerdam a écrit :
> > > Yves Jacolin wrote:
> > > > Hi,
> > > >
> > > > I tried to export raster data from GRASS to GTiff with r.out.gdal, I
> > > > get this error message :
> > > > GRASS 6.2.0RC1 (Lambert2Nord):~ > r.out.gdal input=C03r type=Byte
> > > > output=C03.tiff
> > > > Writing format: GTiff
> > > > Writing type: Byte
> > > > Input file size is 2159, 1574
> > > > 0Warning 1: Lost metadata writing to GeoTIFF ... too large to fit in
> > > > tag. ...10...20...30...40...50...60...70...80...90...100 - done.
> > > > /usr/local/grass-6.2.0RC1/scripts/r.out.gdal: line 136: 25674 Erreur
> > > > de segmentation gdal_translate -of $FORMAT -ot $TYPE $CREATEKEY
> > > > $METAKEY $CELLHD $OUTPUT
> > > >
> > > > I posted a message in the grass list but I got no answer. Have you
> > > > got any ideas ? Thank you.
> > >
> > > Yves,
> > >
> > > I would guess that there is a large color table associated with the
> > > input raster and it is overflowing the size of a TIFF tag. I don't
> > > know why this is resulting in a segmentation fault in r.out.gdal
> > > though.
> > >
> > > Best regards,
> >
> > Thank you Frank,
> >
> > The files are really created but the color are not good ! You are right.
> > Do you think if I change the color table in GRASS, I can sucess to export
> > them ? The raster came from tif files extracted from PDF files and
> > georeferenced inside GRASS.
>
> Another possibility could be that you need to rebuild the
> GRASS-GDAL-OGR plugin. Using
>
> ldd `which gdal_translate`
> you could check if the right plugin is used.
>
> Markus
Thanks Markus,
I did what you suggested to do yesterday. I get this (I don't understand what
it means) :
linux-gate.so.1 => (0xffffe000)
libgdal.so.1 => /usr/local/lib/libgdal.so.1 (0xb7ac4000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7ab1000)
libogdi31.so => /usr/local/lib/libogdi31.so (0xb7a93000)
libungif.so.4 => /usr/lib/libungif.so.4 (0xb7a8b000)
libgeotiff.so.1.2.2 => /usr/lib/libgeotiff.so.1.2.2 (0xb78bb000)
libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb786b000)
libpng.so.3 => /usr/lib/libpng.so.3 (0xb7845000)
libpq.so.4 => /usr/lib/libpq.so.4 (0xb7828000)
libz.so.1 => /lib/libz.so.1 (0xb7815000)
librt.so.1 => /lib/tls/librt.so.1 (0xb780c000)
libdl.so.2 => /lib/libdl.so.2 (0xb7808000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb772c000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7707000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb76fb000)
libc.so.6 => /lib/tls/libc.so.6 (0xb75c9000)
libgeos.so.2 => /usr/local/lib/libgeos.so.2 (0xb74d0000)
libodbc.so.1 => /usr/lib/libodbc.so.1 (0xb7467000)
libNCSEcw.so.0 => /usr/local/lib/libNCSEcw.so.0 (0xb7334000)
libNCSCnet.so.0 => /usr/local/lib/libNCSCnet.so.0 (0xb731f000)
libNCSUtil.so.0 => /usr/local/lib/libNCSUtil.so.0 (0xb72fe000)
libjasper-1.701.so.1 => /usr/lib/libjasper-1.701.so.1 (0xb72b2000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb7292000)
/lib/ld-linux.so.2 (0xb7fdf000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0xb7272000)
libproj.so.0 => /usr/local/lib/libproj.so.0 (0xb723d000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0xb7234000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0xb721c000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xb7150000)
libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0xb711f000)
libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0xb7014000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb6fe6000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb6fd4000)
libnsl.so.1 => /lib/libnsl.so.1 (0xb6fc0000)
Is it correct ? Is it normal that gdal-grass doesn't appear ?
Y.
PS : is it the right list to post this problem ?
--
Yves Jacolin
---
http://yjacolin.gloobe.org
More information about the Gdal-dev
mailing list