[GRASSLIST:4305] Re: r.in.gdal kap files

[Glynn Clements]

Kevin Slover wrote:

> I am attempting to import a Ver3.0 Kap file, and am getting an error:
> 
> ERROR 1: Failed to find required RGB/ or BSB/ keyword in header.
> 
> I did read that gdal does support ver 3.0 kap files.  I can see bsb in
> the header (bsb/na=).  I am using gdal 1.7, however, if I do a ldd on
> r.in.gdal, it is unable to locate libgdal.1.1.so.  Is this maybe the
> problem?

No. If r.in.gdal fails to locate libgdal, you would get a different
error. The above error indicates that r.in.gdal at least managed to
initialise.

Note that there are two ways in which r.in.gdal can be built. If the
--with-gdal configure switch is used, r.in.gdal is linked directly
against libgdal (this is the normal manner in which shared libraries
are used). Otherwise (without --with-gdal), r.in.gdal loads libgdal
dynamically (at run time), using the dlopen() function.

In the latter case, r.in.gdal won't have any dependency upon libgdal
(as far as ld-linux.so or ldd are concerned), so I assume that the
former case applies.

This suggests that libgdal is in $GISBASE/lib, but you didn't run
"ldd" from within a GRASS session.

The GRASS startup explicitly adds $GISBASE/lib to LD_LIBRARY_PATH, so
any libraries which are in that directory will be available within a
GRASS session (but probably not from outside of one).

[BTW, I don't know anything about Kap files, so I can't suggest what
the problem is; but I can tell that it isn't a simple library issue.]

-- 
Glynn Clements <glynn.clements at virgin.net>