v.generalize's remove_small deletes wrong boundary
|Reported by:||hoeth||Owned by:|
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).
Change History (5)
comment:1 by , 13 years ago
|Component:||default → Vector|
|Version:||unspecified → 6.4.0 RCs|