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
I've found a pathological case where the result of voronoi polygons contains LineStrings. See the example below, using shapely built against GEOS 3.12.1.
The last collection contains a Polygon and a tiny LineString, but the presence of the LineString causes failure when using coverage union later.
The issue is most likely caused by the floating point in those y coords and setting the precision grid resolves it (edit: it does in this case but not in others I've found). But I don't think that the algorithm should result in a LineString in any situation.
The text was updated successfully, but these errors were encountered:
I've found a pathological case where the result of voronoi polygons contains LineStrings. See the example below, using shapely built against GEOS 3.12.1.
The last collection contains a Polygon and a tiny LineString, but the presence of the LineString causes failure when using coverage union later.
The issue is most likely caused by the floating point in those y coords
and setting the precision grid resolves it(edit: it does in this case but not in others I've found). But I don't think that the algorithm should result in a LineString in any situation.The text was updated successfully, but these errors were encountered: