I have been opening a 12GB GeoPackage in v19 - one address table.
It opens but is incredibly slow and doesn't like other tables being opened into the same Map Window.
The 8GB csv equivalent dataset performs better!
Needs improvement.
------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------
Original Message:
Sent: 12-15-2017 08:07
From: Andrew Harfoot
Subject: Has MapInfo support for GeoPackage tables improved in v16?
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:
- MI: ~2.7 sec
- QGIS ~6.4 sec
Timings Geopackage:
- MI: ~18.5 sec
- QGIS: ~8.5 sec
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.
Cheers,
Andy