-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting 2025 02 11 (Technical Group)
Time: 13:30 - 15:00 Place: Online
Coordination: Arnaud Poncet-Montanges (Technical Group Secretary) (APM)
Present:
- Urs Kaufmann (Holinger Thun) (UK), Stefan Burckhardt, Lukas Wiss (geowerkstatt), Timothée Produit (Alpnetsystem SA (ig-group)) (TP), Jean-Pierre Dupuy (Morges) (JD), Marion Nappez (GeoConseils SA) (MN)
Excused: Sandro Gassmann (geopoint lütolf AG) (SG),
- Financing for phase 2 (9AB TMMT Installation of Database) of of Outils et processus d’installation, de gestion et de mise à jour des Modules has been completed. Develompment is planned for March/April
- Currently working of financing of phase 3 (9AB TMMT Upgrade of Database)
- Roles and schemas - naming conventinos: https://github.com/teksi/wastewater/issues/522 and https://github.com/teksi/wastewater/blob/main/docs/en/user-guide/layerexplanations/namingconventions.rst and https://github.com/teksi/Home/wiki/TEKSI-Developer-Guide#schemas - clarify if txx_cfg is still needed in phase 2 of 9AB
- Next Release - 2024.1 ? Timing? Needs first that Project 9AB phase 3 is implemented.
Issues:
- fe_sendauth: no password supplied
- 3D geometries of reaches and reach points levels are not synchronized
- Need of clear changelog practice
- Validation attribute - Start basic discussion where to check on validity of data / INTERLIS constraints that allow various profiles see https://github.com/teksi/district_heating/discussions/86
Follow up VSA-DSS 2020 implementation: There is an existing discussion that lists already a lot of ideas. Some already have been implemented as short wins in 20204. Bigger steps would be Measure and Log Cards. ALR was always rated as last prio. https://github.com/teksi/wastewater/discussions/240 Please contact UK if you want to help progress this. Best would be to identify needs and implement in portions of maybe 5-10K each.
- New technologies and architectures:
- GeoGirafe – A modular WebGIS built with a state-of-the-art architecture Initiated by a motivated user group (Geomapfish) comprising various cantons, cities, and other stakeholders, the project GeoGirafeis an exciting new project. This state-of-the-art WebGIS framework features a modular architecture, making it easily extensible and configurable for specific needs. Built on the native browser technology Web Components, this system is not only highly performant but also future-proof and maintenance-friendly thanks to a low dependency footprint, a notable property in the javascript world. It contains an npm package, which allows easy integration of the components within projects that are not primarily focused on WebGIS. This makes Geogirafe versatile for both fully-fledged single-page WebGIS applications and as individual components that can be embedded in websites.
TEKSI could gain visibility if once finished one or several TEKSI projects could be presented with geogiraffe (e.g. Test project)
-
Kablo – A peek into the future of industry solutions Kablo is a proof of concept for the next generation of industry solutions. Kablo demonstrates the potential of modern architecture in implementing workflows for electricity network management. At the core of Kablo lies its middleware, which encapsulates application logic to ensure efficient development processes and the stability and adaptability of the developed solutions. This project seamlessly integrates the capabilities of QGIS and QField with web technologies. A new module allows for bringing application logic to REST services, according to the OGC API – Features standard, which forms part of a series of upcoming standards set to be implemented in the geospatial industry in the upcoming years. „Kablo“ represents a significant advancement in bringing powerful geospatial tools into industry tools, paving the way for innovative and robust solutions, not only for electricity.
-
Qfield plugins QField has a QML/Javascript plugin framework through which additional functionalities and features can be scripted. Plugins can be served in two ways:
- as a project-specific plugin that will be active for the duration of a given project session;
- as an application plugin that will be activated when QField launches.
Blog post: Supercharge your fieldwork with QField’s project and app-wide plugins
First QField-plugins can be found here
Next meetings: