[GRASS-user] Native WinGRASS 6.4 RC5 g.proj failure
apachemaven0 at gmail.com
Wed Jun 17 06:29:29 EDT 2009
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
g.proj -c georef=d:\swilAlphaTIFF.tif
Trying to open with OGR...
Trying to open with GDAL...
2009/6/17 Hamish <hamish_b at yahoo.com>
> Micha wrote:
> > I installed GRASS on WinXP using the
> > setup file of the new version of WinGRASS from:
> > 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?
> > 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()
> (works for me)
> grass-user mailing list
> grass-user at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-user