DOC: update note for is_valid #1944
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 7024601812
💛 - Coveralls |
Comment on lines
+1013
to
+1014
| The validity test is meaningful only for `Polygons`, `LinearRings`, | ||
| and some `LineStrings`. Other geometry types always return ``True``. |
There was a problem hiding this comment.
Keep the reference to MultiPolygon here?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
is_validproperty is more complicated than the manual suggests. For instance, there are invalid LineString and LinearRing types. See other docs for PostGIS on the topic.For more info from GEOS, see
ValidationError.cppmessages (and their enums fromTopologyValidationError.h), andIsValidOpTest.cppfor examples of valid/invalid geometries.