Rowan Winsemius

I knew those boolean modules would eventually come in handy!

Hi @mathildor So I think this is a quirk of visualising data in EPSG:3857 (Web Mercator) and the data being in EPSG:4326 (WGS84). Pulling your data into QGIS and visualising...

Thanks for this PR @pietervdvn So the main question mark here is what is the right output. Prior to v6 when we use `jsts` for performing the operation the returned...

I've done some looking at this. `polygon-clipping` doesn't actually return the full line that intersects along the edge, it's returning duplicate points. And it also doesn't return a point where...

G'day @stevage I don't see why not. You've been through the process of bundling an external dependency so feel free to give it another shot otherwise someone will get there...

I've had a bit of a go at this with rollup and [the dynamic-imports plugin](https://www.npmjs.com/package/@rollup/plugin-dynamic-import-vars). I seem to have some reasonably progress and I'm outputting a slim core bundle that...

Hi @devleaks `turf/lineOffset` is a bit hacky and has some known issues although that one is a bit surprising. The module probably needs a thorough overhaul.

Have had a quick look into this, it's nothing to do with mutation as even without the loop the result is incorrect, see https://runkit.com/rowanwins/5a84b60f0a657c00122a6e07 There is something funky going on,...

FYI have made good headway on refactoring this module to use the [algorithm here](http://geomalgorithms.com/a02-_lines.html), it's source code is way simpler and is producing the correct result. initial benchmark ```` \\...

This is a complex problem, see this [blog post](https://tmcw.github.io/2016/09/26/the-180th-meridian.html) for a fuller discussion. TurfJS is producing valid coordinates, however leaflet is not sure how to render features that cross the...