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
This uses the same export hack that TurfJS uses, if that could possibly be related to the issue. I don't believe this is relevant, I tested a direct import with types ignored.
line is just some real world data that I happen to find an issue with. The original polygon that i noticed it with was much more complex, but I found the issue persisted with simplification of the polygon. Additionally, I removed ~2000 coordinates from the line to arrive at this where commenting some coords that definitely do not reside in the polygon will change the intersection result
The text was updated successfully, but these errors were encountered:
Stripped it back even further and removed z coord. Commenting any coord line will change the intersection result currently, it's down to 6 coordinates in the sample line.
Closing - debugger tool was helpful (thanks!). This was due to self intersections.
So, not a bug with this library but as noted in the linked turf issue I do believe this represents an unannounced breaking change to booleanIntersects as previously I don't think the algorithm used would have reported (or even checked?) self intersections.
Tracking down Turfjs/turf#2707
I traced it back to this lib.
Minimal repro: https://codesandbox.io/p/sandbox/turfjs-7-1-0-s8x273
This uses the same export hack that TurfJS uses, if that could possibly be related to the issue.I don't believe this is relevant, I tested a direct import with types ignored.line
is just some real world data that I happen to find an issue with. The original polygon that i noticed it with was much more complex, but I found the issue persisted with simplification of the polygon. Additionally, I removed ~2000 coordinates from the line to arrive at this where commenting some coords that definitely do not reside in the polygon will change the intersection resultThe text was updated successfully, but these errors were encountered: