[GRASS-dev] i.rectify still chokes on @mapset

[Michael Barton]

On Apr 15, 2009, at 12:10 AM, Markus Neteler wrote:

> grep mapset gui/tcltk/gis.m/georect.tcl  | grep -v '#'
>            set cmd "i.target group=$GRMap::xygroup location=$currloc
> mapset=$currmset"
>            -title [G_msg "Select mapset of raster to georectify"] \
>    Button $row.a -text [G_msg "1. Select mapset"] \
>
> Why
> $GRMap::xygroup
> ?

This calls a variable (xygroup) that identifies the group file.

I think I see what the problem is, and I still don't think it is the  
GUI, especially be cause it causes a problem in both TclTk and wxPython.

Sometime (recently??), i.rectify has been changed so that it now  
accepts map names as input; it used to only accept a group as input.  
The TclTk and wxPython GUI's only send a group to i.rectify, not a map  
or list of maps.

Isaac, take a look at the relevant group file and see if it has the  
mapsets appended to the map names AND see if it has incorrect  
information like mapsets appended twice. Then run i.rectfy with group  
input, not map input. Also, try i.rectify with a map input that does  
use @mapset. I'm betting that it chokes on the first at least and  
either i.group is making the group wrong or i.rectify has trouble with  
groups in which the @mapset is part of the group name.

A more general question Markus (or others) is which direction is  
i.rectify going now: inputting groups or just inputting maps? There  
has been off and on discussion about groups that I've only partly  
followed. I seem to remember that subgroups are now gone. It would  
simplify the GUI work some if we could skip the group creation and  
just rectify a map or list of maps. The group is there to rectify a  
batch of multiband imagery files. Is this still the way to go? Maybe  
we could just leave the more sophisticated way of running i.rectify  
(e.g., on groups) to the module itself and not worry about  
implementing groups in the GUI.

Michael