jiayuasu opened a new pull request, #3102: URL: https://github.com/apache/sedona/pull/3102
## 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 #3088 ## What changes were proposed in this PR? Bumps the `proj4sedona` CRS engine from `0.0.8` to `0.1.0` (single `proj4sedona.version` property in the root `pom.xml`, inherited by all modules). `0.1.0` completes the proj4js projection port — it now implements all 34 map projections, including **Polyconic** (`+proj=poly`), and overhauls CRS parsing/serialization (PROJ string, WKT1, WKT2, PROJJSON). This fixes #3088: `EPSG:5880` (SIRGAS 2000 / Brazil Polyconic) is a `+proj=poly` CRS. `0.0.8` lacked the Polyconic projection, so `ST_Transform` to/from `EPSG:5880` failed on the default proj4sedona path and only worked when `spark.sedona.crs.geotools=all` forced the GeoTools fallback. With `0.1.0` the transform succeeds natively, so the workaround is no longer required. ## How was this patch tested? - Added a regression test in `FunctionsProj4Test` transforming a Brasília point WGS84 ↔ `EPSG:5880` and asserting the projected coordinates and an exact round-trip. Reference values from pyproj 3.7.2 / PROJ 9.5.1 (`5653463.7342, 8243016.2220`). - Ran the full `FunctionsProj4Test` suite against the `0.1.0` artifact from Maven Central: 43/43 pass (42 existing + the new case), no regressions from the bump. - Verified `EPSG:5880` resolves offline through proj4sedona's built-in CRS provider (no network dependency introduced). ## 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]
