looking for something bigger to work on in sedona-db

[CaptainAni187]

hi @paleolimbot @jiayuasu ....

I've had a couple of fixes merged in sedona-db recently (#1408 for the empty points in collections, #1410 for the CREATE DATABASE fallback) and I've really enjoyed working in the codebase. I'd like to keep going and take on something a bit bigger.

I already asked on #1459 about moving ST_Union_Agg / ST_Intersection_Agg over to GEOS.... happy to do that if you're ok with it, or anything else you'd rather have someone pick up. If there's an issue you could assign me, I'll take it.

thanks!

[paleolimbot]

We're glad you're here and enjoying working on the code base! We're aware that because many of us work for the same company, some things appear to move and/or change quickly.

One of the things we've had a hard time prioritizing is completing the list of functions ( apache/sedona-db#174 ). Each function has a unique set of challenges, but we have accumulated a nice set of tools to test and implement many of them.

#1459 is possibly a good fit; however, one of us might get to that one first because it's come up in some of our workloads. Also, I would reccomend implementing a scalar function or two before attempting an aggregate function!

Something more "project"-like might be to implement a GeoPackage reader like the FlatGeobuf reader that's getting added currently. I'd recommend doing that after at least one scalar function!

[CaptainAni187]

thanks, that's really helpful.... makes sense to do a scalar one first. I'm thinking ST_IsPolygonCW / ST_IsPolygonCCW from #174 since nobody seems to have picked those up yet, then ST_Union_Agg after that.

the GeoPackage reader sounds really interesting too, I'll look at the FlatGeobuf one and come back to it once I've got a scalar function in.