Opened 12 years ago

Last modified 3 years ago

#1013 new defect

Wxpython - vector georectification fails at i.group

Reported by: rchirgwin Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Vector Version: 6.4.2
Keywords: wxGUI georectify Cc:
CPU: All Platform: All

Description

Version: Grass 6.40RC5 Platform: OSX 10.5.8

When using the Python GUI to rectify a vector, georectification fails at i.group. The i.group module in the GUI is assuming that georectification is for rasters.

Steps:

  1. Select "vector" at first screen (along with source map location and mapset).
  2. At second screen, select "Create / Edit Group"
  3. Give group a name
  4. Click "Apply"
  5. Result below:

Error in command execution i.group Execution failed: "i.group group=test" Details: Error: no input raster map(s) specified

Richard Chirgwin

Change History (14)

comment:1 by hamish, 12 years ago

Component: defaultImagery
CPU: UnspecifiedAll
Keywords: i.group added
Milestone: 6.4.06.5.0
Platform: UnspecifiedAll
Version: unspecifiedsvn-releasebranch64

as its i.* name suggests i.group et al were designed for rectifying imagery rasters, not vectors. vectors are a modern slap-on hack only present in the GUIs. thus a solution should be carefully considered, but could be as simple as a new group/$GRP/VREF file. This is really an issue for grass7 IMO and for 6.x now we'll just have to figure out some work-around.

Hamish

comment:2 by cmbarton, 12 years ago

In both TclTk and wxPython, the georectification GUI uses GUI code to create a VREF file for vectors, and to parse the VREF file in the same way as is done for rasters.

Apparently, something has broken this functionality in the current version of the wxPython GUI. Unfortunately, I probably won't have time to look at it for a few weeks.

Michael

comment:3 by harrikoo, 9 years ago

Milestone: 6.5.0
Version: svn-releasebranch646.4.2

Unfortunately, this bug seems to be entering the next Debian Stable ("Wheezy"), as the current version in testing still has this bug: the "Georectify" tool cannot be used with vector maps, as it forces one to create an imagery group.

comment:4 by harrikoo, 9 years ago

Milestone: 6.5.0

in reply to:  3 ; comment:5 by neteler, 9 years ago

Milestone: 6.5.06.4.3

Bug confirmed for 6.4.svn (upcoming 6.4.3).

in reply to:  5 comment:6 by mmetz, 9 years ago

Replying to neteler:

Bug confirmed for 6.4.svn (upcoming 6.4.3).

Groups don't support vectors, the current support in the georectifier GUI is a hack specific to the georectifier GUI. A workaround is to create a group with a raster map, then click on the button 'Add vector map to group...' and continue, but vector rectification will probably fail at a later stage. Note that vector rectification similar to raster rectification exists only in GRASS 7, not in GRASS 6. For GRASS 6, the solution would be to disable vector support in the georectifier GUI and implement v.group (or g.group supporting both raster and vector maps) in G7.

Markus M

comment:7 by harrikoo, 9 years ago

Yes, it seems that the georectifier runs v.transform in the end, thus leaving the "rectified" map to the current location and mapset, not to the target location as one is made to expect. It is easy to move the new vector map directory to the desired lcation/mapset/vecto -directory.

All in all, the rectifier as it is in 6.4.2 is not useable; but it does contain working parts, and these could be used to implement a working solution.

in reply to:  7 comment:8 by mmetz, 9 years ago

Replying to harrikoo:

All in all, the rectifier as it is in 6.4.2 is not useable; but it does contain working parts, and these could be used to implement a working solution.

What do you mean with not usable? It works fine for raster maps.

Markus M

comment:9 by mmetz, 9 years ago

Component: ImageryVector
Keywords: wxGUI georectify added; i.group removed
Milestone: 6.4.37.0.0

comment:10 by harrikoo, 9 years ago

Sorry, I meant unuseable for vector rectification; for raster maps it works well.

Harri K.

comment:11 by martinl, 6 years ago

Milestone: 7.0.07.0.5

comment:12 by neteler, 6 years ago

Milestone: 7.0.57.0.6

comment:13 by neteler, 4 years ago

Milestone: 7.0.67.0.7

comment:14 by martinl, 3 years ago

Milestone: 7.0.77.6.2

Still relevant.

Note: See TracTickets for help on using tickets.