TEKSI developer's guide

[ponceta]

To be defined :

Actual draft :
https://github.com/teksi/Home/wiki/TEKSI-Developer-Guide

[ponceta]

Propositions of today's technical meeting 👍
QGIS Project
Map templates
QGIS trackable plugin
Custom fields
DB calculated fields
QGIS calculated fields
How to deal with custom symbologies
$variables
naming conventions on views?

Background maps
-> swiss locator maps
WMS / WMTS

Custom background maps
-> orthophoto / city plans / cadastral data
Vector / WFS / WMS / WMTS

[rbovard]

txx_export : Export
txx_sys : System --> Why not txx_system? (same for others)

[sjib]

see follow-up here: https://github.com/orgs/teksi/discussions/90#discussioncomment-7205842

[sjib]

to do: review and integrate:
https://qgep.github.io/docs/user-guide/layerexplanations/namingconventions.html
https://qgep.github.io/docs/user-guide/layerexplanations/layerexplanation.html
and
https://qgep.github.io/docs/admin-guide/db-customization/index.html

[sjib]

see also this discussion: QGEP/datamodel#219 (comment)

[cymed]

I raise the proposition to distinguish the fields as followed:

1. DB calculated field: fields not present in the interlis model that are used to shortcut topological relations or to prepare labels. (i.e. tww_od.wastewater_structure._usage_current). Updated by triggers.
   suggested prefix: '_'
2. Configuration field: fields that are not updated by triggers, but that can be used by the db admin to customize the db behaviour. (i.e. tww_vl.channel_function_hierarchic.order_fct_hierarchic)
   suggested prefix: 'cfg_'
3. official model extension: Official TEKSI model extension to maintain existing functionalities, (i.e. aquifier handling for TEKSI wastewater)
   suggested prefix: 'txx_'
4. Custom field: user-specific database extensions not included in the official TEKSI base model, to be excluded from pum.
   suggested prefix: 'usr_'

[cymed]

Concerning 3: the type of extensions can be added as a comment.