Overlaying geometries #50

New Issue

mpeltriaux · 2021-12-14T12:28:52+01:00

mpeltriaux commented

2021-12-14 12:28:52 +01:00

Status quo

A user is not notified, that a geometry might intersect with other geometries from the system.

Feature

We need to add a warning on the detail view as well as on the overview view for entries where the stored geometry overlays (partially) another, already existing geometry.

Calculation

When an entry is being initially saved or edited and saved, the given geometry should be test-intersected with every other geometry on the database.

Visualization

If there is a conflict with another geometry, the user should see a warning on the top of the detail view, stating that the following objects geometry have already been found where this geometry has now been drawn: x1, x2, x3 and so on.

Storing

To keep track of these conflicts and avoid re-calculating everytime a detail view is opened, the conflict should be stored on the database using a proper model, such as GeometryConflict which holds the following attributes:

conflicting_geometry - the foreign key pointing on the new/edited geometry
existing_geometry - the foreign key pointing on the geometry, which has already been there before

Each time the conflicting_geometry or existing_geometry is being edited, the conflict will be re-evaluated. If the geometries still are in conflict, the entry will be kept. If the conflict seems to be resolved, the entry can be deleted.

# Status quo A user is not notified, that a geometry might intersect with other geometries from the system. # Feature We need to add a warning on the detail view as well as on the overview view for entries where the stored geometry overlays (partially) another, already existing geometry. ## Calculation When an entry is being initially saved or edited and saved, the given geometry should be test-intersected with every other geometry on the database. ## Visualization If there is a conflict with another geometry, the user should see a warning on the top of the detail view, stating that the following objects geometry have already been found where this geometry has now been drawn: x1, x2, x3 and so on. ## Storing To keep track of these conflicts and avoid re-calculating everytime a detail view is opened, the conflict should be stored on the database using a proper model, such as `GeometryConflict` which holds the following attributes: 1. `conflicting_geometry` - the foreign key pointing on the new/edited geometry 1. `existing_geometry` - the foreign key pointing on the geometry, which has already been there before Each time the `conflicting_geometry` or `existing_geometry` is being edited, the conflict will be re-evaluated. If the geometries still are in conflict, the entry will be kept. If the conflict seems to be resolved, the entry can be deleted.

mpeltriaux added the

feature

label 2021-12-14 12:28:52 +01:00

mpeltriaux self-assigned this 2021-12-14 12:28:52 +01:00

mpeltriaux referenced this issue from a commit

2021-12-15 15:10:38 +01:00

#50 Overlaying geometries

mpeltriaux referenced this issue from a commit

2021-12-15 15:10:38 +01:00

#50 Overlaying geometries KOM + OEK

mpeltriaux referenced this issue from a commit

2021-12-16 09:59:17 +01:00