"Import culverts" GUI

[leendertvanwolfswinkel]

The dialog should look like this:

The dialog has two tabs, one for culverts and one for connection nodes. Culverts that are added in a location where the start or end vertex is within snapping distance (specified by the user) of a connection node will be connected to that connection node. If no connection node is present within snapping distance, connection node(s) will be created. For those newly created connection nodes, the properties can be set in the 'connection nodes' tab.

The columns in the table in the image are in bold in the explanation below.

For each attribute in the target layer, the user can choose which method to use to fill it: the value can be (a) left empty, i.e. NULL (b) taken from the source attribute, or (c) use a default. If the user wants the values to be taken from the source layer, there are two additional considerations:

• If the target field is an enum, users should be able to specify a value map. E.g. cross section shapes may follow a different naming convention in the source data than in 3Di, which the user may want to map to 3Di categories.
• If the target field value is NULL, the user-specified default should be used. Users can also specify NULL as default.

Further details for each culvert attribute specifically, see this Excel sheet: https://nelenschuurmans-my.sharepoint.com/:x:/g/personal/leendert_vanwolfswinkel_nelen-schuurmans_nl/ETjOz94ZsbJOsKk18jfZZNMBWUkhxw3oVDim7wc9MlDydw?e=T7WWXP

Other requirements/considerations:

• [ ] Snapping should be the default option, with a default snapping distance of 0.1 m
• [ ] Transform the geometries from their source CRS to the target layer's CRS
• [ ] If there are > 1 connection nodes within snapping distance, use the nearest. If > 1connection nodes are at exactly the same distance from the start/end vertex, just choose one (the schematisation checker will warn users about this).
• [ ] Culvert geometries can have any number of vertices, so no special operations are needed to deal with lines that have > 2 vertices (unlike pipes)
• [ ] Include an option "Selected features only" to import only features that are selected in the source layer
• [ ] The 'save as template' and 'load template' options will be described in another ticket

[leendertvanwolfswinkel]

@ldebek Really nice work, I am super happy about this!

Some additional wishes after testing:

• [x] Set the 'Create connection nodes' checkbox to checked by default
• [x] Put a combobox widget in the 'source attribute' column, so that users can choose from the attributes available in the source layer
• [ ] Make the dialog non-blocking
• [x] Disable the cells 'source attribute' and 'value map' if method != attribute
• [x] If users choose method 'Attribute' but do not choose a source attribute, make the source attribute cell orange and disable the Run button
• [x] If the option 'create connection nodes' is not checked, disable the 'Connection nodes' tab

[leendertvanwolfswinkel]

@ldebek Tested it and everything seems to work great.

Can you just make this one minor improvement:

Please include the target table in the error message. In the example below, it took me some time to figure out that these missing fields refer to the connection nodes

Please specify a source field for a following attribute(s) and try again:
Connection node: Code
Connection node: Initial water level [m]
Connection node: Storage area [m²]

[ldebek]

@leendertvanwolfswinkel Layer name added to the message.