Modelbaker

Latest version: v1.7.3

Safety actively analyzes 624712 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 28

7.8.4

Fixes
* use nice prefix for meta attribut form_order
* use 'obsolete' parameter createEnumTabs on ili2db 3 only

ili2db

7.8.3

Fixes
* Fix python error wrapped C/C++ object of type xy has been deleted
* unchain the optimize combo from topping results
* Don't make topics irrelevant that are extended by itself (in Basket Page)

ili2db

7.8.2

Improvements / Fixes

* Wait for model refresh on local repository topping receiven https://github.com/opengisch/QgisModelBaker/pull/877
* Fix that when version output not valid we don't think we find a match in https://github.com/opengisch/QgisModelBakerLibrary/pull/84
* Fix topic request, to list them even when no table is implemented in https://github.com/opengisch/QgisModelBakerLibrary/pull/87
* Consider path when building up ilicache, fixes opengisch/QgisModelBaker861 in https://github.com/opengisch/QgisModelBakerLibrary/pull/85

ili2db

7.8.1

Improvements / Fixes

* display --- when no bid-domain defined in https://github.com/opengisch/QgisModelBaker/pull/869
* accept xml files in wizard in https://github.com/opengisch/QgisModelBaker/pull/870
* Return the import models from repository in one entry, what leads to one command for all repo models by in https://github.com/opengisch/QgisModelBaker/pull/871
* Keep Settings in UsabILIty Exporter on Navigation in https://github.com/opengisch/QgisModelBaker/pull/873

ili2db

7.8.0

This release focuses on topping handling (UsabILIty Hub) but brings as well some improvements of the workflow wizard in general. It makes some missing bits available like for example the using of a project topping on generating a project and the possiblity to delete the data in the schema before import.

Improvements

UsabILIty Hub: Topping on Generate Project

Since ili2db 4.11 the id of the metaconfiguration file used to create the physical database is stored in the meta-tables. This means, on **Project Creation** we consider this id and provide the linked **project topping**.

![Screenshot from 2023-12-04 14-41-47](https://github.com/opengisch/QgisModelBaker/assets/28384354/9ddcd4fb-b718-4e01-ab65-aa8f303f5688)

Get Topping by selection
Still it's possible to **disable it** and choose another **project topping file (`YAML`)**.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/1f5760c7-0ad4-4556-8088-9f5d7174550c)

You can choose a **project topping file** (identified by model, db-type etc.) from the **UsabILITy Hub** repositories or as well a YAML file from the **local system**.

Why, *project topping* file
... and not "metaconfiguration* file?

Because on this step only project topping files are relevant. Metaconfiguration files are only relevant, when the schema is created. We thought about to provide them, to choose the same like on schema import, but this part is already provided by getting the topping from the DB.

Sponsors
Financed by Canton of Schwyz and the QGIS Model Baker Group

UsabILIty Hub: Filter Toppings according to the Database Source

Model Baker only provides the toppings that are made for the current database source (GeoPackage, PostgreSQL etc.) in case it's defined in the `ilidata` at the `category` with the key `http://codes.modelbaker.ch/preferredDataSource`. If there is no such category it's always displayed - so there are no backwards compatibility issues.

UsabILIty Topping Exporter
Here it detects what database sources are used and suggests you to optimize. You still can choose none.

![Screenshot from 2023-12-01 09-09-18](https://github.com/opengisch/QgisModelBaker/assets/28384354/da16bde1-6839-4921-8c76-e41208c40ed0)

Sponsors
Financed by the QGIS Model Baker Group

Delete before import

It is now possible to delete the existing data before importing new data. This means on using baskets, the ili2db parameter `--replace` is executed instead of `--update`. On not using baskets, the parameter `--deleteData` is added to the command. Note that on using baskets, only the data from the corresponding dataset is deleted, whereas on not using baskets all data from the schema is deleted.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/d9a6910c-be94-4b47-aa55-db922e11cb98)

Sponsors
Financed by the QGIS Model Baker Group

Busy bar to indicate that Model Baker is doing something

Sometimes the wizard has to load - mostly checking the repos to suggest data / reload the comboboxes. And there users are confused, what's happening. For this reason it does now disable the page (instead of just freeze) and show a busy indicator as a bar below the log panel.

![Screenshot from 2023-12-08 13-50-00](https://github.com/opengisch/QgisModelBaker/assets/28384354/6e8e99b4-1583-46e4-9e6b-d7a1cb24e565)

Sponsors
Financed by the QGIS Model Baker Group

Other improvements
* Introduce prefix `qgis.modelbaker` for Model Baker specific Meta Attributes. See [documentation](https://opengisch.github.io/QgisModelBaker/background_info/meta_attributes/#list-of-specific-attributes)
* With the **UsabILIty Hub Topping Exporter** the transaction mode of the project is exported as well and considered on **generating a project** using this topping.
* On **generating a project** the optimize strategy is stored to the project variables. This setting is then exported by the **UsabILIty Hub Topping Exporter** and considered on **generating a project** using this topping.
* Checkbox to use superuser in OID Manager
* Name OID and TID strictly "OID" to avoid confusions

Fixes
* Update schemas in separate task to avoid freezes in https://github.com/opengisch/QgisModelBaker/pull/854
* Check if the layer is a QgsVectorLayer before getting the fields in https://github.com/opengisch/QgisModelBakerLibrary/pull/77
* Don't handle xml files 2 times in https://github.com/opengisch/QgisModelBaker/pull/845
* Display `---` when no oid-domain defined in the OID Managerin https://github.com/opengisch/QgisModelBaker/pull/864

ili2db

7.7.0

Main feature of this release is all about OIDs, a pain point that has existed for quite some time. First thing is the OIDs generated for the single objects, means the TID (or t_ili_tid in the physical database) what is done with default value expressions. The second thing is the OIDs generated for basket-objects, means the BID (and as well t_ili_tid in the physical database), when creating baskets, what now can be controlled by the user as well.

Improvements

TID (OID) Generation for Objects
Often the models definition requires a cross-system unique identificator. The so called OID.

Model Baker detects the OID domain (like `UUIDOID`, `I32OID`, `STANDARDOID`, `ANYOID` or user defined OID) and suggests default value expressions used in the `t_ili_tid` fields.

Since the user have to be able to edit those values, they are provided in the GUI.

See [documentation](https://opengisch.github.io/QgisModelBaker/background_info/oid_tid_generator/)

In the wizard
There is an additional page after the generation of the QGIS project.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/9a4beb61-ebfa-43fe-beab-5e9ebb1c333d)

You can use the QGIS Expression Dialog to edit the default value expression for the `t_ili_tid` field of each layer.

See [documentation](https://opengisch.github.io/QgisModelBaker/user_guide/import_workflow/#tid-oid-values)

On existing projects

Find the **TID (OID) Manager** via the *Database > Model Baker* menu.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/fc7902b8-1f4f-4cef-96be-e7b8115821ae)

If you need a counter in the expressions, you can use the `t_id` field, that has a schema-wide sequence counting up. This sequence can be reset as well by the user, but be carefull not to set it lower than already existing `t_id`s in your project.

Sponsors
This feature has been financed in a crowdfunding project by [geostandards.ch](https://geostandards.ch/), [Canton of Schaffhausen](https://sh.ch/CMS/Webseite/Kanton-Schaffhausen/Beh-rde/Verwaltung/Volkswirtschaftsdepartement/Amt-f-r-Geoinformation-3854-DE.html) and the QGIS Model Baker Group

Basket Generation with BID (OID)

In case you create a new dataset (e.g. the `Baseset` that is created by Model Baker automatically) and you want to collect ***fresh*** data in QGIS (no import of existing data), the baskets have to be created as well.

Here the `BID` definition needs to be considered.

In the wizard

There is an additional page after the schema import when the `Baseset` is created.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/8a68d207-a4ee-431e-b764-2abd9c1b5f3c)

Reasonable BIDs are suggested, but of course some of them (like `STANDARDOID`) need editing by the user.

As well Model Baker suggests what baskets should be created or not (it sees it as relevant in case it's not extended by other topics).

See [documentation](https://opengisch.github.io/QgisModelBaker/user_guide/import_workflow/#create-baskets)

In the Dataset Manager

Of course you might want to create additional Datasets and with it the Baskets. Here is a new option *Manage baskets of selected dataset* to create the baskets you want.

![image](https://github.com/opengisch/QgisModelBaker/assets/28384354/e0534984-4d0d-4054-a8ab-7e6c734200b8)

See [documentation](https://opengisch.github.io/QgisModelBaker/background_info/basket_handling/#creation-of-baskets)

Sponsors
This feature has been financed in a crowdfunding project by [geostandards.ch](https://geostandards.ch/), [Canton of Schaffhausen](https://sh.ch/CMS/Webseite/Kanton-Schaffhausen/Beh-rde/Verwaltung/Volkswirtschaftsdepartement/Amt-f-r-Geoinformation-3854-DE.html) and the QGIS Model Baker Group

Schema section in drop down
On PostgreSQL connections you are now able to select your schema.

![Screenshot from 2023-11-24 13-12-40](https://github.com/opengisch/QgisModelBaker/assets/28384354/5fa3e3f8-2525-4da8-a71e-a9b47fc9faf8)

Sponsors
This feature has been financed by the [Canton of Schaffhausen](https://sh.ch/CMS/Webseite/Kanton-Schaffhausen/Beh-rde/Verwaltung/Volkswirtschaftsdepartement/Amt-f-r-Geoinformation-3854-DE.html)

ili2db

Page 1 of 28

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.