7.10.7

Fixes and Improvements

Validation Config File as Topping

The validation config file used in the validator can now be exported and used as a topping file

Topping Export

That's why with this PR you have the option in the Topping Exporter to create a topping file from the variable with the name "validator_config" that is stored at the topping files.

Means we have now the validation-config.ini file in the toppings and link over the variable to the ilidata: key.

Topping Import

But what happens on project create with this topping?

Nothing :-) It keeps the ilidata: key in the variable. This means in the Validator we see the ilidata: key as well. And this can be used then on validation (passing this key as --validConfig to ili2db).

Sponsors

Financed by the QGIS Model Baker Group

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.6

7.10.6

Fixes and Improvements

• Fix issue with German translation and keyword "Modelle"
• Fix issue with using authentication configurations that are not available anymore

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.5

7.10.5

Fixes and Improvements

UsabILIty Hub / Topping Naming

• The word topping is only used for the QGIS related files: project topping (YAML), additional topping files (files used by the project topping like QML etc)
• Use metaconfiguration, reference data, extra meta attribute file etc. no matter if they come from local system, repositories or something like UsabILIty Hub...
• No mention of UsabILIty Hub anymore (it's not a hub!) but to have kind of a title of the whole systematic it's called now "UsabILIty Toppings"

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.4

7.10.4

Fixes and Improvements

Topping Exporter: Export all ili2db settings to metaconfig via ili2db

This allows us to use the exact same settings for the recreation of the schema with the metaconfig-file.

Thanks QGIS Model Baker Group for financing!

Other improvements

• Improve usability of basket page with descriptive text

  

• hide system layers in legend (since we have a powerful Basket Manager meanwhile 🙂 )

• make difference between action type SCHEMA_IMPORT and GENERATE (fixes #987)

• Busy bar on Topping Exporter

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.4

7.10.3

Fixes and Improvements

• Don't set "None" (instead of None like NULL) when no fallback user is given
• allow connections without username password
• For toppings: avoid issues with backslashes
• Create display expression for domains with translation considerations in
• Improve log outputs

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.3

7.10.2

Fixes and Improvements

• Log output from ili2db properly in the log files

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.1

7.10.1

Fixes and Improvements

• Refresh validator panel when added new dataset
• Pass blacklisted models to find available language because they are irrelevant

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.1

7.10.0

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.

* Sufficient GDAL Version 3.8

The functionality to read such tables with multiple geometry columns is not standardized and does only work with GDAL Version >= 3.8

When a schema is created with this parameter gpkgMultiGeomPerTable and the Model contains multiple geometries per table, it can neither create a project on QGIS with GDAL<3.8 nor read a project that has been created on a QGIS with GDAL >= 3.8.

If no multiple geometries per table, it still can create a project from it by GDAL<3.8 or open such a project.

As well we need to be aware, that GeoPackages are not that powerful than PostgreSQL. Those not-standardized implementations have been tested with the testmodels, KbS_V1_5 and Nutzungsplanung_V310. But there is no guarantee given that it works in every case.

Sponsors

Financed by the QGIS Model Baker Group

TRANSLATION OF

For TRANSLATION OF model, the database schema is created in it's original language (otherwise you would have to pass the parameter --nameLang manually), but on project generation Model Baker parses the meta table (t_ili2db_nls) and creates the GUI in the selected language.

The result is a translated GUI.

Sponsors

Financed by the Canton of Neuchâtel and the QGIS Model Baker Group

Superpower Dataset Manager

The Dataset Manager has existed for quite some time, but it was still not possible to edit baskets and delete datasets. This had to be done via the technical tables t_ili2db_datasets and t_ili2db_baskets. Not anymore. With the new Dataset Manager you can do everything like adding, modifying or deleting datasets and baskets.

Particularly useful are functions that delete depending children. This means that if you delete a dataset, the referencing baskets and all the data in this basket are also deleted. Of course, you will be warned if you do such critical things.

Sponsors

Financed by the QGIS Model Baker Group

Support non-password DB connections

This mainly concerns solutions with Active Directories and technologies such as Kerberos. There, authentication is performed on the server side, which means that Model Baker should attempt requests without a password.

And if no user name is defined in the connection settings, Model Baker uses the user name of the operating system as a “fallback” (obtained by QgsApplication.userLoginName()).

Sponsors

Financed by the Canton of Schaffhausen

Other things

• Show warning message in TID manager when OIDs cannot be found in #954
• Translation (Transifex) Guide in Documentation in #959
• [export] Hide superuser checkbox on PG export and make it possible to run PG export with authConfig and no superuser in #962
• Topping Exporter: Consider the layer type for style categories in #966 and load style for raster layers as well in opengisch/QgisModelBakerLibrary#105
• Fix on DB Manager: Get db type from settings and read the settings accordingly in #968
• Concern superuser login on receiving schema in #969

ili2db

Using ili2db version 5.2.0

Library

Using modelbaker library 1.9.0

7.9.3

Fixes

• Remove override decorator

ili2db

Using ili2db version 5.1.0

Library

Using modelbaker library 1.8.1

7.9.2

Fixes

• Set the list panel with the db_id instead of the mode.

ili2db

Using ili2db version 5.1.0

Library

Using modelbaker library 1.8.1