[SERVER-10964] $geoIntersect fails when Polygon and LineString share an endpoint Created: 30/Sep/13 Updated: 09/Jul/16 Resolved: 24/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: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Insert a LineString with coordinates [ [1, 1], [2, 2] ]. Query with $geoIntersects and a Polygon with coordinates [ [ [ 0, 0 ], [ 0, 1 ], [ 1, 1 ], [ 1, 0 ], [ 0, 0 ] ] ]. Expect an intersection to be found, but nothing is returned. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 26/Oct/13 ] |
|
By "undefined" we mean it's not reliable whether they're included or excluded. I'll open a DOCS ticket. |
| Comment by Daniel Pasette (Inactive) [ 25/Oct/13 ] |
|
Seems like this should be documented. Is it always true that they're excluded or undefined? |
| Comment by A. Jesse Jiryu Davis [ 24/Oct/13 ] |
|
We don't define whether a polygon includes points on its boundaries; including or excluding a line that shares a vertex with a polygon in a $geoIntersects query are both acceptable behaviors. |