jiayuasu opened a new pull request, #3191:
URL: https://github.com/apache/sedona/pull/3191

   ## 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 #3161
   
   ## What changes were proposed in this PR?
   
   - Bump the managed proj4sedona dependency from 0.1.2 to 0.1.4.
   - Add the exact EPSG:3021 to EPSG:3006 SQL regression from GH-3161. The test 
uses the PostGIS result reported in the issue and retains the existing 
one-metre projected-coordinate tolerance.
   - Convert the EPSG:2163 PROJJSON expected failure into a positive round-trip 
test and remove the obsolete failure helper.
   
   proj4sedona 0.1.4 restores the RT90 datum parameters used by EPSG:3021. This 
fixes the greater-than-180-metre error reported in GH-3161 while keeping the 
dependency update centralized in the existing root property.
   
   ## How was this patch tested?
   
   - Verified that the tested proj4sedona 0.1.4 jar is byte-for-byte identical 
to the Maven Central artifact (SHA-256 
`6617174bcdab31e2402ab32cd3f601e0c04a1fa99842aa6972f7fee8f71f274d`).
   - `mvn spotless:apply`
   - `mvn -pl common test` — 1,159 tests passed.
   - `mvn -pl common -Dtest=CrsRoundTripComplianceTest test` — 81 tests passed.
   - `mvn -f spark/common/pom.xml -Dspark=3.4 -Dscala=2.12 
-DwildcardSuites=org.apache.sedona.sql.CRSTransformProj4Test scalatest:test` — 
37 tests passed, including the GH-3161 regression.
   - `mvn -f spark/common/pom.xml -Dspark=3.4 -Dscala=2.12 
-DwildcardSuites=org.apache.sedona.sql.geoparquetIOTests scalatest:test` — 52 
tests passed.
   - `pre-commit run --all-files`
   - Verified the common and Spark dependency trees both resolve 
`org.datasyslab:proj4sedona:0.1.4`.
   
   ## Did this PR include necessary documentation updates?
   
   - No, this PR does not affect any public API so no documentation change is 
required.
   


-- 
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]

Reply via email to