Skip to content

Automate model import settings (Setting Prophet with ili2py) #1100

@signedav

Description

@signedav

Users are often overwhelmed with these settings. And the worst part: they often make no sense at all for the specific model.

Image
  • When BASKET OID is defined, this setting is mandatory (no setting should be exposed)
  • When the model does not have multiple geometries per table, the next setting does not make sense either
  • The same applies to arcs. When there are no arcs in the model, why have a setting?
  • And the extra meta attribute files (toml-files) are always the same for INTERLIS 2.3 MultiSurface or Multilingual. Why not just generate it automatically?
  • If there is no TRANSLATION OF model, the language dropdown does not make sense either

So why not emit these settings by parsing the model in advance? This would be easy for a single model with no inheritance, but if it extends topics from other models it gets very, very complicated...

... but luckily we now have a tool doing all this work: ili2py 🐍

It would be possible to have this:

Image

And parts (basket, multiple geometry columns, arcs) are already done in this PoC opengisch/QgisModelBakerLibrary#160

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions