General information
This document helps to collect information for a TEKSI project definition and afterwards the TEKSI projects specification that are the basis for passing with the new feature process thru the different decision takers.
- Applicant (User. who would like this feature): Kevin André (SIGE)
- Author (Service provider, who is mandated to write this request): Kevin André (SIGE)
- Developer (suggested developer(s)): To be defined
- TEKSI Code reviewer : Developer responsible for the code review
Users and administrators needs
Description of users and administrators feature requirements
To ensure optimal and harmonized water network planning, the cantons rely on various tools, especially aggregated and centralized geodata. In this context, the canton of Vaud uses the SIRE (Système d'information des réseaux d'eau).
To feed this system, network operators must provide their data according to the model and requirements defined by SIRE.
Specifically, the data to be provided in SIRE format are as follows:
- Complete data from PDDE
- Pipe project data before construction
- installation project data before construction
- Pipe project data after construction (as-built)
- installation project data after construction (as-built)
The QWAT module currently offers an extension schema to format geodata in SIRE format. However, it does not natively handle certain mandatory and optional constraints such as:
- Topology
- Attributes
- Attribute combinations
- Subset selection (for project data)
- Export to file format (provided shapefiles 5.0 + zipped folder)
To produce a valid export, users must therefore carry out additional manual operations.
Currently, to obtain a valid export, users must perform these extra manual steps. Integrating a tool within the Teksi module would simplify and speed up these operations. This tool should allow users to directly generate a valid ZIP export by selecting the type of export as well as the relevant subset.
Requirements
List of requirements
Illustrations of the features and the requirements
Schemes, screen captures, or any other illustrations.
Graphical User Interface (GUI)
Provide a mockup of how it should look like
Technical analysis and specifications
Feedbacks from the technical group
Feasibility study
IF required, list the conclusions of the Feasibility study, options, alternatives and technical specificities
Risks and constraints
Mutualisation
Mutualisation and possible impacts with other projects
Specifications
IF available, link advanced specifications of the features required
Timeline / deadlines
Add a detailed timeline
Related softwares versions
- QGIS version:
- Database model version:
- INTERLIS Model version:
Linked issues :
Documentation
Documentation links
- User manual :
- Administrator manual :
Development and integration
Link and comments from the developer about the product
- Deliverable :
- Recommendations and comments :
- Future prospects :
Conclusion
Conclusions from applicant, users or admins group
- Conclusion:
- Future prospects:
General information
This document helps to collect information for a TEKSI project definition and afterwards the TEKSI projects specification that are the basis for passing with the new feature process thru the different decision takers.
Users and administrators needs
Description of users and administrators feature requirements
To ensure optimal and harmonized water network planning, the cantons rely on various tools, especially aggregated and centralized geodata. In this context, the canton of Vaud uses the SIRE (Système d'information des réseaux d'eau).
To feed this system, network operators must provide their data according to the model and requirements defined by SIRE.
Specifically, the data to be provided in SIRE format are as follows:
The QWAT module currently offers an extension schema to format geodata in SIRE format. However, it does not natively handle certain mandatory and optional constraints such as:
To produce a valid export, users must therefore carry out additional manual operations.
Currently, to obtain a valid export, users must perform these extra manual steps. Integrating a tool within the Teksi module would simplify and speed up these operations. This tool should allow users to directly generate a valid ZIP export by selecting the type of export as well as the relevant subset.
Requirements
List of requirements
Illustrations of the features and the requirements
Schemes, screen captures, or any other illustrations.
Graphical User Interface (GUI)
Provide a mockup of how it should look like
Technical analysis and specifications
Feedbacks from the technical group
Feasibility study
IF required, list the conclusions of the Feasibility study, options, alternatives and technical specificities
Risks and constraints
Mutualisation
Mutualisation and possible impacts with other projects
Specifications
IF available, link advanced specifications of the features required
Timeline / deadlines
Add a detailed timeline
Related softwares versions
Linked issues :
Documentation
Documentation links
Development and integration
Link and comments from the developer about the product
Conclusion
Conclusions from applicant, users or admins group