Thanks, Paul. g.proj -c creates the location perfectly. I confirmed the proj
paramters from within the new location:
g.proj -p
-PROJ_INFO-------------------------------------------------
name : Stereographic
proj : stere
a : 6378137
es : 0.006694380022900787
lat_0 : 46.5
lon_0 : -66.5
k : 0.999912
x_0 : 2500000
y_0 : 7500000
towgs84 : 0,0,0,0,0,0,0
no_defs : defined
-PROJ_UNITS------------------------------------------------
unit : metre
units : metres
meters : 1
So that's odd. Anyway, I'll use this as a workaround for the future. Thanks
again.
~ Eric.
-----Original Message-----
From: Paul Kelly
To: Patton, Eric
Cc: Maciej Sieczka; grass-dev@grass.itc.it
Sent: 10/13/2006 2:00 PM
Subject: Re: [GRASS-user] RE: [GRASS-dev] Can't create locations using EPSG
codes
Hello Eric
On Fri, 13 Oct 2006, Patton, Eric wrote:
One thing that I just noticed is that my epsg file isn't in the
standard
location as the default path of /usr/local/share/proj/epsg given in
the
Grass startup screen. My epsg is in /usr/share/proj/epsg - but I
specify
this path to the startup window, so it should just get passed
verbatim.
Could that make any difference?
This file isn't used for anything unless you select to browse EPSG codes
(which simply displays this file). So should make no difference even if
it
isn't there.
Does the start-up GUI hide error messages? Can you try it from the
command-line and post what you type and what happens? Try something
like:
g.proj -c location=newloc proj4=+init=epsg:XXXX
Paul