Breaches and exchange lines in the Schematisation Editor

[leendertvanwolfswinkel]

3Di Schematisation Editor:

• [x] Add a new layer group "1D2D Exchange"
• [x] Add layer potential_breach (name in layer panel: "Potential breach") in the group "1D2D Exchange"
• [x] When digitizing a new potential_breach, the start vertex should snap to a channel or connection node (preference for connection node if user moves mouse <= 1m from connection node), the end vertex to an exchange_line; the line should have exactly 2 vertices; any extra in-between vertices should be ignored. The attribute channel_id should be filled in automatically, based on the channel to which the breach was snapped.
• [x] Add layer exchange_line (name in layer panel: "Exchange line") in the group "1D2D Exchange"
• [x] Create styling file(s) for Potential breach
• [x] Create styling file(s) for Exchange line
• [x] Create SQLite -> Geopackage import routine for importing v2_potential_breach to potential_breach
• [x] Create SQLite -> Geopackage import routine for importing v2_exchange_line to exchange_line
• [x] Create Geopackage -> SQLite export routine for exporting potential_breach to v2_potential_breach
• [x] Create Geopackage -> SQLite export routine for importing exchange_line to v2_exchange_line
• [x] Upgrade required schema version to 214

[leendertvanwolfswinkel]

Styling files available here: style.zip

Example of these stylings (with and without DEM background):

[leendertvanwolfswinkel]

Layer order should be:

[ldebek]

@leendertvanwolfswinkel Could you please provide me (or point me to) example schematisation .sqlite file with a new feature types?

[leendertvanwolfswinkel]

If you migrate a spatialite using the newest version of threedi-schema (which has been separated out from threedi-modelchecker), the tables will be created.

So perhaps the best thing to do is to first implement the other ticket about bumping the versions, so it is easier to migrate the spatialites.

[ldebek]

@leendertvanwolfswinkel But that won't give me any features to import right? But anyway - is it confirmed that threedi-schema module need to be added to the plugins dependencies?

[leendertvanwolfswinkel]

First question: I have asked @caspervdw if he can provide an example schematisation with features in the potential_breach and exchange_line tables.

Second question: yes

[leendertvanwolfswinkel]

@ldebek you can use either of the two sqlites below for testing the breaches. I'm not sure if the v2_exchange_line table contains any features, but you can just add a few. They are supposed to be drawn more or less parallel to the channel they belong to, with a maximum of 1 exchange line per channel if the channel's calculation type is 'connected', or 2 if the calculation type is 'double connected'

v2_bergermeer.zip overstroming_vanuit_markermeer.zip

[ldebek]

PR: https://github.com/nens/threedi-schematisation-editor/pull/111

[leendertvanwolfswinkel]

Tested it and it all seems to work great. However, some important fixes are needed in the attribute forms

• [x] In the attribute form of Potential Breach, remove the underscore from "Exchange_level [m]"
• [x] In the attribute form of Exchange line, remove the underscore from "Exchange_level [m]"
• [x] Give 3 decimals to the input widget for exchange level (I want to be able to fill in 3.342) in the attribute forms for Potential Breach and Exchange line
• [x] Same for Max breach depth
• [x] Add Display name to the Potential breach attribute form
• [x] Channel id of Exchange line should be editable in attribute form
• [x] Change the group order to:
• 1D
• 1D2D
• 2D
• etc

[ldebek]

@leendertvanwolfswinkel Requested fixes applied.

[leendertvanwolfswinkel]

Excellent