petern48 opened a new pull request, #2332: URL: https://github.com/apache/sedona/pull/2332
## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest/community/develop/) ## Is this PR related to a ticket? - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes #2331 ## What changes were proposed in this PR? Unfortunately, Sedona doesn't have the exact same behavior for geopandas spatial index queries. Geopandas return indices, while Sedona returns actual geometries. It wouldn't be easy to modify Sedona to return the indices, nor does it make much sense to imo, since indexes would be very slow to maintain in a distributed environment. - Additionally, this PR fixes an issue where we return [GeoData](https://github.com/apache/sedona/blob/e6e7c88bc8110bd10de36880ed8597313a3d8846/python/sedona/spark/utils/spatial_rdd_parser.py#L36) types from the RDD api for some of the functions. I don't see a need to keep the userData field, so I've converted so the user receives raw shapely geometries instead. This was already fixed in `query` in [this previous PR](https://github.com/apache/sedona/pull/2216), and this PR now applies it to the rest of the sindex functions. ## How was this patch tested? Added new tests ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- 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: issues-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
