jiayuasu opened a new pull request, #3106: URL: https://github.com/apache/sedona/pull/3106
## 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 #3103 ## What changes were proposed in this PR? Bumps the `proj4sedona` dependency **0.1.0 → 0.1.1** and re-enables the 5 `CrsRoundTripComplianceTest` cases that were `@Ignore`'d against #3103. proj4sedona 0.1.1 fixes the CRS-serialization interop issues that made `RS_CRS` PROJ-string export non-idempotent for several projected CRSs: - WKT1 emits `TOWGS84` in human units (arc-seconds / ppm) - WKT / GeoTools method names are normalized to PROJ short codes on export (e.g. `Polar_Stereographic` → `stere`) - Canonical PROJ short codes are registry-owned - Polar Stereographic variant A/B selection is consistent across proj-string / WKT1 / WKT2 Re-enabled cases: `EPSG:5070` (Albers), `EPSG:28992` (Oblique Stereographic), `EPSG:27700` (OSGB TM), `EPSG:3577` (Australian Albers), `EPSG:3111` (Vicgrid LCC 2SP). Transforms were never affected — this was export idempotency only. ## How was this patch tested? Built the `common` module and the Spark CRS path against proj4sedona 0.1.1: - `common` full suite: **1145** tests, 0 failures / 0 errors / 0 skipped — including `CrsRoundTripComplianceTest` (**81**, all cases active, 0 skipped) - `CRSTransformProj4Test` (Spark `ST_Transform` → proj4sedona): **36**, 0 failures - `CRSTransformationTest` (Spark core CRS): **1**, 0 failures ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- 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]
