-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2023 10 17 (Technical Group)
Stefan edited this page Oct 17, 2023
·
17 revisions
Time: 13:30 - 14:30 Place: Online
Present: Arnaud Poncet-Montanges (Technical Group Secretary) (APM), 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
Features review
- Update on VSA-DSS 2020 Adaption (APM): Project hast started. Model part by Stefan is finished in a version so that opengis can take over. Project adaption was moved after part of opengis.
- Update on different PR for 1.6.1 release in progress (APM): Adaptions to Datamodel 2015 for release 1.6.1 has been pushed and can be downloaded in the datamodel tool in the Master selection. For the plugin and qgepqwat2ili part a review by opengis is planned.
- The technical group decides on the following release timetable: Review by opengis till end of October. Testing release available on November 6th, so planning for testing in November can be done by the technical group, Final release 1. December 2023.
- All datamodel pull request should be integrated except: https://github.com/QGEP/datamodel/pull/219 (move to teksi wastewater). All non-outdate pull requests from qgepqwat2ili (https://github.com/QGEP/qgepqwat2ili/pulls) and the needed plugin adaption (https://github.com/QGEP/qgepplugin/pull/97)
Sustainability review
- Developers guide:
- Define https://github.com/teksi/Home/wiki/TEKSI-Developer-Guide#custom-fields - There is a definition for calculated fields (_ added in front). This is missing for custom-fields: We have a convention in QGEP (https://qgep.github.io/docs/admin-guide/db-customization/index.html#adding-fields) with usr_*
- and suggestion for https://github.com/teksi/Home/wiki/TEKSI-Developer-Guide#value-list : Different options were discussed whether value list tables should get a vl prefix again, so they can be found more easily in the relation tool. And / or if od prefix has to be added manually also. And which views should get a vw_prefix - all or just the ones that or not sub/superclass views. And other suggestion is to improve the relation tool and make a search field as in the search menu of QGIS where you can just start typing. This would be an approach that not only solves the current work of UK - but is a long term improvement for all QGIS users. Use same fonctionality as QGIS search field:
- update on project (AP) - Integration infrastructure github for new developments is www.github.com/teksi -> wastewater. Current version stays on www.github.com/qgep
Diverse
- [QGEP/QGEP] Relation Reference vs Value Relation and speed (Discussion #836) (UK) - use value relation if it is possible instead of relation reference - this helps the performance. Exception when you reference a very big table. Or if you want to connect on the map (e.g. wastewater_node selection from catchment).
- other possible optimization points: Take out e.g. wastewater_node.dataowner / provider - as they slow down view. Fill in automatically either on export or with a button to be the same as wastewater_structure. -> new issue about performance (AP to do link it here)
Next meetings:
November meeting conflicts with Journée romand de la géoinformation 14.11.2023 - move to 7.11.2023 instead.