-
Notifications
You must be signed in to change notification settings - Fork 944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
turf-intersect: new test data with small intersection #1004
Conversation
Attempted to normalize the precision as described: #357 ; issue still persists. Maybe the larger geometry has too many points spanning the small box? |
Is there a function for checking this, like kinks? |
There's unlink polygon that might be useful. https://github.com/Turfjs/turf/blob/master/packages/turf-unkink-polygon/README.md |
|
Oh wait... the Inner & Outer were two polygon features in a FeatureCollection 🤦♂️ my bad. It does seem to be a valid GeoJSON according to https://www.mapbox.com/geojsonhint 🤔 ... looking into this. |
sorry guys, that typo was driving me crazy 🤣 |
@stebogit hilarious! |
@zbyte64 Made a quick patch fix for this issue, seems like the small inner polygon was throwing a topology error in JSTS, when truncating the precision to 4 and removing any duplicate nodes using Not an ideal result, but at least it stopped crashing... 👍 🤔 I couldn't send commits to your PR, so I opened a new one here: #1011 |
Temporary fix for PR #1004
Terrible. Its break all my code, cause i'm try to use turf in precision farming. |
Had an error in my app: 'Uncaught TopologyException: found non-noded intersection between LINESTRING and LINESTRING', issue #463 recommended creating a test case with the failure and that is what this pull request does. On this branch the intersect tests fail with REGEN=true . The added geojson file defines an intersect geometry only 60 inches wide. #297 (comment) indicates that JSTS has issues with resolution and may be the cause.