I just tried to create a new location for UTM Zone 10 using the wxPython
GUI. I could assign a name to the new location, specify defining it from a
list, and selecting 'utm' from that dialog box. However, on the next dialog
box where the zone is to be entered I cannot change the default '30' to
anything but '0'. Is this like the origins with 'll'?
Rich
Rich wrote:
I just tried to create a new
location for UTM Zone 10 using the wxPython
GUI. I could assign a name to the new location, specify
defining it from a
list, and selecting 'utm' from that dialog box. However, on
the next dialog
box where the zone is to be entered I cannot change the
default '30' to
anything but '0'. Is this like the origins with 'll'?
It's a known bug in the new wx location wizard.
https://trac.osgeo.org/grass/ticket/842
Michael & myself have been trying to fix it off-list, but to
be honest we are mostly stumped. (it works for him on Mac)
use the text-based location wizard (g.setproj), after starting
grass with "grass64 -text" or "grass64 -tcltk" from the command
line. your gui choice is sticky so reset it to wx with g.gui
later.
Hamish
On Tue, 29 Dec 2009, Hamish wrote:
It's a known bug in the new wx location wizard.
https://trac.osgeo.org/grass/ticket/842Michael & myself have been trying to fix it off-list, but to be honest we
are mostly stumped. (it works for him on Mac)
Ah!
use the text-based location wizard (g.setproj), after starting grass with
"grass64 -text" or "grass64 -tcltk" from the command line. your gui choice
is sticky so reset it to wx with g.gui later.
I just used a text editor on PROJ_INFO after accepting the default '30'.
Isn't it a wxPython spin-control widget? I've several of those in my
python approximate reasoning models.
Thanks for the response,
Rich
Rich wrote:
I just used a text editor on PROJ_INFO after
accepting the default '30'.
In that case you should double check that if(?) the PROJ_INFO
file has a +lon_0 set, it is set appropriately and not still
using the central longitude from Zone 30...
Isn't it a wxPython spin-control widget?
yes
I've several of those in my python approximate reasoning
models.
here's the code in question-
https://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/gui/wxpython/gui_modules/location_wizard.py#L798
I just spotted an attempt to deal with "weirdness", which may be
a clue-
https://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/gui/wxpython/gui_modules/location_wizard.py#L720
Michael:
I'm about to suggest that we scrap the spin box and return
to a simple text box (rather than the long pull-down) and
have it validate only values 1-60.
A spin box is the right tool for the job, so I'd like to keep
banging our heads against this one until we understand the
deeper cause (in the dev branch, not the release branch of
course).
Hamish
Hamish wrote:
> I just used a text editor on PROJ_INFO after
> accepting the default '30'.In that case you should double check that if(?) the PROJ_INFO
file has a +lon_0 set, it is set appropriately and not still
using the central longitude from Zone 30...
Also: the DEFAULT_WIND and WIND files contain a zone field.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn wrote:
Also: the DEFAULT_WIND and WIND files contain a zone field.
they would, as would (I think) any $MAPSET/cellhd/ files and
perhaps vector equivalent of cellhd, if not for this bug-
https://trac.osgeo.org/grass/ticket/842
Hamish
On Tue, 29 Dec 2009, Hamish wrote:
In that case you should double check that if(?) the PROJ_INFO file has a
+lon_0 set, it is set appropriately and not still using the central
longitude from Zone 30...
Hamish,
It doesn't:
name: Universal Transverse Mercator
proj: utm
datum: nad83
ellps: grs80
zone: 10
no_defs: defined
nadgrids: WO
here's the code in question-
https://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/gui/wxpython/gui_modules/location_wizard.py#L798I just spotted an attempt to deal with "weirdness", which may be
a clue-
https://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/gui/wxpython/gui_modules/location_wizard.py#L720
I'll look at these this coming weekend.
Rich