chay0112 commented on issue #2504: URL: https://github.com/apache/sedona/issues/2504#issuecomment-3534307301
@petern48 QQ: In GeoPandas, the force_3d function accepts both scalar and array-like values for the Z coordinate, allowing users to specify a different Z value for each geometry. However, since Sedona uses Spark SQL under the hood, does it make sense to support array-like Z values in this context? Specifically, can Sedona's Spark SQL backend handle per-row Z values, or should we only support scalar Z values for all geometries in the series? -- 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]
