2.1. Requirements

2.1.1. Provider Side

In order to install the TEKSI Wastewater module, you will need to install :

A PostgreSQL instance with PostGIS extension (check the roadmap for supported versions)

Note

TEKSI Wastewater uses a PostgreSQL with postgis Extension database, you need to install these on your server : Recommended is to use the EnterpriseDB to make sure your postgreSQL version matches your postgis version and is installed at the right place.

Python 3.12+ (installed via OSGEO4W or using python.org)
QGIS installed with the latest LTR version
Recommanded is to install it with the OSGEO4W installer directly with all python packages listed.
A working pg_service file and a connexion secured to your database server (hosted or local)
TEKSI Module Management Tool (TMMT) plugin installed from the QGIS plugin repository

The following Python packages (installed via OSGEO4W or using pip) are required:

Psycopg as database adapter
Pydantic for data validation
Pirogue for model generation and upgrades

Note

PUM python package is automatically installed with the TMMT plugin.

2.1.2. Client Side

For each client (workstation), you will need :

QGIS installed with the latest LTR version
Recommanded is to intall it with the OSGEO4W installer directly with all python packages listed.
A working pg_service file and a connexion secured to your database server (hosted or local)
TEKSI Wastewater plugin (.zip file)
TEKSI Wastewater project (.qgs file)

The following Python packages (installed via OSGEO4W or using pip) are required:

Psycopg as database adapter
sqlalchemy for INTERLIS imports and exports
geoalchemy2 for INTERLIS imports and exports

2.1.3. PostgreSQL Server side :

Allow the connexion of your clients through the postgresql.conf file and make sure your client is allowed to reach the server postgresql port (default is 5432).

TEKSI Wastewater requires PostGIS functions that did not function properly in a set of releases:

Versions before PostGIS 3.2 are not affected
When using PostGIS 3.2, the bug is fixed in Version 3.2.7
When using PostGIS 3.3, the bug is fixed in Version 3.3.6
When using PostGIS 3.4, the bug is fixed in Version 3.4.2
Versions of PostGIS 3.5 or later are not affected