[SERVER-11293] Can't extract geo keys from object, malformed geometry? Created: 21/Oct/13 Updated: 04/Nov/13 Resolved: 31/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 2.4.6, 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Edgardo Vega | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Done | Votes: | 0 |
| Labels: | indexing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Operating System: | Linux |
| Steps To Reproduce: | Insert the following polygon into a collection without an index. "type": "Polygon", Then query the polygon using $geoIntersects. Everything works as expected. Then create an index on the field and add the same polygon you will get the following error "Can't extract geo keys from object, malformed geometry?" when inserted the same data. The polygon does pass the test on http://geojsonlint.com/ |
| Participants: |
| Description |
|
The same GeoJson polygon throws errors depending on if a 2dsphere geo index exists or not. Either the indexing need to be fixed not to throw this error or querying needs to have the same checks to throw the error to keep behavior the same. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 30/Oct/13 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This polygon includes longitudes less than -180, which we don't support. In summary,
In the near future we'd like to improve error messages to say why a polygon can't be parsed. But this particular ticket does not represent unexpected behavior. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by A. Jesse Jiryu Davis [ 24/Oct/13 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi vegaed. To help us diagnose this issue, could you please provide an example of a polygon that MongoDB thinks intersects with this one? I find that if I insert your example polygon and search for it with $geoIntersects, I can't construct a polygon that MongoDB thinks intersects it:
|