Opened 16 years ago
Closed 12 years ago
#647 closed defect (fixed)
v.generalize's remove_small deletes wrong boundary
| Reported by: | hoeth | Owned by: | |
|---|---|---|---|
| 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)
Change History (5)
by , 16 years ago
| Attachment: | broken.ascii added |
|---|
by , 16 years ago
| Attachment: | working.ascii added |
|---|
working.ascii -- v.generalize remove_small deletes the small boundary
comment:1 by , 16 years ago
| Component: | default → Vector |
|---|---|
| Keywords: | v.generalize added |
| Version: | unspecified → 6.4.0 RCs |
follow-up: 3 comment:2 by , 13 years ago
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 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
v.generalize has been rewritten and fixed in all active branches. Closing as fixed.
broken.ascii -- v.generalize remove_small deletes both boundaries