Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDAL 3.0 Coordinate transformation backwards compatibility is broken #44

Open
terovirtanen opened this issue Aug 15, 2022 · 0 comments
Open

Comments

@terovirtanen
Copy link
Contributor

terovirtanen commented Aug 15, 2022

GDAL 3.0 switched axis lat/long order has broken point transform.

OGR Coordinate Reference Systems and Coordinate Transformation tutorial - GDAL documentation

Before GDAL 3.0, the OGRSpatialReference class did not honour the axis order mandated by the authority defining a CRS and consequently stripped axis order information from the WKT string when the order was latitude first, longitude second. Coordinate transformations using the OGRCoordinateTransformation class also assumed that geographic coordinates passed or returned by the Transform() method of this class used the longitude, latitude order.

Starting with GDAL 3.0, the axis order mandated by the authority defining a CRS is by default honoured by the OGRCoordinateTransformation class, and always exported in WKT1. Consequently CRS created with the “EPSG:4326” or “WGS84” strings use the latitude first, longitude second axis order.

Other references and links
GDAL 3.0 Coordinate transformation (backwards compatibility (?)) #1546
Fixed #30678 -- Added support for GDAL 3. #12878

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant