petern48 commented on issue #224: URL: https://github.com/apache/sedona-db/issues/224#issuecomment-3407128589
If a function **already** has an implementation in `rust/geo`'s [algorithm](https://github.com/georust/geo/tree/8940db79aa6aa4ec8820d6328c68a2ae08ac8fdc/geo/src/algorithm) package, shouldn't implementing `geo` instead be the **same amount** of time/effort? If it's the same amount of effort, why not make them exist in the faster library first, so we don't need to duplicate our efforts implementing them in `geos` too? For example, we implemented ST_Centroid using `geo` in [this PR](https://github.com/apache/sedona-db/pull/33). And there seems to be [a lot more](https://github.com/georust/geo/tree/8940db79aa6aa4ec8820d6328c68a2ae08ac8fdc/geo/src/algorithm) that we can leverage (e.g concave_hull, simplify, etc). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
