#647: v.generalize's remove_small deletes wrong boundary
---------------------+------------------------------------------------------
Reporter: hoeth | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: default | Version: unspecified
Keywords: | Platform: Linux
Cpu: x86-64 |
---------------------+------------------------------------------------------
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).
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`.