-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2022 11 08 (Technical Group)
Focus: Technical Group Meeting
Time: 13:30 - 15:30 Place: Online
Coordination: Arnaud Poncet-Montanges (Technical Group Secretary)
Present: Urs Kaufmann (Holinger Thun) (UK), Timothée Produit (Alpnetsystem SA (ig-group)) (TP), Peter Zamudio (geopoint lütolf AG) (PZ), Stefan Burckhardt, Olivier Dalong (OD)
Excused: Valentine Arrieta (VA), Saeid Rezvani (Sutter Ingenieur- und Planungsbüro AG)(SR), Kevin André (SIGE) (KA), Noemi Romano (Lausanne) (NR), Jean-Pierre Dupuy (Morges) (JD), Denis Rouzaud (DR)
Topics (please add your topics):
- new release of qgep project-file: UK presents his improvement in the QGEP project file he has done in the last months. They should be documented in a new issue New project release #772 :
- to decide: eliminate vw_pump, vw_prank_weir, vw_leapingweir??
- Entry of numbers with range min / max (Issue 750): changing range to restriction? OD looks into this and opens a QGIS Upstream issue if not already existing.
- There is a second issue Problems when editing co_level in vw_qgep_wastewater_structure #749 that is caused if a field is used twice in a form, that UK mentioned just after the meeting. OD - Can you look at this also?
- sequence of layers is often not useful: if i'm interested in nodes or covers, i have to turn off vw_qgep_wastewater_structure... Change groups? Change sequence? AP points out, that the order of layers can be changed when eg. editing - new functionality in QGIS. UK and AP make suggestion for sequence of layers for editing.
- SQL Errors - UK please open separate issues for these
- AP has also some ideas for improving the project file - AD will add his points in the issue
- TP has some views he would like to add also that display possible mistakes in the data - TP will add descriptoin in the issue
- Rémi Bovard has the need of adding two more subclass views and corresponding layers for visualisation: vw_wwtp_structure (ARABauwerk) and vw_infiltration (Versickerungsanlage) (added after the meeting - direct contact SB and RB 9.11.2022)
OD suggests to use the plugin "Trackable QGIS Project" to have a better structured project file:
UK will the first add his new version as a pull request and then the others AP (please also do the suggestions of RB) and TP can add their improvements. Please work on a 3.26 version. We will at the end decide if we want to save as a 3.28 version finally, but once saved in the wrong version makes it very complicated to go back.
- INTERLIS Export with Text classes
- testing of pull request has been done by SB, UK and PZ, Open issue: Default selection of scales is none. Last selection will be saved for multiple exports. Then Implementation as new release ok.
- logs with xtf file instead of temp folder #77: OD created fix for this https://github.com/QGEP/qgepqwat2ili/pull/79, implementation with new release ok.
Decisions:
- Create new release of QGEP (Plugin) (1.5.6) with these two pull request. OD pushes them to master and creates new release (till October 30th at the latest)
- Follow up of Dependeny with Model Baker issues #71 by OD in writing a proposal on how to disconnect ModelBaker from TEKSI wastewater. PZ does not like the point to have to change ModelBaker version to the given version. Advanteges with using ModelBaker to look up the Java path are not worth to keep the dependency. No direct contacts to ModelBaker steering commitee or time to check if latest Model Baker version still comply.
- INTERLIS Import / Export additional models (SIA405 Abwasser / VSA-DSS) - update on discussion and implementation (SB)
- Testing to export SIA405_ABWASSER_LV95 directly from ili2pg_abwasser (KEK schema) is possible
- Testing to import SIA405_ABWASSER_LV95 directly to ili2pg_abwasser (KEK schema) is possible with existing version of tool
- to discuss and decide:
- Option a) VSA-KEK export becomes VSA-KEK / SIA405 Abwasser Export and both xtf Files are always created. Pro: When you export VSA-KEK a seperat export of the network only is helpful and you can choose what you want to give to your TV company. Con: If I have a lot of KEK data the export is slower.
- Option B: Seperate VSA-KEK and SIA405 Abwasser export. Using of the same script, but selection of the xtf at the end. Pro: Very easy additional configuration, no duplicity of code / configuration between VSA-KEK and SIA405 Abwasser. Con: see option A
- Option C: totally separat configuration of VSA-KEK and SIA405 Abwasser, Pro: Export of SIA405 Abwasser stay quicker even if there is a lot of VSA-KEK data in the database. Con: Duplicity of code / configuration, higher maintenance costs and risk of contradicitions.
Decision: Go for Option a) for the moment. Open a new issue about optimizing the performance of import / export
- For VSA-DSS a seperate configuration is needed as VSA-DSS is not an extension to SIA405 Abwasser. Improvement of code can be done in checking to use same base functionalities - to do SB with OD.
- Calculation slope per mille: https://github.com/QGEP/QGEP/discussions/766 - postphoned to December meeting
- **Prepare QGEP 2023 -> QGIS 3.28.1 will be the new LTR for next year / postgres 10+ (since 1.5.5) **- postphoned to December meeting
- Identify critical bug fixes: The three critical bugs have been worked and identified as QGIS Upstream issues on and are beeing fixed with QGIS 3.28. or 3.28.1
- vw_qgep_reach not drawing the start and end line segments of a polygon. Problem caused by NAN #752 - OK
- Multiedit works not with QGEP #739 - Testing needed with QGIS 3.28.1 after 2022-11-18
- 'nan' values on reaches makes the layers export fail #737 - Waiting for review https://github.com/qgis/QGIS/pull/50507
- Identify critical bugs for the December meeting if there are any.
- PZ mentioned about a tool he uses (Autohotkey) he built to calculate bottom levels if you have cover level and depths in a manhole. This is a very common use case in daily work. Currently he uses key functions to do so. PZ formulates a new feature idea for this and describes it in the discussion section so everyone can see how it works (short video). This will be the basis for a new feature request proposal.
Next meeting: December 13th , 2022