You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: