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

   ## 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. The PR name follows the `[GH-XXX] my subject` format.
   - Closes #3162.
   - Closes #3163.
   - Closes #3164.
   - Part of #2230.
   
   ## What changes were proposed in this PR?
   
   - Add distributed `GeoSeries.has_m` and GeoDataFrame delegation using native 
Sedona expressions. Mixed-dimensional GeometryCollections check all component 
points so their result matches GeoPandas.
   - Add distributed `GeoSeries.minimum_clearance_line` and GeoDataFrame 
delegation using `ST_MinimumClearanceLine`, while retaining the input SRID for 
degenerate geometries.
   - Add distributed `GeoSeries.constrained_delaunay_triangles` and 
GeoDataFrame delegation using `ST_TriangulatePolygon`. Empty inputs return an 
SRID-preserving empty GeometryCollection instead of reaching the JTS 
empty-polygon failure path.
   - Add direct edge-case, metadata, delegation, and version-gated GeoPandas 
parity tests.
   
   All three methods remain lazy and distributed; they do not collect geometry 
data to the driver or use Python row UDFs.
   
   ## How was this patch tested?
   
   - Ran focused direct and GeoPandas parity tests for all three methods: 6 
passed.
   - Ran the neighboring `has_z`, `delaunay_triangles`, and `minimum_clearance` 
direct and parity tests: 6 passed.
   - Ran the repository pre-commit hooks on all changed files.
   - Verified the three API examples against a local Spark session.
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I am adding new APIs using the current SNAPSHOT version, v1.9.1.
   - Yes, I added API docstrings, examples, return descriptions, and 
related-method references.
   


-- 
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