Skip to content

Meeting 2024 03 19 (Technical Group)

Jump to bottom Edit New page
Stefan edited this page Mar 19, 2024 · 5 revisions

Time: 13:30 - 15:25 Place: Online

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

Present: Urs Kaufmann (Holinger Thun) (UK), Stefan Burckhardt, Lukas Wiss (geowerkstatt)

Excused: Sandro Gassmann (geopoint lütolf AG) (SG), Timothée Produit (Alpnetsystem SA (ig-group)) (TP), Jean-Pierre Dupuy (Morges) (JD), Saeid Rezvani (Sutter Ingenieur- und Planungsbüro AG)(SR)

Protocol

Organisation

Technical discussion

*** Update on VSA-DSS 2020 Adaption (AP):

  • VSA 2020 Tests and dev progress:

  • Additional suggestions from @cymed:

    • https://github.com/teksi/wastewater/pull/36 How do we warn the user that no cover is created (Logs? QMessageBar?) - to do testing with provides dump
    • https://github.com/teksi/wastewater/pull/42 How do we want to handle the 'minor' wastewater structures (2 views sounds good) - integrate with VSA-DSS 2020 phase 2
    • 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? Yes
      • using tww_od.text_txt? (see also Interlis Export) No
    • 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?
      • UK adds possible design for User Interface from GEPView - implement the same way with selection if wastewater node should be added and / or reach should be split.
    • https://github.com/teksi/wastewater/pull/120 Add option for role management per database - looks good, also define how to deal with multiple databases (e.g. different communities)

*** Release 1.6.1 (AP)

** New feature request

*** AG64/AG96

*** export to mike+ for VSA 2020

  • who (Cyril and Urs), how - make project description, suggested timetable (Q2 project description, review and board Q3 / Q4 development and implementation)

*** Steuerungskabel und Schutzrohr

  • request raised a General Assembly 2024
  • Define if integrated in each module or as an additional central module (pro / con) (SB), till April technical meeting
  • Make short project description and requirements document (SB), till April technical meeting
  • Datamodel available in SIA405 - translation to English needed
  • SB can create SQL code for datamodel - make estimation of effort needed, , till April technical meeting
  • Integrate INTERLSI Import / Export
  • who (SB), timetable (Q2 project description, review and board, Q3 development and implementation)

*** 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 would like to take care of that?, until when)

Sustainability review

Next meetings: April 9th, 2024 13:30 - 15:00

Add a custom footer

TEKSI

https://www.teksi.ch

Clone this wiki locally