#760: Location wizard: region, UTM, search for EPSG
---------------------+------------------------------------------------------
Reporter: helena | Owner:
[hidden email]
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Resolution: | Keywords: Location wizard
Platform: MacOSX | Cpu: OSX/Intel
---------------------+------------------------------------------------------
Comment (by cmbarton):
if startup has grassdata but I create location in tgrassdata using wizard
it tells me that I will need to change into tgrassdata but then it asks
whether I want region I say Yes and then I get Error in command execution
g.region because wizards g.region still looks into grassdata and tells me
that the location does not exist - it needs to look into tgrassdata for
the new location or skip the region creation in this case.
--Although it can create a location in another GISDBase, g.region and
g.proj run in the default GISDbase--i.e., the one you started in. So you
can't get region info from a location in another GISDbase folder (at least
not easily).
EPSG search works but if I type name North Carolina it picks up the first
one and moves on - would it be possible to select all that have North
Carolina in it and then the user selects one of them? Searches for
projection and for Elipsoid already do it, which is very nice (you give it
search for Lambert and you get all 3 that are there)
--I'm not sure how doable this is given the way that the EPSG file is
structured. However, it's worth looking into.
For the chose projection when you type UTM into projection code and click
Next nothing happens - this is because you should type utm so it is not
clear what to do next or what is wrong - maybe an error message that UTM
does not exist? to make the user scrolls down and looks for the correct
code?
--you mean it is not recognizing capitals? UTM vs utm?? This should be
easy to fix.
If I select datum with associated elipsoid and then pick up nad83 it again
does not do Next and it is not clear what is wrong
--Not sure what is going on here. Can you give us more information to
replicate it?
At least the region issue and UTM search should be addressed before
release, I believe
--I agree about the UTM issue. The region issue is best fixable (if at
all) by seeing if we can create an error message more specific to this
situation. That is, you can't set the region for a location that is in a
GISDbase that is not the current one.
Michael
--
Ticket URL: <
http://trac.osgeo.org/grass/ticket/760#comment:3>
GRASS GIS <
http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
