Michael Kirk

I think this would be a good addition! Some design thoughts: > Should we have a separate trait method for returning triangle indices? Do you mean _vertex_ indices? Otherwise I...

Do you mean something other than passing `--features "proj proj/bundled_proj"` / `--features "proj proj/pkg_config"`?

oh you're right. I never realized you couldn't do something like: ``` [dependencies] geo = { version = "*", features = ["proj", "proj/bundled_proj"] } #

Sorry for the slow response. I for one would love to see a comprehensive affine feature. Do you have a proposal for what the API would look like?

> convert a geo-type into a different geo-type The output type should always be the same as the input. A Linestring will never become a Point, right? > possibly in-place...

Cool! Just as a reminder, @rmanoka did a *somewhat* related investigation of intersection perf here: https://github.com/georust/geo/issues/649 It's a slightly different use case, but the findings might be relevant. In particular,...

Maybe https://github.com/georust/geo/issues/566? (lol not to just dump my wishlist on you or anything...)

Now that https://github.com/georust/geo/pull/829 is merged, we might get comparable perf via something like `a.relate(b).is_intersects()`

> from a first cut, use of relate introduces extreme perf regressions (900 %+ in some case) in our nice new boolean ops intersection benchmark suite… Do you still have...

Disclaimer that I've only given this a cursory look. There's a lot of noise in the diff from the upstream commits. re: the naming of `Coord` that you've proposed -...