[GRASSLIST:1528] Re: r.in.tiff sefault

[J. Simon Goodall]

Yes, r.in.tiff is segfaulting inmediately, my config is;

Slack 7.1
grass5.0beta11 compiled from source
latest libtiff, tiff-v3.5.6-beta

Guess I'm one of the only ones with the problem, r.in.tiff must be used
extensively.

Cheers,


Simon.

"Eric G. Miller" wrote:

> On Tue, Feb 27, 2001 at 01:46:48PM -0300, J. Simon Goodall wrote:
> > Hello list,
> >
> > Having problems with r.in.tiff, got the latest tiff libraries. latest
> > grass5.0beta11 and when I run
> >
> > $r.in.tiff
> > Segmentation fault
> >
> > Any ideas where the problem lies? via tktclgrass it doesn't work either
> > ( with input output options). I'm really wanting r.in.arctiff, it does
> > not seem to be around in 5.0beta11, has that been removed?
>
> r.in.arctiff always just called r.in.tiff.  Handling of TIFF world files
> was merged into r.in.tiff.  Unfortunately, r.in.tiff is quite buggy.  Am
> I understanding that it is segfaulting immediately?  My experience has
> been it only segfaults with certain types of TIFF files.  You may try
> using r.in.gdal.  However, I haven't had good like with its handling of
> the TIFF world files -- it seems to prefer GeoTIFF files that have
> projection information encoded in their "directory".  It will still get
> the file in, but without georeferencing info.  It's possibly to
> calculate tie-points fairly easily for i.rectify from the TIFF world
> file.  However, this is less than an ideal way...
>
> --
> Eric G. Miller <egm2 at jps.net>

--
J.Simon Goodall, Lic. Ea.Viamonte, C.C.8, 9420 Río Grande, TDF, Argentina
te:54.2964.430.861 fx:422.008 mob:155.69148 e-mail:sgoodall at global.com.ar