There's more to experience when you log in!
We are searching for a file format that works well in both MapInfo Pro and QGIS. GeoPackage may be the answer, but it certainly had issues in V15. Does anybody know of a better format for both applications or if the support has improved in V16? We find .tab files are very slow to load in QGIS and need to use both applications.
Yes, MapInfo Pro 16.0 version supports the geopackage format.
MapInfo Pro lets you select which tables in a GeoPackage to open, when you have multiple number of tables inside it.
However, MapInfo Pro creates the .tab file for each of the tables that you have selected to open from the GeoPackage and the update made to the tables are saved over these new tab files.
Would like to hear from you what kind of issues are coming up in v15.0. It could be an issue with the format or an issue in Mi Pro we could take up as an improvement idea. Please do let us know.
Geopackage and TAB are the obvious formats as both have read / write support in MapInfo and QGIS. I've just done a quick test of a full table redraw (zoomed to full extent so not using the spatial index), with Enhanced rendering (MI), Feature simplification and anti-aliasing (QGIS) disabled to create a fairly level playing field.
Software used: QGIS 2.18.15 (x64), MapInfo 16.0.2 (x64)
Data used: https://s3-eu-west-1.amazonaws.com/data.defra.gov.uk/Natural_England/Designations/SSSI_Impact_Risk_Zones/SSSI_IRZs_Tab.zip
Timings MapInfo TAB:
The conclusion is that whilst QGIS is slower than MI at rendering TAB files, both are a lot slower at rendering Geopackages, so I'd recommend you stick to TAB unless you need to use the additional functionality available in Geopackages.
I recall an issue with null values in gpkg which MapInfo doesn't do. Has that been resolved??
Yes, this issue has been fixed for version 16.0.