[GRASSLIST:6158] DEM imports to Grass - missing libproj.so

[John Doucette]

I have run gdalinfo for the dem I am trying to import.  gdalinfo reports
that it is "unable to load PROJ.4 library (libproj.so), creation of
OGRCoordinate transformation failed."

I don't know where libproj.so is susposed to be or when it would have been
installed.  After updating my search database (updatedb) I cannot find
libproj.so.

Anybody know anything about libproj.so and why gdal wants it?

Hopefully,
John Doucette



----- Original Message -----
From: "John Doucette" <doucettj at gbis.com>
To: "Glynn Clements" <glynn.clements at virgin.net>
Cc: <grasslist at baylor.edu>
Sent: Tuesday, April 29, 2003 11:03 PM
Subject: [GRASSLIST:6154] Re: DEM imports to Grass


> > If you have no idea regarding the format, posting more details (e.g.
> > file names or the URL) might result in someone recognising it.
>
>
> I am using  the Big_Bald mountain dems for White Pine County, Nevada from
> the following link.
>
>
> http://data.geocomm.com/dem/demdownload.html
>
> which is a part of www.geocomm.com
>
> ----- Original Message -----
> From: "Glynn Clements" <glynn.clements at virgin.net>
> To: "John Doucette" <doucettj at gbis.com>
> Cc: <grasslist at baylor.edu>
> Sent: Tuesday, April 29, 2003 2:55 PM
> Subject: Re: [GRASSLIST:6152] DEM imports to Grass
>
>
> >
> > John Doucette wrote:
> >
> > > I am unsure how to import DEM's into Grass.
> >
> > It depends upon the format.
> >
> > > I have been trying to use DEM's from Data Depot for US topomap areas.
I
> am
> > > trying to use r.in.gdal which (in man pages) says it can import USGS
> ascii
> > > DEM's or SDTS format. When I try either of these it get an
"Unrecognized
> > > format" error.  What the heck?
> > >
> > > I know that I have somehow gotten a DEM into Grass in the past but
don't
> > > remember how.
> > >
> > > Can anyone give me a clue?
> >
> > As well as the formats which GDAL supports, raw binary DEMs (e.g.
> > GTOPO30) can be imported with r.in.bin.
> >
> > If you have no idea regarding the format, posting more details (e.g.
> > file names or the URL) might result in someone recognising it.
> >
> > --
> > Glynn Clements <glynn.clements at virgin.net>
> >
>
>