szehon-ho opened a new pull request, #55525:
URL: https://github.com/apache/spark/pull/55525

   ### What changes were proposed in this pull request?
   
   This PR bumps Spark's embedded spatial reference system registry 
(`srs_registry.csv`) to match **OSGeo PROJ 9.8.1** by updating 
`dev/generate_srs_registry.py` and re-running the generator. It also adds 
**regression tests** for SRIDs that appear in the PROJ 9.8.1 registry but were 
absent in the prior registry: projected **ESRI:102964**, **ESRI:105604**, and 
geographic **ESRI:104030**, plus updated counts in 
`SpatialReferenceSystemMapperSuite` and additional round-trip SRIDs in 
`GeometryDataFrameSuite`.
   
   ### Why are the changes needed?
   
   Keeping the bundled registry aligned with current PROJ releases ensures 
newly standardized CRS codes resolve correctly for `Geometry` / `Geography` 
types and connector interoperability. Tests lock in representative new entries 
so future registry refreshes do not silently drop CRS coverage.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. Users may see additional supported SRIDs / CRS string IDs and updated 
canonical mappings consistent with PROJ 9.8.1 data (the CSV diff is the source 
of truth).
   
   ### How was this patch tested?
   
   - `build/sbt 'sql/testOnly 
org.apache.spark.sql.internal.types.SpatialReferenceSystemMapperSuite'`
   - `build/sbt 'sql/testOnly org.apache.spark.sql.GeometryDataFrameSuite -- -z 
"round-trip with Geometry SRIDs"'`
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   No.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to