[GRASS-dev] Re: pj_transform problem: failed to load NAD27-83 correction file

Yann Chemin ychemin at gmail.com
Fri Oct 13 22:41:34 EDT 2006

After some more research...

the Proj 449 version has already the conus bin in /usr/share/proj/
along with nad27 and nad83 files.

PROJLIB was empty, export $PROJLIB=/usr/share/proj/ as mentioned in
proj website, no change. But this may not affect how Proj code is used
in GRASS, so...

...wondered if the configure of GRASS went wrong, but it says:
checking for location of External PROJ.4 includes...
checking for proj_api.h... yes
checking External PROJ.4 version... 449
checking for location of External PROJ.4 library...
checking for pj_get_def in -lproj... yes
checking for location of External PROJ.4 data files... /usr/share/proj
checking for /usr/share/proj/epsg... yes
checking for nad2bin... /usr/bin/nad2bin

So far so good... Just wonder if there is anything more in the
configure file to be set? Or should it be a proj recompile?

Anybody used a proj449 and NAD?


On 13/10/06, Yann Chemin <ychemin at gmail.com> wrote:
> Hi list,
> I am trying to make a program writing a latitude map. it works in a
> lat/lon projection, but the only non-ll mapset i have is Spearfish,
> and when testing on it, it returned this:
> pj_transform() failed
> cause: failed to load NAD27-83 correction file
> GRASS_INFO_ERROR(19542,1): Error in pj_do_proj
> How can i get through this problem? is it a problem in compilation of proj?
> thanks,
> Yann

Some Google Working rules:
*  Developers can switch teams and/or projects any time they want, no
questions asked; just say the word and the movers will show up the
next day to put you in your new office with your new team.
* There aren't very many meetings. I'd say an average developer
attends perhaps 3 meetings a week.
* Google has a philosophy of not ever telling developers what to work
on, and they take it pretty seriously.
* Google tends not to pre-announce. They really do understand that you
can't rush good cooking, you can't rush babies out, and you can't rush
software development.

More information about the grass-dev mailing list