Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trench and trench_line - move trench_type to pipe_section table #54

Open
jpdupuy opened this issue Aug 29, 2024 · 1 comment
Open

trench and trench_line - move trench_type to pipe_section table #54

jpdupuy opened this issue Aug 29, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jpdupuy
Copy link
Collaborator

jpdupuy commented Aug 29, 2024

This issue has been raised by the initiators of the TDH module during the prototype presentation.

The trench (curvepolygonZ) and trench_line (compoungcurveZ) will never be used or captured by the land surveyors, nor by the QGIS operators. The datamodel references the trench by the fk_trench in the trench_line table. This means that the trench (polygon) must be created first. This is unrealistic. A special python tool should be created to allow to digitize the trench axis and ask for the trench_width. We do not believe that the landsurveyor will capture the axis of the trench, but rather the pipe_section fixed points, start and end points, and all intermediate elements.

Therefore, the initiators ask to include the trench_type and trench_width in the pipe_section table. There is a need to know the trench_type when the end user select a pipe_section.

image

@sjib sjib added the enhancement New feature or request label Nov 1, 2024
@sjib
Copy link
Contributor

sjib commented Nov 28, 2024

  • Think about how to relate these tables in a view vw_tdh_* (connecting pipe_section and trench)
  • check with user needs described above
  • sketch a new form
  • implement in datamodel
  • adapt project file

@sjib sjib self-assigned this Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants