petern48 commented on issue #539: URL: https://github.com/apache/sedona-db/issues/539#issuecomment-4269837905
I'd say the ideal solution is to add a new method upstream in the [geos-rust repo](https://github.com/georust/geos), and then use that in sedona-db. That's definitely more friction. It not only involves implementing the code and tests for the geos-rust bindings, but also waiting for their reviewers to respond to your PR, and possibly waiting for a release, etc. Also note, this is likely the least commonly used variant (I'm definitely not familiar with it, for example) I'd say if you're just looking for ways to contribute (rather than needing this particular function personally), I'd recommend picking other functions from the umbrella issue: https://github.com/apache/sedona-db/issues/174 since I'm sure there will be more functions with less friction. Though if you feel strongly about it. You can give it a shot! I would just caution that it's less likely to land as quickly as other methods. -- 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]
