[GRASS-dev] [GRASS GIS] #776: wxvdigit not functional with 3D vector maps

#776: wxvdigit not functional with 3D vector maps
------------------------------+---------------------------------------------
Reporter: harrikoo | Owner: grass-dev@lists.osgeo.org
     Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Keywords: wxvdigit, vector | Platform: Linux
      Cpu: x86-32 |
------------------------------+---------------------------------------------
I just (20091006) updated from releasebranch_6_4, and found out, that
wxvdigit is not fully functional. Description:

If the vector map is 2D, there are no problems.

If the vector map is 3D (as shown by v.info), wxvdigit is not able to draw
really anything. Two symptoms:

1. Add a line, with 4 vertices. When ending the line, UI reports:
"Incorrect number of points (8)". The incorrect number seems always be
double the amount of vertices in the line.

2. Add a line, with 4 vertices. Instead of the line, wxdigit adds at least
8 lines, that start from all or some of the 4 vertices and continue
towards north-west ad infinitum.

Note, that I'm not thinking that the lines should have height or
z-coordinates. I'm just trying to draw simple 2D objects to a vector map,
which is originally 3D, with the expectation, that the new objects should
reside at z-level 0 (zero).

So it seems, that the wxvdigit module is not able to work with 3D vector
map. Note too, that the old v.digit module works perfectly and does not
have these problems.

Best,

Harri K.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/776&gt;
GRASS GIS <http://grass.osgeo.org>

#776: wxvdigit not functional with 3D vector maps
-----------------------+----------------------------------------------------
  Reporter: harrikoo | Owner: grass-dev@lists.osgeo.org
      Type: defect | Status: new
  Priority: normal | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Resolution: | Keywords: wxvdigit, vector
  Platform: Linux | Cpu: x86-32
-----------------------+----------------------------------------------------
Changes (by martinl):

* cc: grass-dev@lists.osgeo.org (added)

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/776#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#776: wxvdigit not functional with 3D vector maps
-----------------------+----------------------------------------------------
  Reporter: harrikoo | Owner: martinl
      Type: defect | Status: assigned
  Priority: normal | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Resolution: | Keywords: wxvdigit, vector
  Platform: Linux | Cpu: x86-32
-----------------------+----------------------------------------------------
Changes (by martinl):

  * owner: grass-dev@lists.osgeo.org => martinl
  * status: new => assigned

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/776#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#776: wxvdigit not functional with 3D vector maps
------------------------------+---------------------------------------------
Reporter: harrikoo | Owner: martinl
     Type: defect | Status: assigned
Priority: normal | Milestone: 6.4.4
Component: wxGUI | Version: 6.4.0 RCs
Keywords: wxvdigit, vector | Platform: Linux
      Cpu: x86-32 |
------------------------------+---------------------------------------------
Changes (by neteler):

  * milestone: 6.4.0 => 6.4.4

Comment:

Confirmed - when selecting the 3D map for editing, the map disappears from
the
wx digitizer display.

Test map: North Carolina data set
{{{
# set region to tile792 where we have both DEM and planimetry
g.region rast=el_D792_6m -p

# extract buildings
v.extract P079215 out=bldg_resid where="layer='BLDG_RESID_BL'"

# add height of the buildings
v.extrude -t bldg_resid out=bldg_resid_3d height=10 elev=el_D792_6m
v.info bldg_resid_3d
}}}

Then load bldg_resid_3d into the wxGUI and start to digitize in it.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/776#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>