7.6.1

Improvements / Fixes

Filter in Relation Reference for Baskets

On extended class's layers all possible baskets (if NONE-Strategy) or only the relevant ones (if GROUP- or HIDE-Strategy) are listed in the widget of the t_basket field.

Dataset Selector and Default Values

In the dataset selector all possible baskets (if NONE-Strategy) or only the relevant ones (if GROUP- or HIDE-Strategy) are listed. The chosen value is then written to the project variable and can be used as default value.

Library

Using modelbaker library 1.5.1

7.6.0

This release offers new features that make working with advanced capabilities of INTERLIS even more enjoyable, such as with advanced models and using validation configurations. Furthermore, it offers some enhancements and fixes, like clearing the cache, a pleasant log and the support of drag'n'drop of extra meta attribute files.

Improvements

Optimized Project Generation of extended INTERLIS Models

The problem

If a model or topic contains extended classes, the inclusive base classes are implemented in the physical database what leaded to a confusing layer tree, messy forms and lots of unused relations.

While the you only want to see, what is relevant for you, Model Baker detects the irrelevant layers and lets you to apply an optimization to the project.

The solution

When generating a project you can now choose one of the following strategies to optimize your project:

Hide strategy

Base class layers with extensions of the same name are hidden and base class layers with multiple extensions also. Unless the extension is in the same model, then it's not hidden but renamed.

Relations of hidden layers are not created and thus the widgets for them neither.

Group strategy

Base class layers with extensions of the same name are grouped, base class layers with multiple extensions also. Unless the extension is in the same model, then it's not grouped but renamed.

Relationships of grouped layers are created, but widgets are not applied to the form.

None strategy

Independently from extended models (but pretty much connected to it), we eliminate ambiguous layer naming in general. This means:

• If layername is ambiuous append topic name as suffix.
• If layername is still ambiguous append model name as suffix.

Sponsors

This feature has been financed by QGIS Anwendergruppe Schweiz - Groupe d'utilisateurs QGIS Suisse - Swiss QGIS User Group

Persistent Logging Functionality

Warning and information messages are printed to the log panel of the wizard dialog. This is good to see the information immediately, but to track down a problem, users and developers require the information of past actions. The new logging functionality saves each log output to a daily file (in the plugin directory, i.e. the QGIS profile folder) and keeps the last ten files accessible via the Model Baker menu.

Error dialog

If Java is not installed, a barely visible log line used to be output. For people using Model Baker (and thus ili2db) for the first time, this was quite confusing. Now a popup appears indicating that Java is not installed and pointing to a possible download source.

Clear Ilicache Button

In several places, but especially on the Source Selection Page, the user can select and use a model from the network of Swiss Geodata Repositories. These files are downloaded and cached locally. In case of immediate changes - which is not often the case, but can be if the model is in a test phase - the problem can occur that a different file (the one from the cache instead of the one from the repository) is used. Users had to delete the cache folder manually, which was usually too advanced and inconvenient. This is now solved by having a button do it for you.

Store Validator Config File in Project Variable

Since some time you have the possibility to select a config file in the validator and pass it to ili2db. Since it is meaningful to use this multiple times, it is handy that you can now store the path in the QGIS project variables. The path is stored relatively (so that the project can be exchanged to other systems), but passed absolutely to ili2db. Likewise, it is possible to pass (and store) a key to the ilidata repository, like ilidata:<key>.

Drag&Drop Support for Extra Meta Attribute Files (toml/ini)

While Model Baker claims to do everything for you when dragging and dropping files into QGIS, the Extra Meta Attribute Files (the file formerly known as the toml file) were not considered. This is now fixed. When you drop an additional Extra Meta Attribute File, it is automatically set in the advanced schema import settings.

Other Improvements and Fixes

• Possibility to validate schemas based on ili2db 3.x.x
• Fix missing port parsing from layer to use in validator
• COMPOSITION strength relation on STRUCTURE childs: A STRUCTURE object cannot exist without a parent. This means when the parent is deleted the entry in the linking table (the structure) needs to be deleted. Means, every relation with a child that is a structure, shall have composition as strength.
• Better default size for Layer Style Categories Dialog
• Add the icon for the main menu entry
• Remove old unused files

ili2db

Using ili2db version 5.0.0 fixing this #779

Library

Using modelbaker library 1.5.0

7.5.2

Fixes

• Sort models / toppings in autocompleter box
• Print short description when a metaconfig has been selected
• Set current layer only if validate dock is visible
• Deactivate next button while searching for referenceData

Library

Using modelbaker library 1.4.4

7.5.1

Fixes

• Fix multiple evaluation of next-id in wizard and broken export models check-list and broken export models GUI on validator.

Library

Using modelbaker library 1.4.3

7.5.0

This release brings better support of working with extended models concerning export and validation.

Improvements

Export the data in the base model format

If your data is in the format of the cantonal model, but you want to export it in the format of the national model, you have to pass --exportModels to ili2db, otherwise (or if the data cannot be exported/validated in the selected model because it's not an extension of it) the data is exported in the model it is stored.

Usually, this is one single model. However, it is also possible to pass multiple models, which makes sense if there are multiple base models in the schema you want to export.

Note that this implementation works as addition (and not replacement) of the filters where models can be passed to define what data (not what format) should be exported.

The tool tip is listing all the relevant parent models (the ones that are listed as well, means are exportable).

The export session visualization has been improved, helping for more clearity.

Validate the data in the base model format

Same is now supported in the validator as well.

When the data are validated in the model where they are stored (here Staedtischer_Ortsplanung_V1_1 extending Kantonale_Ortsplanung_V1_1, all the constraints are considered. Means the one of the extended model and of its parents.

And when validating according to the parent model, only the parent model's constraints are checked (and the parent's parent's constraints of course 😄

Sponsors

This feature has been financed by QGIS Anwendergruppe Schweiz - Groupe d'utilisateurs QGIS Suisse - Swiss QGIS User Group

ili2db

Using ili2db version 4.10.0

Library

Using modelbaker library 1.4.3

7.4.2

Fixes

• Fix workaround to add the usabilityhub repository when a metaconfig is passed to ili2db in opengisch/QgisModelBakerLibrary#55

Library

Using modelbaker library 1.4.2

7.4.1

Fixes

• Allow ini for the Extra Meta Attribute File in #778
• Consider base config in the validation configuration in #783
• Reset Metaconfig on Data Import / Update in #787
• Passing --sqlColAsText when importing schema without constraints in opengisch/QgisModelBakerLibrary#51
• Workaround to add the usabilityhub repository when a metaconfig is passed to ili2db in opengisch/QgisModelBakerLibrary#53

Library

Using modelbaker library 1.4.1

7.4.0

This release brings support of map themes, layer styles, custom variables and print layouts in the UsabILIty Hub Toppings.

Improvements

UsabILIty Hub passing metaconfig to ili2db

ili2db configurations are defined in the metaconfiguration file.

[ch.ehi.ili2db]
defaultSrsCode = 2056
smart2Inheritance = true
strokeArcs = false
importTid = true

ili2db will be called like this:

ili2db --metaConfig ilidata:metconfigId --schemaimport 

Some parameters are automatically set in the background when ili2db is called by the Model Baker (like --coalesceCatalogueRef --createEnumTabs --createNumChecks --createUnique --createFk --createFkIdx --coalesceMultiSurface --coalesceMultiLine --coalesceMultiPoint --coalesceArray --beautifyEnumDispName --createGeomIdx --createMetaInfo --expandMultilingual --createTypeConstraint --createEnumTabsWithId --createTidCol --importTid), and others can be configured by the user in the input mask of the Model Baker (like --smart1Inheritance/--smart2Inheritance, --createBasketCol, --strokeArcs, --iliMetaAttrs (for ini/toml), --preScript and --postScript or --models). In addition, the relevant metaconfiguration file is passed to ili2db. But parameters passed directly to ili2db override the configurations of the passed metaconfiguration file.

The Model Baker reads the ili2db parameters from the metaconfiguration file. The parameters that can be set via the input mask of the Model Baker are loaded from the metaconfiguration file into the input mask. The user can now customize them. The Model Baker now passes the metaconfiguration file and the parameters from the input mask (whether customized or not) to ili2db. So if the parameters were listed in the metaconfiguration file but then disabled in the input mask, they will be passed to ili2db as false.

Changes are marked visually in the input mask for ili2db Options:

The parameters set by the Model Baker in the background are still set. But they can be overridden in the metaconfiguration file. However, if in the metaconfiguration file such parameters are not mentioned, then they are also not overridden with false.

Exception is the setting to consider only the metaconfiguration file. If this is set, then only the parameters configured in the metaconfiguration file should be set and no others (Exception from the exception is --models and --sqlEnableNull on "Run withouth constraints"):

[CONFIGURATION]
qgis.modelbaker.metaConfigParamsOnly = True

When this parameter is set the Advanced Options and CRS settings are disabled in the input mask.

Known Issues (workaround provided in 7.4.2)

Be aware that the UsabILIty Hub Repository (located at http://models.opengis.ch) is not found by ili2db what means that when using qgis.modelbaker.metaConfigParamsOnly toppingfiles referenced in metaconfig file with ilidata: should not be located there. Other repositories (like e.g. from the cantons) can be used without any restrictions. Still you can add http://models.opengis.ch as a directory in the Model Baker Settings.

Sponsors

This feature has been financed by the canton of Schaffhausen

ili2db

Using new ili2db version 4.10.0

Library

Using modelbaker library 1.4.0

7.3.2

Fixes

• Fix run button after failed schema import in #773

Library

Using modelbaker library 1.3.8

7.3.1

Fixes

• Validator: Pan and zoom to coordinate (whenever possible) in #770
• only check repo again for toppings when model list diverts in #772

Improvements

• Ability to re-run and cancel import processes #761

Library

Using modelbaker library 1.3.8