wmgeolab / geoContrast

Data to support the comparison tool for geoBoundaries
2 stars 1 forks source link

Matching intersection error #32

Open karimbahgat opened 2 years ago

karimbahgat commented 2 years ago

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: