{"id":13328,"date":"2022-11-15T06:47:00","date_gmt":"2022-11-15T05:47:00","guid":{"rendered":"https:\/\/www.opengis.ch\/?p=13328"},"modified":"2024-08-13T23:37:51","modified_gmt":"2024-08-13T21:37:51","slug":"model-baker-interlis-data-validator","status":"publish","type":"post","link":"https:\/\/www.opengis.ch\/it\/2022\/11\/15\/model-baker-interlis-data-validator\/","title":{"rendered":"Model Baker INTERLIS Data Validator"},"content":{"rendered":"\n

The fully integrated Data Validator, which allows validating your<\/strong> data directly in QGIS against their INTERLIS model, exists for almost a year now. After lots of user feedback and some investments, it’s now shinier than ever. Time for an update and a little step-by-step guide.<\/strong><\/p>\n\n\n\n

Why is it so awesome?<\/h2>\n\n\n\n

Using the Model Baker Data Validator has two major advantages.<\/p>\n\n\n\n

First, you do not need to export your data before you validate them<\/strong>. Thanks to the --validate<\/code> option, Model Baker can use ili2db<\/a> to validate the data directly in the database.<\/p>\n\n\n\n

Second, you can interactively use the result list and zoom or pan to coordinates of validation issues<\/strong> in the QGIS map canvas or directly open or select the feature in question<\/strong>. So fixing the errors is much easier.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Step-by-step guide<\/h2>\n\n\n\n

Though the validation is performed on the database, we start with importing an invalid transfer file. With this, we have the complete end-to-end journey ?\u200d?<\/p>\n\n\n\n

Import invalid data<\/h3>\n\n\n\n

Depending on the quality of your data, you need to create the schema already with less strict constraints in the database. Like if some mandatory (NOT NULL) constraints are violated in your data, you need create a database without these constraints enabled.<\/p>\n\n\n\n

We use an example model<\/a> in this guide to avoid complexity and some invalid demo data<\/a>. <\/p>\n\n\n\n

In Database > Model Baker > Import\/Export Wizard<\/em> choose Run without constraints<\/em> on the import session. <\/p>\n\n\n\n\n\n

\"\"<\/figure>\n\n\n\n

And when importing the transfer data choose Run without validation<\/em>.<\/p>\n\n\n\n

The database is created and the invalid data from the transfer file are imported. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n

More information how to import models and transfer files in general you can find in the\u00a0official Model Baker documentation<\/a>\u00a0or in this\u00a0blog post.<\/a><\/p>\n<\/blockquote>\n\n\n\n

Let’s validate<\/h3>\n\n\n\n

Now open the Data Validator panel with Database > Model Baker > Data Validator<\/em>.<\/p>\n\n\n\n

There the current database is found according to the active layer. In our example, we have only one database, but if you use more than one in the same QGIS project, the Data Validator will recognize the source of the current layer.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After performing the validation we receive 14 errors. Geometry intersections, wrong formatted TIDs, out-of-range values and others. Actually, these are not many errors, still, sometimes you might want to separate the kind of errors that are found to keep the overview.<\/p>\n\n\n\n

Filtering data<\/h3>\n\n\n\n

Let’s start with the separation of the data and later we separate the kinds of errors. You can do it by filtering the data either by models<\/em> or datasets<\/em> or baskets<\/em>. You can choose multiple of them, but only one kind of filter. Let’s validate only the data of the basket considering the TOPIC nature<\/code>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

We have three intersection issues and one type error.<\/p>\n\n\n\n

Skip geometry errors<\/h3>\n\n\n\n

When the checkbox is activated, geometry errors are ignored and the validation of area topology is disabled. Errors like those will not be listed:<\/p>\n\n\n\n