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 - foreign key from trench_line to trench #88

Open
jpdupuy opened this issue Feb 27, 2025 · 0 comments
Open

Trench - foreign key from trench_line to trench #88

jpdupuy opened this issue Feb 27, 2025 · 0 comments

Comments

@jpdupuy
Copy link
Collaborator

jpdupuy commented Feb 27, 2025

I believe that the foreign key defined in the trench_line table does not make sense.

Image

The land surveyor is supposed to capture the trench axis (CompoundCurve) instead of the trench edges (CurvePolygon) because it takes less time and less number of points.

Furthermore based on the current datamodel, you currently have to capture the trench polygon with QGIS (and all of the attributes like trench width, depth, type, ....). Then you can capture the trench_line, and then refer the foreign key to the trench polygon.

It would make more sense to define all of the attributes to the trench_line, and then build a buffer depending to the trench width. The trench polygon is just a construction.( suggest to ;

  • trench_line (rename to trench_poly +change geometry type from CompoundCurve to CurvePolygon + change fk)
  • trench (change the geometry type from CurvePolygon to CoumpoundCurve)

Luzern Specifications : Le tracé ne doit être capturé que si sa largeur dépasse 2 m ou s'il s'agit d'un canal maçonné ou en béton. Les autres captures de tracés sont facultatives. Le tracé est capturé comme une ligne pour une géométrie parallèle. Pour des objets plus complexes avec des angles supplémentaires, une géométrie en surface peut être capturée.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant