-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
MapInfo CRS not correctly recognized #5217
Comments
I could not reproduce with GDAL 3.4.0dev on Windows. I had a try both with tab and mif
and then
Or with gdalsrsinfo
|
I've a fix pending. The issue is when using the WKT2 definition of EPSG:25832, which is what QGIS does under the hood, which lacks an explicit datum code. |
QGIS 3.18 finds https://epsg.org/crs_7791/RDN2008-UTM-zone-32N.html from the mif file that I created but I really made that shapefile with an odd method (attach srs UTM32 into EPSG:4326 data in degrees). |
that changed in QGIS 3.22 from EPSG7791 to EPSG32632 @rouault thats great! looking forward to this release then :) |
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
MapInfo .tab writing: correctly detect datum when creating a layer from a WKT2 CRS string (fixes #5217)
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
…ce: use authId as much as possible This helps preserving metadata, like datum code, which is generally absent from WKT2 output. Or when importing from WKT1, extent is missing. This is an alternative to the fix of OSGeo/gdal#5218 for OSGeo/gdal#5217.
Hello,
I m using GDAL 3.4.1 with QGIS 3.22.3
When exporting any file to a MapInfo .tab into the CRS EPSG:25832, opening that exported file is incorrectly recognized as EPSG:32632.
gdalinfo of that file reports:
It should be ETRS and not WGS84 i think. I opened an issue some time ago for QGIS, but i think here it is better placed, if not please delete (qgis/QGIS#43482) !
The text was updated successfully, but these errors were encountered: