The fully integrated Data Validator, which allows validating your 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.

Why is it so awesome?

Using the Model Baker Data Validator has two major advantages.

First, you do not need to export your data before you validate them. Thanks to the --validate option, Model Baker can use ili2db to validate the data directly in the database.

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

Step-by-step guide

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 ?‍?

Import invalid data

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.

We use an example model in this guide to avoid complexity and some invalid demo data.

In Database > Model Baker > Import/Export Wizard choose Run without constraints on the import session.

And when importing the transfer data choose Run without validation.

The database is created and the invalid data from the transfer file are imported.

More information how to import models and transfer files in general you can find in the official Model Baker documentation or in this blog post.

Let’s validate

Now open the Data Validator panel with Database > Model Baker > Data Validator.

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.

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.

Filtering data

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 or datasets or baskets. 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.

We have three intersection issues and one type error.

Skip geometry errors

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

  • Intersecting geometries
  • Duplicate coordinates
  • Overlaying geometries

In the back end the parameters --skipGeometryErrors and --disableAreaValidation are passed to ili2db.

After performing the validation only the error with the TID is left.

Analise the error

Before we go narrowing down the error message by disabling constraints, let’s have a look at the fixing part. The error we see above tells us the TID needs to be a UUID but it is a string: « velopark_id »

The TID is the OID defined in the model like this:


In the physical model, it’s represented by the column called t_ili_tid.

With right-click in the Data Validator on the error a menu is opened with the following options:

– Zoom to coordinates (if coordinates are provided) with an extent of 10 map units
– Open in Feature Form (if a stable t_ili_tid is available)
– Select in Attribute Table (if a stable t_ili_tid is available)
– Set to fixed (marking the entry mark green to have organize the fixing process)
– Copy (to copy the message text)

On opening the form, we see that we don’t have any possibility of changing the t_ili_tid. Since it’s an auto-generated value, Model Baker did not set it to the visible fields on creating the form. We would need to display it by clicking on the Layer > Properties… > Attribute Form or we use the other option to Select in Attribute Table.

Now we can use the QGIS Field Calculator to set a UUID on the t_ili_tid of the currently selected feature (the feature in question).

After validating again, the error disappears.

Valid. But of course, there are still the geometry errors as well as all the errors we had in the other TOPIC living.

Fixing geometry errors

Let’s have a look at the geometry errors.

With right-click > Zoom to Coordinates the canvas zoom to the coordinates in question and highlights them.

To fix intersections as well as duplicate errors, the QGIS Vertex Tool can be used. As well the Vertex Editor is very helpful.

Navigating through the errors

With the three symbols on the bottom left you can navigate through the features and coordinates in the error list, like you are used to it in the attribute table.

Most of the errors concerning a value can be fixed comfortably by the tools provided with right-click > Open in Feature Form / Select in Attribute Table.

Using Config File with meta attributes

The possibility to skip the error messages is quite present. But there are much more possibilities to narrow down the errors by skipping more specific checks.

To have all the validation functionalities available you can load a Config File (INI) the Data Validator passes to ili2db. In this Config File, meta attributes can be defined to enable / disable specific checks as well as naming and describe constraints in a more readable format. The basics are described here. Let’s continue in this post with the example.

Global parameters


By disabling the multiplicity we disable mandatory constraints and cardinality checks on associations. By disabling constraintValidation all the defined logical constraints are not considered.

See all the possible meta attributes in the official documentation of ilivalidator.

Specific class / attribute parameters

The errors that are left are type errors. A value in Levels that is too high (see in the Model: Levels: 0 .. 200;) then the error with control characters (mostly because of using multiple lines in normal TEXT) in the attribute Description and the values in Email that are not in the requested INTERLIS.URI format.

We can disable them by referencing the attribute in question with the format Model.Topic.Attribute:


See for all the global configurations the official documentation of ilivalidator.

Add constraint description and name with meta attributes

Finally, let’s take a look at something particularly beautiful.

This constraint here in the model is a logical constraint. It’s neither implemented in the physical database nor the validator can recognize what it means:

          Name: TEXT;
          IsHuman: BOOLEAN;

It means that if the boolean value IsHuman is true, Name must not be NULL. Anyway, the validator output would be like this:

Set Constraint ModernCity_V1.Living.Resident.Constraint1 is not true.

Because we had in our example already a meta attribute defined, but in the model itself. It did not say Constraint1, but:

Set Constraint ModernCity_V1.Living.Resident.MandatoryHumanName is not true.

The definition in the model looks like this:

      !!@ name = MandatoryHumanName

To define a better readable message you can use !!@ ilivalid.msg to define the complete error message as well.

But because normally the person doing the data validation is not the same as the person writing the model, these meta attributes are not in the model. So everyone can define his messages in the Config File, like this:

msg = "When the resident with the id {ID} is human, then it needs a name."

Notices that you can use other attribute values with curly brackets.

Well then, that’s it

For more information, check out the Model Baker documentation.

Meanwhile happy baking and: Happy validating! ?‍?

1 Comment

Laisser un commentaire