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
Use the same logic as we have for other layers, based on the measure_location.connection_node_id -> connection_node.id FK relation
Memory control / table control
Attribute form magic
Tags
For table control: the action_table is a three-column table with columns Measured value, Action value 1, Action value 2. Should work the same as the tables we have in other attribute forms (e.g. for tabulated cross-sections)
Automated actions
Set the target_type based on whether the memory/table control is placed on a weir, orifice, or pump
Fill in the ID of the weir, orifice or pump in the the target_id field
If placed on an orifice or weir, snap the geometry to the centroid of the orifice/weir
Use the same logic as we have for other layers; the relation is a bit more complicated; target_type indicates which table is referenced; target_id indicates which feature in that table is referenced. The memory control should snap to orifice, weir, and pump features. When the orifice, weir, or pump feature is deleted and user also wants to delete all features that reference the deleted objects, the memory control should also be deleted.
Measure map
Attribute form magic
Tags
Automated actions
When creating a new feature, set the weight to 1 by default
Fill in measure_location_id automatically if the measure_map starts at a measure location (also update this automatically if the geometry changes)
Fill in control_type and control_id automatically if the measure_map is created or when its geometry is changed
For an illustration of the workflow from the user perspective, see this powerpoint presentation: https://nelenschuurmans-my.sharepoint.com/:p:/g/personal/leendert_vanwolfswinkel_nelen-schuurmans_nl/ERXFQx4jVU5Iv759Gq0ZEGEB1UReWWhsx4i9XmjS9Jtz_w?e=EubU7W
Measure location
Attribute form magic
None, except for the tags
Automated actions
Set connection_node_id to the id of the connection node on which this is snapped
Snapping / topological editing / cascaded deletion options
Use the same logic as we have for other layers, based on the measure_location.connection_node_id -> connection_node.id FK relation
Memory control / table control
Attribute form magic
action_table
is a three-column table with columns Measured value, Action value 1, Action value 2. Should work the same as the tables we have in other attribute forms (e.g. for tabulated cross-sections)Automated actions
target_type
based on whether the memory/table control is placed on a weir, orifice, or pumptarget_id
fieldSnapping / topological editing / cascaded deletion options
Use the same logic as we have for other layers; the relation is a bit more complicated;
target_type
indicates which table is referenced;target_id
indicates which feature in that table is referenced. The memory control should snap to orifice, weir, and pump features. When the orifice, weir, or pump feature is deleted and user also wants to delete all features that reference the deleted objects, the memory control should also be deleted.Measure map
Attribute form magic
Automated actions
weight
to 1 by defaultSnapping / topological editing / cascaded deletion options
Similar to those for
surface_map
. Snap tomeasure_location
,memory_control
, andtable_control
features.The text was updated successfully, but these errors were encountered: