If digitising boundaries, then using 'remove vertex' to delete some of a
boundary, vertex-by-vertex... If I kept going and removed all the
vertexes (instead of the correct way of using 'delete
point/line/boundary'), it was possible to end up with some leftovers..
I could see a lone red cross on the v.digit screen (meaning, node(1
line) ) that I could not select to move, add, delete, anything... no
matter what my zoom.
This errant node did not show in the GRASS map view of the vector in
question, only in v.digit.
Using v.clean 'found' and removed this errant node (using the rmline
option) and I checked the vector info of the 'dirty' versus 'clean'
vectors to see nothing else had been upset.
It was an accident, I thought I'd selected the 'delete' tool...
but interesting, nonetheless
If digitising boundaries, then using 'remove vertex' to delete some of a
boundary, vertex-by-vertex... If I kept going and removed all the
vertexes (instead of the correct way of using 'delete
point/line/boundary'), it was possible to end up with some leftovers..
I could see a lone red cross on the v.digit screen (meaning, node(1
line) ) that I could not select to move, add, delete, anything... no
matter what my zoom.
This errant node did not show in the GRASS map view of the vector in
question, only in v.digit.
Using v.clean 'found' and removed this errant node (using the rmline
option) and I checked the vector info of the 'dirty' versus 'clean'
vectors to see nothing else had been upset.
It was an accident, I thought I'd selected the 'delete' tool...
but interesting, nonetheless
2011/1/7, Shane Litherland <litherland-farm@bigpond.com>:
> Hi again,
>
> another little thing I found by accident,
>
> If digitising boundaries, then using 'remove vertex' to delete some of a
> boundary, vertex-by-vertex... If I kept going and removed all the
> vertexes (instead of the correct way of using 'delete
> point/line/boundary'), it was possible to end up with some leftovers..
>
> I could see a lone red cross on the v.digit screen (meaning, node(1
> line) ) that I could not select to move, add, delete, anything... no
> matter what my zoom.
>
> This errant node did not show in the GRASS map view of the vector in
> question, only in v.digit.
>
> Using v.clean 'found' and removed this errant node (using the rmline
> option) and I checked the vector info of the 'dirty' versus 'clean'
> vectors to see nothing else had been upset.
>
> It was an accident, I thought I'd selected the 'delete' tool...
> but interesting, nonetheless
>
> regards,
> shane.
>
> _______________________________________________
> grass-user mailing list
> grass-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
If digitising boundaries, then using 'remove vertex' to delete some of a
boundary, vertex-by-vertex... If I kept going and removed all the
vertexes (instead of the correct way of using 'delete
point/line/boundary'), it was possible to end up with some leftovers..
I could see a lone red cross on the v.digit screen (meaning, node(1
line) ) that I could not select to move, add, delete, anything... no
matter what my zoom.
This errant node did not show in the GRASS map view of the vector in
question, only in v.digit.
Using v.clean 'found' and removed this errant node (using the rmline
option) and I checked the vector info of the 'dirty' versus 'clean'
vectors to see nothing else had been upset.
It was an accident, I thought I'd selected the 'delete' tool...
but interesting, nonetheless
Hello Maciek,
it wouldn't change a lot, as this bug is also present in 6.5. It's
just a corner case. Nobody has been doing such strange thing before
and thus it has went unnoticed for years.
Shane, thanks for report. I will fix it someday (hopefully for 6.4.2).
Maris.
2011/1/9, Maciej Sieczka <msieczka@sieczka.org>:
W dniu 08.01.2011 06:01, Shane Litherland pisze:
Hi Maris,
Have braved my first attempt at filing a bug report, and appear to have
put enough together to generate a ticket
Ticket #1256
leftover node when deleting boundaries vertex-by-vertex
If digitising boundaries, then using 'remove vertex' to delete some of a
boundary, vertex-by-vertex... If I kept going and removed all the
vertexes (instead of the correct way of using 'delete
point/line/boundary'), it was possible to end up with some leftovers..
I could see a lone red cross on the v.digit screen (meaning, node(1
line) ) that I could not select to move, add, delete, anything... no
matter what my zoom.
This errant node did not show in the GRASS map view of the vector in
question, only in v.digit.
Using v.clean 'found' and removed this errant node (using the rmline
option) and I checked the vector info of the 'dirty' versus 'clean'
vectors to see nothing else had been upset.
It was an accident, I thought I'd selected the 'delete' tool...
but interesting, nonetheless
Hello Maciek, it wouldn't change a lot, as this bug is also present
in 6.5. It's just a corner case. Nobody has been doing such strange
thing before and thus it has went unnoticed for years.
Shane, thanks for report. I will fix it someday (hopefully for
6.4.2).
Shane,
FWIW - I was referring to reporting an testing habbits in general :).
Hello Maciek, it wouldn't change a lot, as this bug is also present
in 6.5. It's just a corner case. Nobody has been doing such strange
thing before and thus it has went unnoticed for years.
Shane, thanks for report. I will fix it someday (hopefully for
6.4.2).
Shane,
FWIW - I was referring to reporting an testing habbits in general :).
Hello Maciek, it wouldn't change a lot, as this bug is also present
in 6.5. It's just a corner case. Nobody has been doing such strange
thing before and thus it has went unnoticed for years.
Shane, thanks for report. I will fix it someday (hopefully for
6.4.2).
Shane,
FWIW - I was referring to reporting an testing habbits in general :).
trust me to do something strange with otherwise healthy software
... that dangerous stage where I think I know enough to use it but don't
really (i.e. brashly clicking on tool icons without checking what tool
i've clicked on...)
Regards,
Shane.
On Sun, 2011-01-09 at 20:00 +0200, Maris Nartiss wrote:
Hello Maciek,
it wouldn't change a lot, as this bug is also present in 6.5. It's
just a corner case. Nobody has been doing such strange thing before
and thus it has went unnoticed for years.
Shane, thanks for report. I will fix it someday (hopefully for 6.4.2).
Maris.
2011/1/9, Maciej Sieczka <msieczka@sieczka.org>:
> W dniu 08.01.2011 06:01, Shane Litherland pisze:
>> Hi Maris,
>>
>> Have braved my first attempt at filing a bug report, and appear to have
>> put enough together to generate a ticket
>>
>> Ticket #1256
>> leftover node when deleting boundaries vertex-by-vertex
>>
>> hope it's of help...
>
> Shane,
>
> 6.4.0 RC6 is several months old.
>
> Please try installing and veryfing your issues against the newest stable
> release candidate - http://grass.osgeo.org/grass64/binary/linux/snapshot/.
>
> If impossible, please at least try the 6.4.0 final Ubuntu package from
> https://launchpad.net/~ubuntugis/+archive/ubuntugis-unstable/.
>
> Maciek
>
>>
>> -shane.
>>
>> On Fri, 2011-01-07 at 12:49 +0200, Maris Nartiss wrote:
>>> Open a bug report with exact step-by-step how to reproduce this issue.
>>> http://trac.osgeo.org/grass
>>>
>>> Maris.
>>>
>>>
>>> 2011/1/7, Shane Litherland<litherland-farm@bigpond.com>:
>>>> Hi again,
>>>>
>>>> another little thing I found by accident,
>>>>
>>>> If digitising boundaries, then using 'remove vertex' to delete some of a
>>>> boundary, vertex-by-vertex... If I kept going and removed all the
>>>> vertexes (instead of the correct way of using 'delete
>>>> point/line/boundary'), it was possible to end up with some leftovers..
>>>>
>>>> I could see a lone red cross on the v.digit screen (meaning, node(1
>>>> line) ) that I could not select to move, add, delete, anything... no
>>>> matter what my zoom.
>>>>
>>>> This errant node did not show in the GRASS map view of the vector in
>>>> question, only in v.digit.
>>>>
>>>> Using v.clean 'found' and removed this errant node (using the rmline
>>>> option) and I checked the vector info of the 'dirty' versus 'clean'
>>>> vectors to see nothing else had been upset.
>>>>
>>>> It was an accident, I thought I'd selected the 'delete' tool...
>>>> but interesting, nonetheless
>>>>
>>>> regards,
>>>> shane.
>>>>
>>>> _______________________________________________
>>>> grass-user mailing list
>>>> grass-user@lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>
>>
>>
>> _______________________________________________
>> grass-user mailing list
>> grass-user@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>
>
>
> --
> Maciej Sieczka
> http://www.sieczka.org
>
Just looking into newer version/s. Appreciate comment. I check the
standard ubuntu stable reps for versions, RC6 has been hanging in there
for a while... I generally have stuck with those ubuntu-reps versions
for ease-of-use etc, but will see what I can get from 'unstable' (seems
6.4.0-2 is an option) or, manually upgrade GRASS to on my box. Alas,
when I set this box up early 2010, the consensus seemed to be to stick
with 32-bit unless I really needed 64-bit... now GRASS 6.4.1 is only (?)
in 64-bit on the link you gave, so I'll either resort to the next-best
32-bit that I can find... or tackle the small drama of reinstalling
64-bit on my box... at the moment, the former is easier, but I know, I
know, at some point I'll have to be dragged kicking and screaming to
64-bit
... I could probably wade through compiling from source to get 6.4.1 as
32-bit if it's available but i'd be stretching my computing skills there
too..
Regards,
Shane.
On Sun, 2011-01-09 at 20:39 +0100, Maciej Sieczka wrote:
W dniu 08.01.2011 06:01, Shane Litherland pisze:
>>> Hi Maris,
>>>
>>> Have braved my first attempt at filing a bug report, and appear
>>> to have put enough together to generate a ticket
>>>
>>> Ticket #1256 leftover node when deleting boundaries
>>> vertex-by-vertex
>>>
>>> hope it's of help...
W dniu 09.01.2011 19:00, Maris Nartiss pisze:
> Hello Maciek, it wouldn't change a lot, as this bug is also present
> in 6.5. It's just a corner case. Nobody has been doing such strange
> thing before and thus it has went unnoticed for years.
>
> Shane, thanks for report. I will fix it someday (hopefully for
> 6.4.2).
Shane,
FWIW - I was referring to reporting an testing habbits in general :).
