7.0.0

With the release 7.0. Model Baker introduces it's data validator as a new feature, but sets also a milestone after all those integrations in the last year like the UsabILIty Hub (6.5), the Wizard (6.6) and the proper handling of Baskets and Datasets (6.7).

Data Validator

Easy validation of the physical data against the ILI model. The data can be filtered by model, dataset or baskets.

The database connection parameter are emitted from the currently selected layer. Mostly this is representative for the whole project, since mostly a project bases on one single DB schema. In case of multiple used DB Schemas, it's possible to "switch" between the validation results when switching the layers.

ili2db is used with the parameter --validate, so no export of the data is needed. The output is parsed by Model Baker and provided in an interactive list.
Entries of the type Error and Warning are listed.

With right click on the error there is opening a menu with:

• Zoom to coordinates (if coordinates are provided)
• Open form (if a stable t_ili_tid is available)
• Set to fixed (marking the entry mark green to have organize the fixing process)

Use List Widget for ARRAY mapping

If the metaattribute [email protected]=ARRAY is defined in the ILI model configure the corresponding widget in QGIS as "List".

ili2db 4.6.1

In this release we use ili2db version 4.6.1

6.7.1

• Fix the importTid/exportTid handling in the wizard: Get the TidHandling from settings table to decide if --importTid / --exportTid needs to be passed on data import/export. TidHandling is in the t_ili2db_settings table when --createTidCol is passed on schema import.
• Set t_ili2db_basket table to writable: Since Model Baker does not create always the BIDs correctly.
• Use fetch and increment of T_Id in geopackage: Considering the T_KEY_OBJECT table simulating a global sequence number. This is used because we edit the dataset and basket table.

6.7.0

Catalogue dataset handling in wizard

On importing data you can mark a file as catalogue. If so, then there is no dataset selectable.

The data is imported to a dataset called Catalogueset. It stays technical and it's hidden for the user (It's not listed in the Dataset Manager, it's not listed in the Dataset Selector and it's not listed as option in the Relation Reference of the basket ids. On export it's not listed as dataset).

Export of baskets / models / datasets in wizard

On the data export page of the wizard you can filter for model(s) but also dataset(s) and basket(s).

In the ili2db doc they say you can use models or alternatively datasets or baskets (so this implies that you only use usually one of them). And it makes no conjunction (AND) but a disjunction (OR) if multiple parameters are given. A conjunction can still be done by selecting the smallest instance (baskets).

Getting catalogues from the UsabILIty Hub

On entering the Import Schema Configuration Page the ilidata.xml on the UsabILIty Hub repositories are parsed for the modelnames (from the listed models) and the type referenceData in the categories. There the modelLink properties are read and the models are loaded into the list of models to import automatically.

On the Import Data Configuration Page we have an autocomplete drop down containing the referenceData items (transfer files) found according all the models in the current database schema (not only the previously imported ones). You can add and remove them by +/-. xml files receive the default property that they are catalogues (considering the datasets).

6.6.7

• fix ilidata.xml parsing on title element

6.6.6

• The possibility to disable validation on import / export is provided again.
• Do not pass a dataset on import when it's not requested
• Allow to drop XML files on the source selection page
• Don't add unused models from the parsed XTF to the import list

6.6.5

• Fix weird dialog order in MS Windows
• Default CRS is 2056 instead 21781
• Update configuration change in ili2db command sessions when "going back" in wizard
• Wizard GUI improvements

6.6.4

• pass iface to Wizard to be able to generate QGIS projects

6.6.3

• Supports XTF model parsing on multiple lines.
• The strange window order (on MS Windows) introduced with 6.6.2 is reverted to the status before.

Known issues:

• The settings are not updated in wizard when going back #561
• Wizard dialog don't stays in front on MS Windows #564

6.6.2

• Dataset combobox stays stable on unexpected data sources (like an xtf file).
• Drop of multiple files (including ili-files) in QGIS opens source selection page in wizard.
• File list in source selection page supports drop of multiple files.
• Check the export-configuration instead of the import-configuration on export if there has been a basket handling.
• Wizard dialog stays always in front of QGIS.
• Only check the models in the import model list when same named models are not checked already.
• Only pass models as list in the same session/ili2db command when they are contained in the same ili file.
• Smarter parsing for models in xtf.
• Do not create nm-relation direct relation editor when already a relation_editor to the linktable has been created (because it's not a pure link table but with attributes instead).

6.6.1

• Validation of input (by disabling the button) in the Dataset Manager.
• Use of QGIS Theme icon (so no path problems in Windows) in the Workflow Wizard source selection page.
• Update all the configurations of the Workflow Wizard on the schema import config page. So on data import the same configuration is considered.
• Remove the empty Toolbar when refreshing (updating) Model Baker
• Correct topic parsing (e.g. when there are structures in the model that are not in a topic)
• Basket handling of tables having no topic, like structs that are used in multiple topics. There it should be possible to choose the dataset of it's parent. So all baskets are enabled for them:
  
• Fix error on trying to use an authentication configuration without super user
• Support Dataset Selector on layers using an authentication configuration
• Avoid error of Dataset Selector on layers using the (not supported by the Dataset Selector) PG service file