Morgan Herlocker

I will give this a crack tomorrow. I will probably plug into [geojsonhint](https://github.com/mapbox/geojsonhint).

mapshaper does this, which I think is integrated into topojson (which is already a dependency of turf), so the features you are looking for may actually be pretty easy to...

Here is the new issue: https://github.com/morganherlocker/turf/issues/87

Same questions as @mourner for me, and one more. I definitely think this could be useful as a core module. What should the behavior be when a line partially slices...

@GerfriedC, perhaps helpful, I recently wrote up some notes in a gist for WSL users trying to run OSRM. I have tested this with a scratch build on Windows 10...

Try out the [docs for building the frontend](https://github.com/Project-OSRM/osrm-frontend#development). osrm-frontend uses [browserify](http://browserify.org/) to compile node.js to clientside JavaScript. The frontend code lives in the [src directory](https://github.com/Project-OSRM/osrm-frontend/tree/gh-pages/src). Try modifying and recompiling to...

Check out geojson-normalize and geojson-flatten. Running everything through both of these tends to smooth things out with highly variable input. ``` js geojson = normalize(flatten(geojson)) ```

@tmcw wrote up a [great post](http://www.macwright.org/2013/02/18/literate-jenks.html) a couple years ago describing a literate jenks classifier that I have used all over the place. The implementation is included in [simple-statistics](https://github.com/tmcw/simple-statistics/blob/master/API.md#jenksdata-number_of_classes).

Completely agree. I am using jsts very reluctantly at this point, as I have found it pretty challenging to debug and its size really hurts client-side viability (I personally only...

I have started porting jsclipper to node (the current implementation is heavily tied to the browser and contains a lot of code that optimizes it for various browsers). Minified, I...