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

   ## 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 
#2385. Closes #3168. Closes #3169.
   
   ## What changes were proposed in this PR?
   
   This PR adds distributed GeoSeries support for `is_ccw`, `interiors`, and 
`orient_polygons`.
   
   - `is_ccw` uses JTS ring-orientation semantics on the original coordinate 
sequence, including GeoPandas-compatible behavior for open lines.
   - `interiors` returns an object Series containing interior-ring lists while 
preserving MultiIndex metadata.
   - `orient_polygons` recursively orients polygonal members of nested geometry 
collections and preserves empty geometries, SRID, user data, and nulls.
   - Scalar and array expressions now retain their actual Spark schema, and 
`geom_type` strips its prefix with a native Spark expression.
   
   The implementations use native Spark and Sedona expressions without driver 
collection or Python UDFs. The line-orientation Catalyst bridge is internal and 
is not exposed as a new public SQL function.
   
   This is part of #2230.
   
   ## How was this patch tested?
   
   - `mvn -pl common -Dtest=FunctionsTest test` (326 tests passed)
   - `mvn -pl spark-shaded -am clean install -DskipTests`
   - Focused direct and GeoPandas-parity tests for all three methods and 
`geom_type` (8 tests passed)
   - Repository pre-commit hooks on all changed files
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I am adding a new API. I am using the [current SNAPSHOT version 
number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29)
 in `v1.9.1` format.
   


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