Paul Mach

I'm fine with adding that, but I am curious about your usecase.

sure, filter them out. But maybe your looking for something like https://github.com/mapbox/tippecanoe

The answer for your tool it to load the file for every request. The `layers.ProjectToTile`, `layers.Clip` and `layers.Simplify` commands modify the layer data. This is by design for performance reasons....

I don't plan on doing that. It's a big project and there is no way I have time for that.

Thank you, but this is already implemented in the `orb/geo` package where all "geo" type functions are located. Flat/euclidean stuff is located in `orb/planar`. https://github.com/paulmach/orb/blob/master/geo/distance.go#L26 For the "distance from" stuff....

Sure. A orb.Ring is just a slice/array. You can create it with 0, 1, 2, 3, 4... points. There is no validation. Not really sure what to do about it....

> FWIW, I see github.com/paulmach/orb as a general purpose geo lib, and github.com/paulmach/orb/geojson as an extension for handling standards-compliant geojson. > As such I would put all the 'geojson stuff'...

more specifically, do you mean geojson flatgeobuf?

I looked at flatgeobuf but don't see much documentation. I see a few lines for Specification in the readme and some flatbuffer files. I don't really understand how to pack...

I wasn't really happy with the API in go.geo. What kind of API are you thinking of. It gets weird because two line strings can intersect into nothing, a point,...