Opened 8 years ago

Closed 8 years ago

#648 closed defect (fixed)

g.proj fails to create default region using Grass6.4 RC5

Reported by: voncasec Owned by: grass-dev@…
Priority: major Milestone: 6.4.0
Component: Python Version: 6.4.0 RCs
Keywords: g.proj, wxpython, g.region, UTM Cc:
CPU: x86-64 Platform: Linux


Using Location Wizard to create a new location fails. It does not prompt the user to define the default region for the new location and crashes.

Execution failed: 'g.proj -c proj4=+proj=utm +zone=14 +a=6378206.4 +rf=294.9786982 +no_defs +towgs84=-12.000,130.000,190.000 +to_meter=1.0 location=GrassDatabase?'

Details: Error: region for current mapset is not set run "g.region"

Traceback (most recent call last):

File "/usr/local/grass-6.4.0RC5/etc/wxpython/", line 404, in OnWizard?

gWizard = location_wizard.LocationWizard?(self, self.tgisdbase.GetValue?())

File "/usr/local/grass-6.4.0RC5/etc/wxpython/gui_modules/", line 1742, in init

success = self.OnWizFinished?()

File "/usr/local/grass-6.4.0RC5/etc/wxpython/gui_modules/", line 1903, in OnWizFinished?

success = self.CustomCreate?()

File "/usr/local/grass-6.4.0RC5/etc/wxpython/gui_modules/", line 2047, in CustomCreate?

p = gcmd.Command(cmdlist, stderr=None)

File "/usr/local/grass-6.4.0RC5/etc/wxpython/gui_modules/", line 358, in init

_("Error: ") + self.GetError?()))


Change History (2)

comment:1 Changed 8 years ago by LarryS

Component: wxGUIPython
Keywords: g.region UTM added
Priority: normalmajor
Summary: g.proj fails using Grass6.4 RC5 wxpythong.proj fails to create default region using Grass6.4 RC5

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.

comment:2 Changed 8 years ago by hamish

Resolution: fixed
Status: newclosed

fixed in r37983, r37979, r37981. (bug #654)

Note: See TracTickets for help on using tickets.