Michael Kirk
Michael Kirk
Alternatively we could yolo and just implement #15 😆 - I'm not sure what the capacity for boat rocking is.
🤷 I don't really know. I'm definitely more than zero serious. I'm pretty conservative, but the unnecessary Point/Coord distinction haunts me.
Even if this is a backwards compatible change, I think we should be clear about where we're heading before we adopt geo-traits into the geo public API. I'd assume the...
I also want to clarify: I don't think the bar should be that we migrate **every** single API to geo-traits before we accept **any** geo-traits code in geo. But I...
> I'm personally leaning toward option 1, with selective use of option 2 when benefit is clear That's my instinct. Thanks for laying out some alternatives.
With my work on #1216, I've been thinking about this too! I was imagining something kind of like what you've laid out here. Here's a POC with configurable haversine: b89c07e0...
Hello! Thanks for the contribution. I'm not familiar with this algorithm - does this exist in other popular toolkits (in other languages, e.g. jts/geos)?
>> I'm not familiar with this algorithm - does this exist in other popular toolkits (in other languages, e.g. jts/geos)? > > I have no idea if this exists in...
Semantic commits are wonderful. For example you can separate out small refactors from feature changes. A squashed commit is better than a ton of garbage commits. I don't want to...
Any update @kylebarron?