jiayuasu opened a new pull request, #3246:
URL: https://github.com/apache/sedona/pull/3246

   ## 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 `[GH-XXX] my subject` format. Part of 
#3243.
   
   ## What changes were proposed in this PR?
   
   - Implement top-level `geopandas.overlay` and `GeoDataFrame.overlay` with 
`intersection`, `difference`, `identity`, `symmetric_difference`, and `union` 
modes.
   - Keep geometry rows distributed through Sedona spatial joins, cluster-side 
mask aggregation, and native geometry expressions. The implementation performs 
one bounded input-metadata aggregation and does not collect geometry rows or 
use Python row UDFs.
   - Match GeoPandas schema, suffix, index, validity, geometry-family, CRS, 
SRID, and nullable-dtype behavior, including empty and disjoint inputs.
   - Document the intentional distributed-execution differences for warnings, 
stable nullable schemas, output ordering, and JTS versus GEOS invalid-polygon 
repair.
   
   ## How was this patch tested?
   
   - Ran the complete overlay test module with Python 3.9 and GeoPandas 1.0.1: 
25 passed.
   - Ran the GeoPandas 1.1.3 identity, dtype, inactive-geometry, and 
NumPy-boolean compatibility subset: 8 passed.
   - Verified native spatial-join plans contain no Cartesian product or Python 
evaluation nodes.
   - Ran the repository commit hooks successfully.
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I have updated the English and Chinese GeoPandas API 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to