8

When I open a tab file that's been generated in QGIS using EPSG 28355 (MGA 94, z55s) using QGIS 3.10 the projection is transformed to 5551

enter image description here

But when I open it in Mapinfo v17 it's correctly reported as 28355 enter image description here

ogrinfo thinks that it's EPSG:9122 and 9001 enter image description here

This is not just one dataset, it's been happening to any data that starts in 28355 or 28354.

It works fine for shp/gpkg etc...the issue is just with the .tab format.

As per my comment to a reply -this has been happening in all QGIS 3x versions and the test is simple.

  1. Create a temp table in 28355 enter image description here

  2. Add some data enter image description here

  3. Save it as a tab file and a shp file using save-as rather than "Make Permanent"

  4. In a new project try and bring the data in. The SHP is fine but the TAB asks to transform.

TAB enter image description here

SHP enter image description here

Improve this question

1 Answer 1

Reset to default
5

Issue with the latest QGIS, you wont encounter this if you use 3.8 or earlier. I believe it has something to do with the latest version of Proj

Improve this answer
10
  • 1
    Tested here in the latest QGIS long-term release 3.4.13, compiled against PROJ 6.2.1 and GDAL 3.0.2, same as QGIS 3.10.0, and the EPSG:28355 is well recognized for a file exported as MapInfo TAB. Even so, the PROJCS tag remains "unnamed" for ogrinfo.
    – Gabriel De Luca
    Nov 25, 2019 at 3:00
  • I'm not a mapINFO user but have worked extensively with 28354 and 28355 (everything from 28349 to 28356 over time) which are all on the way out, soon it will be 7854 and 7855 for MGA2020 zone 54 and 55 respectively. If this is causing a serious issue perhaps define as 32755 (WGS84 UTM Zone 55 South) which is more uniform and see if the problem persists - it could be that the MapINFO TAB driver is finding it difficult to read the coordinate information from the most recent TAB files and this CRS is probably near enough for most datasets and purposes except the sub-metre accurate.
    – Michael Stimson
    Nov 25, 2019 at 3:18
  • So what you're saying is that 'newer' isn't necessarily 'better' MapInfoNewbie.. this wouldn't be the first time I've seen the most recent version introducing errors in workflows that have had no previous problems. I like that enough for a +1 but don't have MapINFO to test it on.
    – Michael Stimson
    Nov 25, 2019 at 3:21
  • Thanks but this has been happening for all versions of QGIS from 3 onwards. I just kept letting it be hoping that it would get fixed but it keeps happening. The test is simple... create a temp table in QGIS save in 28355 as tab and shp, close QGIS and open it and you will see the tab comes up in 5551. See updated Q for details.
    – GeorgeC
    Nov 25, 2019 at 4:56
  • 2
    The same problem with Balkans projections, qgis 3.10??
    – nagib
    Nov 25, 2019 at 6:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.