-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2024 03 19 (Technical Group)
Arnaud Poncet-Montanges edited this page Mar 19, 2024
·
5 revisions
Time: 13:30 - 15:00 Place: Online
Coordination: Arnaud Poncet-Montanges (Technical Group Secretary) (APM)
Invited: Urs Kaufmann (Holinger Thun) (UK), Sandro Gassmann (geopoint lütolf AG) (SG), Stefan Burckhardt, Timothée Produit (Alpnetsystem SA (ig-group)) (TP), Jean-Pierre Dupuy (Morges) (JD), Saeid Rezvani (Sutter Ingenieur- und Planungsbüro AG)(SR)
Agenda - please add your topics
Organisation
- Goals for 2024 https://github.com/orgs/teksi/discussions/99
Technical discussion
*** Update on VSA-DSS 2020 Adaption:
-
VSA 2020 Tests and dev progress:
- see https://github.com/teksi/wastewater/issues
- Defined milestones:
- TEKSI Wastewater VSA DSS 2020 Part 1 as soon as possible intergrate open issues, do testing and fix bugs
- TEKSI Wastewater 2024.0: 31.3.2024
-
Additional suggestions from @cymed:
- https://github.com/teksi/wastewater/pull/36 How do we warn the user that no cover is created (Logs? QMessageBar?)
- https://github.com/teksi/wastewater/pull/42 How do we want to handle the 'minor' wastewater structures (1 or 2 views)
-
https://github.com/teksi/wastewater/pull/85 _label fields should be separated from od classes. Where do we want to handle them?
- separate table as in draft pull request?
- using tww_od.text_txt? (see also Interlis Export)
-
https://github.com/teksi/wastewater/pull/142 Add tool to split reaches with node
- When splitting a reach by a wastewater structure, two new channels are created. How do we want to proceed for easy KEK compatibility?
- When splitting a reach by a wastewater node, channel/ws attributes are kept. Do we create two new reaches or update one and keep one?
- Which fields should be kept from the previous vw_tww_reach when splitting with wn/ws?
- https://github.com/teksi/wastewater/pull/120 Add option for role management per database - clear functionality
*** Release 1.6.1
- Define open steps to complete
- Points to backport from VSA-DSS 2020 adaption - eg. DEFERABLE (to avoid import errors such as https://github.com/QGEP/qgepqwat2ili/issues/125)
- Define timeline
** New feature request *** AG64/AG96
- Extend TEKSI wastewater to support AG64/AG96
- Review by Technical group so that in can be handed in to the board meeting in May
- ---
*** export to mike+ for VSA 2020
- timetable, who, how
*** Steuerungskabel und Schutzrohr
- request raised a General Assembly 2024
- Define if integrated in each module or as an additional central module (pro / con)
- Datamodel available in SIA405 - translation to English needed
- SB can create SQL code for datamodel - make estimation of effort needed
- Import / Export
- timetable, who, how
*** VSA-DSS 2020 - phases 2 and 3
- update and write down project definition (take existing project definition and update and integrate feedback from Moritz Brennecke from testing - email)
- write down requirements document (who, until when)
Sustainability review
- [Developers guide]
- [Contributors Guide]
- Providers guide:
Diverse
- ...
Next meetings: April 9th, 2024 13:30 - 15:00