jiayuasu opened a new issue, #3204:
URL: https://github.com/apache/sedona/issues/3204

   Part of #2230.
   
   ## Summary
   
   Complete three related GeoPandas geometry operations in one distributed 
batch:
   
   - `GeoSeries.maximum_inscribed_circle`
   - array-like distance support for `GeoSeries.dwithin`
   - `extend_to` support for `GeoSeries.voronoi_polygons`
   
   All geometry rows must remain distributed. Implementations must use native 
Spark/Sedona expressions and must not collect geometry data to the driver or 
use Python row UDFs.
   
   ## Requirements
   
   - `maximum_inscribed_circle` returns the radius line from the center to the 
boundary for each polygon or multipolygon, supports the GeoPandas tolerance 
argument, preserves index, CRS, and SRID, and matches GeoPandas handling of 
null, empty, and unsupported geometry inputs.
   - `dwithin` accepts a scalar distance or row-wise array/Series distances, 
validates lengths and numeric values consistently with GeoPandas, and preserves 
the existing geometry alignment behavior.
   - `voronoi_polygons` accepts `extend_to` and applies it through Sedona 
native Voronoi expressions while preserving row distribution, index, CRS, SRID, 
nulls, and empty geometries. `only_edges=True` remains outside this issue 
unless it can be supported without expanding the engine scope.
   - GeoDataFrame delegation works for all newly completed GeoSeries behavior.
   - Update API documentation to describe supported arguments and any 
intentional compatibility boundaries.
   
   ## Tests
   
   Add direct and GeoPandas parity tests covering scalar and row-wise 
arguments, named and duplicate indexes, null and empty geometries, 
geometry-family validation, CRS and Spark SRID preservation, GeoDataFrame 
delegation, argument validation, and execution plans without Python UDF nodes.


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