You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that the second polygon in Area does not describe a whole inside the first polygon since the upper/lower latitude is the same. So instead of cutting a whole into the first polygon (rectangle), its cuts it into two separate rectangles. This is not supported by the S2 library which we use internally. With a small adaptation to the coordinates of the second polygon it works as expected:
We can (and will) improve the documentation about these limitations and perhaps also improve the error messages, but otherwise we are not going change the current behavior, so I am closing this as won't fix.
Uh oh!
There was an error while loading. Please reload this page.
My Environment
Component, Query & Data
Affected feature: arango engine
AQL query (if applicable):
AQL explain (if applicable):
Dataset:
Size of your Dataset on disk:
Replication Factor & Number of Shards (Cluster only):
Steps to reproduce
Problem:
unable to get "true" result with GEO_INTERSECTS function
Expected result:
expect to get "True" boolean.
The text was updated successfully, but these errors were encountered: