Meeting 2023 11 07 (Technical Group)

Time: 13:30 - 14:30 Place: Online

Coordination: Arnaud Poncet-Montanges (Technical Group Secretary) (APM)

Present: Urs Kaufmann (Holinger Thun) (UK), Sandro Gassmann (geopoint lütolf AG) (SG), Stefan Burckhardt, Jean-Pierre Dupuy (Morges) (JD)

Excused: Timothée Produit (Alpnetsystem SA (ig-group)) (TP), Saeid Rezvani (Sutter Ingenieur- und Planungsbüro AG)(SR)

Meeting notes

Technical discussion

• Testing new datamodel and new project for TEKSI wastewater - who can join. Planned for December / January
• How to contribute
• Distance heating code repository (APM) https://github.com/teksi/distance_heating. S. Burckhardt makes proof of concept for datamodel creation (SQL create scripts)

Features review

• Update on VSA-DSS 2020 Adaption: A. Poncet explains why there is a new schema tww_app: Everything that is linked to work logic will be in that schema (triggers, functions), separated from tables for easier update management
• Update on different PR in progress (APM)
  • 1.6.1 pull request - some of them were merged
  • only new version of datamodel plugin needs to be released (includes VSA-DSS import / export)

Sustainability review

• Developers guide:

• PUM Postgers Update Manager: Originall developed for QGEP and qwat: Current Documentation for QGEP

  • Great tool, but also great danger, especially when integrating multiple databases

• Question raised, if own data model customization should be kept or not?

  • the defined rules should continued to be valid and applied for datamodel customizations: https://qgep.github.io/docs/en/admin-guide/db-customization/index.html
  • 4.4.1. Check first, if there is not already an attribute that could handle my need. If not make a request to the VSA and suggest and adaption there
  • 4.4.2. if still needed: add usr_ prefix to own attributes and regenerate views
  • 4.4.3. joining tables
  • 4.4.4. create custom views

• Question raised? Do you use customizations?

  • S. Gassmann: I have created new view for Eigentuemer / Betreiber, but no new attributes added
  • U. Kaufmann: Additional views used, but no new attributes or tables added
  • J.P. Dupuy: No topic yet
  • V. Arrieta: Personalisation absolutely necessary - but we agree to haved training and rules for it.
  • SIGE: Small customizations made
  • Vevey: Integration - have problems with customized value lists -> better documentation needed: Add link in chapter 4.4.

• Decision by technical group: Keep customization mechanism, but keep strict rules and have discussion process (inform technical group when you have an idea about a customization and check first with them about your implementation)

• Responsibility for customizations stays with the user - also for migration processes later

• Suggested general adaptions for 2020:

  • Additional fields in vw_qgep_reach (U. Kaufmann) - please list here
  • Additional calculated fields in views (U. Kaufmann) - please list here

• update on project - Integration infrastructure github (A. Poncet)

  • There has been a refactoring of the Continues Integration process (CI) with the development of VSA-DSS 2020 Adaption - see
  • New datamodel-create-dumps.yaml that creates a datamodel dump after each datamodel adaption -> restore in empty database possible with that
  • This is also planned for plugins and TEKSI QGIS project (qgs) fils - so testing ahead should become easier

Diverse

• Keep STANDAROID for TEKSI
• If range of postfix is too small there are the following options: a) just add a new prefix to the project (easy) b) Invest in code adaptions for obj_id generation to also included letters - see https://github.com/QGEP/QGEP/discussions/764
• for online / offline editing - use temporary UUOID and translate on import to TEKSI
• extended value lists on INTERLIS export - still open issue (C. Meder / S. Burckhardt)

Next meetings: December 12th, 2023 14:00 - 15:30