-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is_valid
for all geometry types.
#1130
Comments
For |
Some time ago I tried to implement various validity checks for I think it implements most of the validity checks of GEOS as well as some other checks. The non-validity diagnostic messages could greatly be improved, and there is no functionality to attempt to repair the geometries. |
Somewhat related to #1120 |
As stated in the description of the geometry types (e.g.,
Polygon
,LineString
), validity is not enforced, but it is expected. While the validity requirements are clearly documented, there is no "canonical" way to check if your geometry adheres to the validity requirements.An example of when this would be desirable is loading polygons from a file. There is no guarantee that the file contained valid geometry, but once we check this, the algorithms should produce valid polygons.
Therefore, if checking validity is expensive, that is ok, since this should be a one-time cost.
Ideally this is supported by each geometry type separately, and also on
Geometry
.The text was updated successfully, but these errors were encountered: