I just connected with Sandro. They use the current batch script in a windows environment without QGIS installation, but as long as the problem can be solved by installing QGIS somewhere accessible and altering PYTHONPATH, it should be manageable.

From a GDI point of view, wrapping the export in a docker image is probably a good way forward mid-term. I am however hesitant to start dockerising the interlis import/export without a clear project definition.

@domi4484 I suggest the following

Integrate import/export based on the assumption that a QGIS Desktop installation with the TEKSI wastewater plugin is available in the environment from which the shell script is run
document the dependencies of the necessary QGIS Classes and Libraries in the new docs
document the syntax in the new docs

As we assume the QGIS Desktop installation with the TEKSI wastewater plugin to be available, there is no advantage on the user side to define the --labels-file instead of the --qgs-file.

@ponceta Should we add the idea of a dockerised import/export gateway to the harmonsiation pendencies? If we are to follow that path, we should do so for all TEKSI modules.

Possibility to export from command line missing #78

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions