On Feb 23, 2009, at 9:47 PM, <grass-dev-request@lists.osgeo.org> wrote:
Date: Tue, 24 Feb 2009 00:38:04 -0000
From: "OSGeo4W" <trac_osgeo4w@osgeo.org>
Subject: [GRASS-dev] Re: [osgeo4w] #37: grass: wxpython gui issues
Cc: osgeo4w-trac@lists.osgeo.org
Message-ID: <056.4d818a4f221566f1382d068e0ccc6441@osgeo.org>
Content-Type: text/plain; charset="utf-8"#37: grass: wxpython gui issues
----------------------+-----------------------------------------------------
Reporter: jachym | Owner: osgeo4w-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone:
Component: Package | Version:
Resolution: | Keywords: GRASS
----------------------+-----------------------------------------------------
Comment (by hamish):Replying to [comment:24 hamish]:
if you click "browse EPSG codes", you get an error that the
file can't be found. If you browse for the EPSG file, the
path becomes `C:/OSGeo4W/share/proj/epsg` and then it all
works: ie the nice code table browsing, searching, & grabbing.Replying to [comment:25 marisn]:
Path in Tcl/Tk is taken from env variable: GRASS_PROJSHARE that
is set during compilation(?). Make it correct on Windows and
there will be no error messages.usually set in ./configure with --with-proj-share=/usr/share/proj
or so. I think that only sets the path for the EPSG codes browser/
search GUI; g.proj uses the PROJ4-linked version regardless of what you
set that path to. Not sure if things have changed though.Hamish
The GUI parses PROJ_SHARE to get the path.
Michael