On Feb 23, 2009, at 10:00 AM, <grass-dev-request@lists.osgeo.org> <grass-dev-request@lists.osgeo.org > wrote:
Date: Mon, 23 Feb 2009 08:28:23 -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.8a03d6f20996fc3bcddbd6f26d4a3b23@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:19 hamish]:
Hi, just attempting my first OSGeo4W GRASS install. Downloaded today.
packaging issues re. the wxpython GUI & epsg file:
wxPython Startup: [Create new location from EPSG code]
Error window:
{{{
"Unable to read EPSG codes: [Errno 2] No such file or directory:u'/c/OSGeo4W/share/proj\\epsg'
}}}
[Ok], Choose EPSG Code window comes up.Path to the EPSG-codes file: [c/OSGeo4W/share/proj\epsg]
[Browse], find it in the above location, [Ok]
Error window:
{{{
Unable to read EPSG codes: string index out of range
}}}
[Ok]but if I know the number and put it in, it accepts it and expands to the
correct +proj terms. (I tried # 4326 ll/wgs84)
So it's just the code browser which is unhappy in the end. But without
browsing to fix the "/c/...\epsg" to "C:\...\epsg" it gives me a Traceback
error in the DOS console (line 1567 KeyError: 4326).Martin:
Hopefully fixed in Changeset 35981 – GRASS GIS.
Hi,
similar problems in the Tcl/Tk GUI. From the startup screen:
{{{
Define new locations with ... [EPSG codes]Path to the EPSG-codes file: /c/OSGeo4W/share/proj/epsg
EPSG code number of projection __________ [Browse]
}}}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.
There is a PROJ_SHARE environment variable that is supposed to be set and put into init.sh at compile time. This variable can be set manually to point to the epsg directory. Then it should pop up automatically.
Michael