I have also tried creating a new mapset using g.mapset -c and I get an
error saying the region is invalid, and that g.region needs to be run
manually.
Running g.region manually would not resolve that issue (I had to copy
the WIND file from a different mapset to the new one to get it to
recognize the region settings).
GRASS GIS wrote:
#648: g.proj fails to create default region using Grass6.4 RC5
-----------------------+----------------------------------------------------
Reporter: voncasec | Owner: [email protected]
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Python | Version: 6.4.0 RCs
Resolution: | Keywords: g.proj, wxpython, g.region, UTM
Platform: Linux | Cpu: x86-64
-----------------------+----------------------------------------------------
Changes (by LarryS):
* keywords: g.proj, wxpython => g.proj, wxpython, g.region, UTM
* priority: normal => major
* component: wxGUI => Python
* summary: g.proj fails using Grass6.4 RC5 wxpython => g.proj fails to
create default region using Grass6.4 RC5
Comment:
Same issue here on Mac OS X Leopard (10.5.7 - 64 bit) using Kyngesburye
frameworks (he does not think it has anything to do with his build, per
se).
However, all methods of creating any UTM location fail, both GUIs and via
command line. DEFAULT-WIND just ends up with 'proj: 1, zone: <zone# here>'
without any region specs. I can create a geographic-based location, but
any UTM projected locations fail, whether using NAD27 or NAD83 and any
datum conversion. Also fails regardless of method of defining the UTM
setup, either via EPSG code, PROJ def, etc.
Location creation never gets to defining the region (as indicated by
previous poster), making an unusable location. I have not tested whether
other projections have the same issue.
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
