Closed mfbehrens closed 2 months ago
Thanks for doing a PR!
I would like to decide between our own Coordinate
struct or an external one. As mentioned, I prefer our own (for now). Or do you have any further plans for using geo
, like implementing polygonizing rasters? Another candidate would be geodesy's Coor2D, since georaster should have projection support once.
For that reason I designed it as a feature. It should be disabled by default, but if I use geo I can enable it. Then I get the dependency (that I have anyway) and get the conversions implemented. The same can also be done for geodesy. By default, you just get our own Coordinates struct, but if you enable one (or multiple) features manually, you can use them interchangeably.
Fix #4