[GRASS-dev] Re: [GRASS GIS] #1257: Georectifier is broken

GRASS GIS trac at osgeo.org
Sun Jan 16 14:27:10 EST 2011


#1257: Georectifier is broken
--------------------------+-------------------------------------------------
 Reporter:  cmbarton      |       Owner:  grass-dev@…              
     Type:  defect        |      Status:  new                      
 Priority:  blocker       |   Milestone:  6.4.1                    
Component:  wxGUI         |     Version:  unspecified              
 Keywords:  georectifier  |    Platform:  MacOSX                   
      Cpu:  OSX/Intel     |  
--------------------------+-------------------------------------------------

Comment(by mmetz):

 Replying to [comment:9 cmbarton]:
 >
 > Helmut tried an alternate way of getting a target map that neither
 William nor I tried (image ending in 144249). When I replicate what he did
 in GRASS 6.5, I do not get a target map. The georectifier does not crash,
 but I get the same error as I reported above (and no target map).
 >
 The Georectifier works fine in Linux and Windows. But I encountered cross-
 platform problems with the wxpython AUI Manager when developing the
 Georectifier and had to include a few msys hacks. Maybe the AUI Manager
 behaves different again on Mac?

 Both the source and the target map display are buffered windows managed by
 an instance of the AUI Manager, just like the regular map display. The
 only difference is that the source map display is the center pane whereas
 - in the aui layout - the target map display the pane right of the center
 pane is.

 > self.height is not getting set. I'm not sure where this variable is
 coming from in the current version of the code.

 This is set in render.py, independent of the georectifier:

 https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/gui/wxpython/gui_modules/render.py#L383

 > Does this variable get used in any other code than the GUI? If not, then
 we need to look at how its value is being acquired. If yes, then it is the
 way it is being used in this case--perhaps switching locations (from xy
 back to target) is not working right.

 Problems with switching locations could be a starting point. The wxGUI
 sometimes overrides the settings of the georectifier and switches back to
 its original location/mapset, although nobody told it to do so... That's
 why i.rectify can no longer be executed in the main wxGUI Layer Manager
 Output window, but instead runs in the background. That is somehow related
 with the wxGUI layer Manager (not the georectifier) having its own private
 copy of GISRC which is a relatively recent change.
 >
 > I'm happy to do some testing, but don't have time right now to
 completely reverse engineer the new code and so could use help in this.
 >
 I hope that gives a bit more insight into the design of the new
 Georectifier. And there is still the manual:

 http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.GCP_Manager.html

 Markus M

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/1257#comment:10>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list