petern48 commented on issue #2504: URL: https://github.com/apache/sedona/issues/2504#issuecomment-3536001820
Geopandas: `z : float | array_like (default 0)` Sedona: `ST_Force3D(geometry: Geometry, zValue: Double)` PostGIS (what Sedona generally tries to follow): `geometry ST_Force3D(geometry geomA, float Zvalue = 0.0);` Yeah, support array arguments isn't too common for SQL, and it's honestly slower for Sedona, since it requires a distributed shuffle + join (`_row_wise_operation()`). But we do have a convenient way to do it. Model it off the implementation of `.segmentize()`. I noticed a few bugs in `.segmentize()`, so I submitted [this PR](https://github.com/apache/sedona/pull/2507/files) to fix a few things. Here's [the link](https://github.com/petern48/sedona/blob/22bf0d73daccec0c1001847f60712007be02f135/python/sedona/spark/geopandas/geoseries.py#L1076-L1086) to the `.segmentize()` implementation in that PR. You'll likely need to copy over [this change](https://github.com/apache/sedona/pull/2507/commits/0f448a4d772ea55b969fb988b68d4e809859d7de) for lists to work properly or wait for that PR to get merged. Great Question! -- 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]
