You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of raster_to_vector can cause quite a few problems in the output polygons that make them unusable for further processing. This is known problem that is usually solved by using iso lines.
Perfectly parallel lines and polygons that touch perfectly aligned can cause some issues like considering polygons inside out, or unable to calculate overlaps.
When taking iso-lines (or marching squares) tent to have less of those issues. Also they weight less.
I would propose a threshold argument: raster_cube.raster_to_vector(threshold=800)
For binary images, it would allow us to do: gaussian_blur(raster_cube, range=0.2).raster_to_vector(threshold=0.5) (A method used by ITK-Snap)
Downsides for doing this on binary images are that it would be less precise and that some might say that it is not true to the original data. But the differences are mostly on sub-pixel proportions.
The current implementation of raster_to_vector can cause quite a few problems in the output polygons that make them unusable for further processing. This is known problem that is usually solved by using iso lines.
cc @EmileSonneveld
The text was updated successfully, but these errors were encountered: