paleolimbot commented on issue #791: URL: https://github.com/apache/sedona-db/issues/791#issuecomment-4327960879
Thanks for opening! A high level I think we should add an expression API (we've already started one) and pure Python DataFrame layer. Then you can prototype this in a separate package to see if there is interest without adding maintenance surface to apache/sedona. We've talked about this offline, but I've always been skeptical of the GeoPandas compatibility layer. Most of the performance benefit from SedonaDB comes from rethinking existing workflows based on the relational model and the explicit non-goals are severe enough that it's not just an import change in most cases. Cookbook style documentation on how to accurately rewrite GeoPandas workflows into the relational model to help users and/or their AIs rethink their code would be a good project to tackle before this (because each cookbook entry is a mini design doc for a component). -- 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]
