Location wizard: region, UTM, search for EPSG

[helena]

Here are few Location Wizard issues - there may be more:

Apparently Universe is still there for UTM, see here ​http://lists.osgeo.org/pipermail/grass-dev/2009-March/042951.html

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.

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)

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?

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

At least the region issue and UTM search should be addressed before release, I believe

Helena

[hamish]

Universe -> Universal now done in all branches.

[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

[hamish]

Helena:

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

Michael:

--Not sure what is going on here. Can you give us more information to replicate it?

if I may take a wild guess: after selecting the ellipsoid try pressing the spacebar in the text box (then delete it) and see if the [Next] button lights up. It might just be a missing update notification.

Hamish

[cmbarton]

I've fixed items #3 and #4 above in develbranch_6. Please test. If it is OK, I'll backport to release branch and trunk.

Michael

[cmbarton]

I've fixed item 2 in develbranch_6 r39310. Please test. If OK, I'll backport.

Michael

[cmbarton]

I've fixed issue 1 above. If a location is created in an alternate GISDbase--i.e., one that is not the current one--the user is not offer a bogus chance to set the region extents (since this doesn't work and only generates an error).

Please test in develbranch_6 r39311. If OK, it can be backported to other branches.

Michael

[helena]

Michael,

thanks for the fixes - I tried it out and all items work at least for the examples that I tested. It was mostly about handling situations when the user does not make a correct selection. The search for EPSG codes now works great, I think the changes can be backported and the ticket closed as fixed, (I would still encourage others to try out the Location wizard with their favorite coordinate systems and try to make some typos too)

thank you,

Helena

[cmbarton]

I've backported these changes to develbranch (6.4) and trunk (7.0). Thanks for testing.

Michael