Two major problems have been solved with this version of Model Baker and its underlying components. Support for translation models and the ability to handle tables with multiple geometry columns on GeoPackage. In addition, the dataset/basket manager has been improved so that you no longer need to edit (or view) these technical tables directly.
Tables having multiple geometries on GeoPackages
Finally. Multiple geometries per table are possible in GeoPackage, just like in PostgreSQL. Actually, we are building on the great work done on GDAL and ili2db. This concerns models with multiple geometry attributes in one class like `KbS_V1_5`, `Nutzungsplanung_V310` and others.
The setting for `gpkgMultiGeomPerTable` on Schema Import
If this parameter is set, ili2db creates multiple geometry columns per table in a GeoPackage.
This only works with a sufficient GDAL version \* Otherwise it's invisible and false.
Generating QGIS Project
If we have a **sufficient** GDAL version \*, we can create a QGIS project, but need to warn, that others reading this project may have problems.
If the schema was created with the `gpkgMultiGeomPerTable` *and* it contains tables with multiple geometry columns, but the current **GDAL version is not sufficient**, we block the creation of a QGIS Project.
