Currently it's very hard to determine what the problem is when large shapes are invalid according to mongodb - geojsonlint helps somewhat, but in certain edge cases we're slightly more restrictive.
- is duplicated by
-
SERVER-15376 Improve error message for polygons with intersecting edges
- Closed
-
SERVER-14182 Improve Error reporting of invalid geo queries
- Closed
- is related to
-
SERVER-9401 GeoJSON Parser: Can't extract geo keys from object, malformed geometry?
- Closed
-
SERVER-13735 “Malformed geometry” error when creating a geosphere index for a valid MultiPolygon
- Closed
-
SERVER-14921 Pull S2 header dependencies from non-geo headers
- Closed
- related to
-
SERVER-17486 Crash when parsing invalid polygon coordinates
- Closed
-
SERVER-14467 Capture S2 debug log messages
- Closed