leftover node when deleting boundaries vertex-by-vertex

[shaneL]

further to posting about this on grass-users mailing list, was advised to file bug (my first attempt, hope I get this right...)

to reproduce issue;

1. run v.digit (I am using defaul tcl/tk monitors in my ubuntu 10.04 install)

2. create a new vector 'node_issue', or can get same result in an existing vector.

3. choose from GUI 'boundary' tool, draw a boundary. I set options as 'no category' and not to add entry to table, though doubt this affects issue.

4. whether the boundary is closed or open after digitising, didn't affect the final result either

5. choose 'remove vertex' tool, and click on any vertex (start, end, or anywhere in the middle), and continue clicking on vertices, thereby deleting them, until you arrive at the last vertex remaining for the boundary.

6. it appears to be deleted, but then a red cross remains. red cross in v.digit settings means Node (1 line) for my install. this red cross only visible in v.digit. opening vector in map view of grass does not show it.

running v.info after digitising a boundary:

Number of points: 0 Number of areas: 1 Number of lines: 0 Number of islands: 1 Number of boundaries: 1 Number of faces: 0 Number of centroids: 0 Number of kernels: 0

running v.info after removing vertices and having 'red cross' remain:

Number of points: 0 Number of areas: 0 Number of lines: 0 Number of islands: 0 Number of boundaries: 1 Number of faces: 0 Number of centroids: 0 Number of kernels: 0

-this errant node can be removed using v.clean. I successfully used v.clean to remove such a node from a working vector without upsetting any of the other boundaries or centroids in the vector layer.

after running: v.clean input=node_issue@Lacebark output=node_issue_cleaned type=boundary tool=rmline

the v.info for the cleaned vector is:

Number of points: 0 Number of areas: 0 Number of lines: 0 Number of islands: 0 Number of boundaries: 0 Number of faces: 0 Number of centroids: 0 Number of kernels: 0

Hope this explanation is of use :-)

[marisn]

Fixed in r44914 for 6.5.

Candidate for backporting.

[martinl]

Reopen ticket, it's not fixed for given milestone.

[marisn]

Merged to 6.4.1 r45225