This should be relatively easy, given that the .TAB file header contains a Table Type which is commonly NATIVE (old .TAB files readable by MITAB, etc.) or NATIVEX (extended .TAB files), as well as a few other less popular options. So the 'magic' identifier should be clearly spelled out in plain text.
E.g. > !table > !version 1520 > !charset WindowsLatin1 > Definition Table > Type NATIVEX Charset "WindowsLatin1" Locale "en-US" > Fields 32 ... *____________________________________________________Ryan Proulx* | Team Lead, Principal Developer, Project Manager Suite 1200 - 9639 137A Street, Surrey, BC Canada V3T 0M1 [email protected] | www.safe.com <http://www.safe.com/> *____________________________________________________* [image: http://www.safe.com/emailsignature] <http://www.safe.com/emailsignature> On Mon, Aug 3, 2020 at 3:06 AM Even Rouault <[email protected]> wrote: > On lundi 3 août 2020 09:26:16 CEST Rahkonen Jukka (MML) wrote: > > > Hi, > > > > > > Might be good if the MITAB driver could recognize if TAB file is of the > new > > > Extented TAB format and show a meaningful error for the users. It could > > > save troubles similar to this one in gis.stackexchange > > > > https://gis.stackexchange.com/questions/369014/mapinfo-tab-files-with-large > > > int-cant-be-converted-to-qgis-or-any-other-format. I hope the new format > has > > > some magic number that stores the version. > > > > From a comment in the thread, it looks it might be something that could be > addressed by MITAB with some extra work. We'd need a reproducer dataset to > confirm. > > > > Even > > > > -- > > Spatialys - Geospatial professional services > > http://www.spatialys.com > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
