Opened 10 years ago

Closed 7 years ago

#647 closed defect (fixed)

v.generalize's remove_small deletes wrong boundary

Reported by: hoeth Owned by: grass-dev@…
Priority: normal Milestone: 6.4.0
Component: Vector Version: 6.4.0 RCs
Keywords: v.generalize Cc:
CPU: x86-64 Platform: Linux

Description

Running v.generalize method=remove_small on the boundaries in "working.ascii" and "broken.ascii" yields different results, even though the only difference between the two files is the order in which the boundaries are stored. For "working.ascii" only the small open boundary is removed, while for "broken.ascii" both boundaries are removed.

I observe this behaviour both in 6.3.0 and in 6.4.0RC5 (didn't try any other releases).

Attachments (2)

broken.ascii (1.4 KB) - added by hoeth 10 years ago.
broken.ascii -- v.generalize remove_small deletes both boundaries
working.ascii (1.4 KB) - added by hoeth 10 years ago.
working.ascii -- v.generalize remove_small deletes the small boundary

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by hoeth

Attachment: broken.ascii added

broken.ascii -- v.generalize remove_small deletes both boundaries

Changed 10 years ago by hoeth

Attachment: working.ascii added

working.ascii -- v.generalize remove_small deletes the small boundary

comment:1 Changed 10 years ago by hamish

Component: defaultVector
Keywords: v.generalize added
Version: unspecified6.4.0 RCs

comment:2 Changed 8 years ago by mmetz

The remove_small method has been removed because it was faulty. Working equivalents (that is, the original cleaning functions) are as before provided by v.clean.

Markus M

comment:3 in reply to:  2 Changed 7 years ago by mmetz

Resolution: fixed
Status: newclosed

v.generalize has been rewritten and fixed in all active branches. Closing as fixed.

Note: See TracTickets for help on using tickets.