jiayuasu opened a new pull request, #3253: URL: https://github.com/apache/sedona/pull/3253
## 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 #3252. Part of #2230. ## What changes were proposed in this PR? - Add `GeoDataFrame.estimate_utm_crs` by delegating to the active distributed geometry column. Geometry rows remain distributed; only a one-row emptiness probe and four aggregate bound values reach the driver. - Align `GeoDataFrame.set_crs` and `GeoSeries.set_crs` with GeoPandas: - accept the `epsg` keyword on `GeoDataFrame`; - default `allow_override` to `False`; - return the mutated object for `inplace=True`; - keep direct `.crs` assignment as an explicit override. - Preserve Sedona's former positional `GeoDataFrame.set_crs(crs, inplace, allow_override)` calls through a `FutureWarning` deprecation path so the signature alignment does not silently change existing 1.x behavior. - Fix `GeoDataFrame.from_arrow` to pass `to_pandas_kwargs` as one named dictionary on GeoPandas 1.1+, while omitting the keyword on the GeoPandas 1.0 default path. - Add regression coverage for signature defaults, EPSG assignment, in-place identity, legacy positional calls, CRS property assignment, distributed UTM estimation, and Arrow option forwarding. ## How was this patch tested? - Full GeoDataFrame test module on GeoPandas 1.1.3: 50 passed. - Focused compatibility tests on GeoPandas 1.0.1: 4 passed. - Focused compatibility tests on GeoPandas 1.1.3: 4 passed. - Existing GeoSeries `set_crs` and `estimate_utm_crs` parity tests: 2 passed. - Existing empty-dissolve CRS regression test: 1 passed. - All repository commit hooks passed, including Black, pyupgrade, Bandit, codespell, and license checks. - `git diff --check` and Python 3.9 syntax validation passed. ## Did this PR include necessary documentation updates? - Yes, I am adding a new API and used the current SNAPSHOT version, `v2.0.0`. - Yes, I updated the affected GeoPandas API docstrings, including the distributed execution notes and legacy positional-call deprecation. -- 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]
