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 would expect either shape() to raise an error in both cases or to silently accept the invalid coordinate component and then fix in in the make_valid().
Right now geometries that allow the user initialize with a NaN are: Point, LineString, MultiPoint make_valid() fixes the error in all of these cases.
Geometries that raise a ValueError: Polygon, MultiLineString, MultiPolygon.
Steps to reproduce the problem.
See the example from the previous section.
Operating system
macOS Monteray 12.6.2 (21G320)
Shapely version and provenance
Shapely 2.0.4, installed from PyPI using pup
The text was updated successfully, but these errors were encountered:
Expected behavior and actual behavior.
Consider the following examples:
Result:
Result:
I would expect either
shape()
to raise an error in both cases or to silently accept the invalid coordinate component and then fix in in themake_valid()
.Right now geometries that allow the user initialize with a NaN are:
Point
,LineString
,MultiPoint
make_valid()
fixes the error in all of these cases.Geometries that raise a ValueError:
Polygon
,MultiLineString
,MultiPolygon
.Steps to reproduce the problem.
See the example from the previous section.
Operating system
macOS Monteray 12.6.2 (21G320)
Shapely version and provenance
Shapely 2.0.4, installed from PyPI using pup
The text was updated successfully, but these errors were encountered: