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

QGIS not recognizing CRS "EPSG:3301 - Estonian Coordinate System of 1997" in MapInfo mid/mif and tab formats #58283

Closed
2 tasks done
asko456 opened this issue Jul 31, 2024 · 1 comment · Fixed by OSGeo/gdal#10920
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Projections/Transformations Related to coordinate reference systems or coordinate transformation Upstream Needs changes in an upstream library (like Qt, Proj, GDAL, ...)

Comments

@asko456
Copy link

asko456 commented Jul 31, 2024

What is the bug or the crash?

  1. When exporting mid/mif file with CRS "EPSG:3301 - Estonian Coordinate System of 1997" to another mid/mif file with CRS "EPSG:3301 - Estonian Coordinate System of 1997" in QGIS the Layer Properties--> Information does not show exported layer's CRS --- it is "unnamed" instead of "EPSG:3301 - Estonian Coordinate System of 1997".

  2. Possible QGIS bug: when opening mid/mif file, which was created in QGIS with CRS "EPSG:3301 - Estonian Coordinate System of 1997" (although is showing CRS as "unnamed") in MapInfo there is 50 mm gap between original mid/mif's (point 1) tab and tab from QGIS mid/mif. There is no gap when exporting files to and from (tab--> mid/mif; mid/mif to tab) within MapInfo without using QGIS.

Steps to reproduce the issue

  1. I open to QGIS a mid/mif file created in MapInfo Pro version 2023 (Release Build 142, Formatting Date 31.03.2021 13:45:00, Formatting number -12345.67). Mid/mif file name is "E_101_kivi_p_sel".

Mid/mif file CRS in QGIS is "EPSG:3301 - Estonian Coordinate System of 1997" (figure below).

QGIS_origin_mif_info

In MapInfo the mid/mif file projection (it can be seen when opening mif file in notepad) is also EPSG:3301 and is described as follows:

CoordSys Earth Projection 3, 115, "m", 24, 57.51755393056, 58, 59.33333333, 500000, 6375000 Bounds (-503054.5255, 5371945.474) (1503054.526, 7378054.526)

  1. I export this mid/mif file to another mid/mif file in QGIS (Export--> Save Features As). Exported file is named as "E_101_kivi_sel_QGISmif". When exporting I'm using parameters like in figure below:

FromQGIS_to_mif

  1. I open previously exported file "E_101_kivi_sel_QGISmif" to QGIS. Possible bug: Layer Properties--> Information does not show layers CRS, it is "unnamed" instead of "EPSG:3301 - Estonian Coordinate System of 1997" (figure below).

QGISmif_info

  1. Now I export (Export--> Save Features As) the first mid/mif file ("E_101_kivi_p_sel") to .tab file in QGIS with EPSG3301 (figure below). The exported file is named as "E_101_kivi_QGIS_tab".

QGIS_origin_to_tab

  1. I open previously exported file "E_101_kivi_QGIS_tab" to QGIS. Possible bug: CRS is "unnamed" and measured gap between previous layers is 10 mm. Maybe this behavior is explained with issues described here.. Although I tried also custom bounds when exporting in QGIS without results.

  2. I guess this is not an QGIS issue (?), but when opening mid/mif file "E_101_kivi_sel_QGISmif" (which was created in QGIS, point 4) in MapInfo (MapInfo saves it as .tab before opening, that .tab name is "E_101_kivi_sel_QGISmif.tab") there is 50 mm gap between first mid/mif's ("E_101_kivi_p_sel") tab and "E_101_kivi_sel_QGISmif" (figure below).

Origin_vs_QGIS_miftab_measure

When opening "E_101_kivi_sel_QGISmif" mif file in Notepad the projection is as follows:

CoordSys Earth Projection 3, 104, "m", 24, 57.5175539305556, 59.3333333333333, 58, 500000, 6375000

  1. QGIS project with files are here:
    Files.zip

Versions

QGIS version
3.38.1-Grenoble
QGIS code revision
3d4177a
Qt version
5.15.13
Python version
3.12.4
GDAL/OGR version
3.9.1
PROJ version
9.4.0
EPSG Registry database version
v11.004 (2024-02-24)
GEOS version
3.12.2-CAPI-1.18.2
SQLite version
3.45.1
PDAL version
2.6.3
PostgreSQL client version
16.2
SpatiaLite version
5.1.0
QWT version
6.2.0
QScintilla2 version
2.14.1
OS version
Windows 10 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@asko456 asko456 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jul 31, 2024
@agiudiceandrea agiudiceandrea added Data Provider Related to specific vector, raster or mesh data providers Projections/Transformations Related to coordinate reference systems or coordinate transformation labels Aug 2, 2024
@nyalldawson
Copy link
Collaborator

This is an upstream (gdal) issue. (Ping @rouault )

@nyalldawson nyalldawson added the Upstream Needs changes in an upstream library (like Qt, Proj, GDAL, ...) label Oct 3, 2024
@rouault rouault self-assigned this Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Projections/Transformations Related to coordinate reference systems or coordinate transformation Upstream Needs changes in an upstream library (like Qt, Proj, GDAL, ...)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants