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
Some boundary files, seemingly very large ones, abort early during the matching process. Looks like turf.js has trouble calculating the intersection for some shapes:
turf.min.js:88 Uncaught Error: Infinite loop when putting segment endpoints in a priority queue (queue size too big). Please file a bug report.
at t.value (turf.min.js:88)
at Object.intersection (turf.min.js:88)
at Object.sy [as intersect] (turf.min.js:88)
at similarity (internalSpatialWorker.js:33)
at self.onmessage (internalSpatialWorker.js:65)
Possible solutions:
Look into the intersection error itself if there's some obvious easy fix.
Try to get around the error, e.g. add a fallback that simplifies or fixes invalid geometries and then try again.
Even with the above, some shapes may be buggy and not able to be fixed. In those cases, skip over them and continue the matching process. Maybe add an error icon for those shapes that couldn't be calculated.
The text was updated successfully, but these errors were encountered:
Some boundary files, seemingly very large ones, abort early during the matching process. Looks like turf.js has trouble calculating the intersection for some shapes:
Possible solutions:
The text was updated successfully, but these errors were encountered: