When starting GRASS, as long as I point to an existing
GRASS GISDBASE it works fine. But if I try to set up a new
GISDBASE, new location and mapset (based on epsg codes) the
"location wizard" fails, popping up an error window (as in
the attached image).
this doesn't diminish the bug any, but what's wrong with two locations
in the same GISDBASE?
This bug is something of a show-stopper since without a
properly defined location GRASS will not start. Even if I
start GRASS with the command line and try to run g.proj -c
or g.setproj they also fail. So without jumping thru some
tricky hoops, editting PROJ_INFO, etc. , GRASS is unusable.
Now, if I run the OSGeo4W installer and get 6.4.0svn, these
problems do not appear.
the error message is from lib/gis/get_window.c when G_fopen_old()
fails.
I think I came across the same problem of the g.proj
the commond “g.proj -c georef=d:\swilAlphaTIFF.tif location=tset” works well in grass6.3 get some warning in grass6.4 6.4 RC5 :
(Wed Jun 17 18:27:31 2009)
g.proj -c georef=d:\swilAlphaTIFF.tif location=tset
Trying to open with OGR…
Trying to open with GDAL…
…succeeded.
ERROR: 要得到当前地图集未设置的范围
请运行 “g.region”
When starting GRASS, as long as I point to an existing
GRASS GISDBASE it works fine. But if I try to set up a new
GISDBASE, new location and mapset (based on epsg codes) the
“location wizard” fails, popping up an error window (as in
the attached image).
this doesn’t diminish the bug any, but what’s wrong with two locations
in the same GISDBASE?
This bug is something of a show-stopper since without a
properly defined location GRASS will not start. Even if I
start GRASS with the command line and try to run g.proj -c
or g.setproj they also fail. So without jumping thru some
tricky hoops, editting PROJ_INFO, etc. , GRASS is unusable.
Now, if I run the OSGeo4W installer and get 6.4.0svn, these
problems do not appear.
the error message is from lib/gis/get_window.c when G_fopen_old()
fails.
I installed GRASS on WinXP using the
setup file of the new version of WinGRASS from:
[http://grass.osgeo.org/grass64/binary/mswindows/native/](http://grass.osgeo.org/grass64/binary/mswindows/native/)
When starting GRASS, as long as I point to an existing
GRASS GISDBASE it works fine. But if I try to set up a new
GISDBASE, new location and mapset (based on epsg codes) the
"location wizard" fails, popping up an error window (as in
the attached image).
this doesn't diminish the bug any, but what's wrong with two locations
in the same GISDBASE?
Well, nothing of course. But a GISDBASE with no location is certainly a problem
This bug is something of a show-stopper since without a
properly defined location GRASS will not start. Even if I
start GRASS with the command line and try to run g.proj -c
or g.setproj they also fail. So without jumping thru some
tricky hoops, editting PROJ_INFO, etc. , GRASS is unusable.
Now, if I run the OSGeo4W installer and get 6.4.0svn, these
problems do not appear.
the error message is from lib/gis/get_window.c when G_fopen_old()
fails.
Which means that the WIND or DEFAULT_WIND are not being set up right.
(works for me)
What I did to double check the problem was to temporarily rename .grassrc to something else, then try to start WinGRASS. With no .grassrc it begins the setup grass database and location routine, and then, after I choose an epsg code for the CRS, I get the failure.
