Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.7.7
Affects Version/s: None
Component/s: Geo
Labels:
None

Backwards Compatibility:
Fully Compatible
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(2 related to)

Assignee:: Siyuan Zhou
Reporter:: Greg Studer (Inactive)
Participants:: Githook User, Greg Studer, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jul 09 2014 03:50:20 PM UTC
Updated:: Mar 06 2015 01:32:43 AM UTC
Resolved:: Sep 22 2014 06:51:53 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates