Flood Modeller Tutorial Module02 Provisional: Difference between revisions

Content deleted Content added
Line 10:
* Addition of a river reach represented in ESTRY downstream of the Flood Modeller network.
 
=GIS and Model Inputs=
The steps requirednecessary to modify each of the GIS inputs are demonstrated in QGIS using SHP and GPKG formats. InstructionsIf foryou completingwould like to view instructions for the moduletutorial in ArcGIS or MapInfo arethese availablecan be found on the archive page for [[Flood_Modeller_Tutorial_Module02_Archive | Tutorial Module 02]].
 
===Define Elevations (Building a TIN)===
We have provided theThe GIS layers necessary to modify the ground elevations to represent the proposed development are provided. This part of the tutorial will demonstratedemonstrates how a TIN is created from these GIS layers. We will also update theThe GIS defining the road crest level is also updated. FollowInstructions theare instructionsavailable below for yourthe preferred GIS format.:
 
* [[FM Tutorial M02_QGIS_SHP_Define_Elevations | QGIS - SHP]]
* [[FM Tutorial M02_QGIS_GPKG_Define_Elevations | QGIS - GPKG]]
 
===Define Surface Roughness===
We have provided theThe GIS layers necessary to modify the land use areas thataffected will change as part ofby the proposed development are provided. This part of the tutorial willdemonstrates requirehow populatingto populate the layer attributes to assign Manning’s n roughness values to each land use. FollowInstructions theare instructionsavailable below for yourthe preferred GIS format.:
* [[FM Tutorial M02_QGIS_SHP_Define_Roughness | QGIS - SHP]]
* [[FM Tutorial M02_QGIS_GPKG_Define_Roughness | QGIS - GPKG]]
 
* [[FM Tutorial M02_QGIS_SHP_Define_Roughness | QGIS - SHP]]
===Define Pipe Network===
* [[FM Tutorial M02_QGIS_GPKG_Define_Roughness | QGIS - GPKG]]
This part of the module creates the GIS layers that make up the definition of the sub-surface pipe network. The inlets/pits of the pipe network will be linked to the 2D domain. We will also create the pit inlet database which links those GIS layers to depth-discharge curves. Follow the instructions below for your preferred GIS format.
* [[FM Tutorial M02_QGIS_SHP_Pipe_Network | QGIS - SHP]]
* [[FM Tutorial M02_QGIS_GPKG_Pipe_Network | QGIS - GPKG]]
 
===Define BoundaryPipe ConditionsNetwork===
This part of the module demonstratescreates howthe anGIS inflowlayers canthat bedefine appliedthe directlysub-surface topipe thenetwork. The inlets and pits of the pipe network. Aare GISlinked layer ofto the inflow2D boundarydomain. hasThe beenpit provided.inlet Wedatabase willis also modifycreated, linking the existingGIS Boundary Conditions Databaselayers to include these newdepth-discharge inflowscurves. FollowInstructions theare instructionsavailable below for yourthe preferred GIS format.:
* [[FM Tutorial M02_QGIS_SHP_Boundary_Conditions | QGIS - SHP]]
* [[FM Tutorial M02_QGIS_GPKG_Boundary_Conditions | QGIS - GPKG]]
 
* [[FM Tutorial M02_QGIS_SHP_Pipe_Network | QGIS - SHP]]
==Flood Modeller 1D/ESTRY 1D Link==
* [[FM Tutorial M02_QGIS_GPKG_Pipe_Network | QGIS - GPKG]]
This part of the module demonstrates how TUFLOW 1D (ESTRY) domains can be dynamically linked with Flood Modeller using "X1DH" and "X1DQ" links. Follow the instructions below for your preferred GIS format.
* [[FM Tutorial M02_QGIS_SHP_Flood Modeller1D/ESTRY 1D Link | QGIS - SHP]]
* [[FM Tutorial M02_QGIS_GPKG_Flood Modeller1D/ESTRY 1D Link | QGIS - GPKG]]
 
===Define PipeBoundary NetworkConditions===
The Flood Modeller 1D/ESTRY 1D Link could be employed for a number of reasons including:
This part of the module demonstrates how an inflow can be applied directly to the pits of the pipe network. A GIS layer of the inflow boundary is provided. The existing Boundary Conditions Database is also modified to include these new inflows. Instructions are available below for the preferred GIS format:
 
* [[FM Tutorial M02_QGIS_SHP_Boundary_Conditions | QGIS - SHP]]
*The inclusion of the powerful pipe network and manhole modelling capabilities of ESTRY within a Flood Modeller - TUFLOW linked model (see <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/DomainLinking-1.html#OneD2DLinkingFM-2 Section 10.5]</u> of the TUFLOW Manual for more details);
* [[FM Tutorial M02_QGIS_GPKG_Boundary_Conditions | QGIS - GPKG]]
*The further extension of a Flood Modeller Network within ESTRY to overcome Flood Modeller node licence limits;
*The representation of a steeper tributary in ESTRY which can then be connected to the main river represented in Flood Modeller.
 
==Flood Modeller 1D/ESTRY 1D Link==
Flood Modeller and TUFLOW (ESTRY) nodes will be considered linked if an ESTRY node in a 1d_nwk layer, and a Flood Modeller node in a <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/TCFCommands-1.html#tcfReadGISX1DNodes Read GIS X1D Nodes]</u> or <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/TCFCommands-1.html#tcfReadGISX1DNetwork Read GIS X1D Network]</u> layer are snapped together, or are within the snap tolerance distance specified.
This part of the module demonstrates how TUFLOW 1D (ESTRY) domains can be dynamically linked with Flood Modeller using "X1DH" and "X1DQ" links. FollowInstructions theare instructionsavailable below for yourthe preferred GIS format.:
 
* [[FM Tutorial M02_QGIS_SHP_Flood Modeller1D/ESTRY 1D Link | QGIS - SHP]]
ESTRY nodes are automatically generated at the upstream and downstream extremities of an ESTRY link so manually generating a node is not mandatory. If no node is manually added, then the Flood Modeller-ESTRY link is assumed to be an “X1DH” link. If an ESTRY is manually generated, then the ESTRY node can have a 1d_nwk layer Conn_1D_2D attribute of either “X1DH” or “X1DQ”.
* [[FM Tutorial M02_QGIS_GPKG_Flood Modeller1D/ESTRY 1D Link | QGIS - GPKG]]
 
The Flood Modeller 1D/ESTRY 1D Linklink couldcan be employed for a number of reasons, including:
An "X1DH" link means a Flood Modeller 1D water level is being applied at the ESTRY node (ie. Flood Modeller sends ESTRY a water level and ESTRY sends back a +/- flow to Flood Modeller). An ESTRY "X1DH" (the default) would be used for most Flood Modeller ESTRY links where ESTRY is discharging into a Flood Modeller network. The "X1DH" link is applied to the the Flood Modeller 1D network as a lateral inflow. The Flood Modeller 1D node connected to the ESTRY node by an "X1DH" connection must not be the end node of a reach.
 
*The inclusionInclusion of the powerful pipe network and manhole modelling capabilities of ESTRY within a Flood Modeller - TUFLOW linked model (see <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/DomainLinking-1.html#OneD2DLinkingFM-2 Section 10.5]</u> of the TUFLOW Manual for more details);.
An "X1DQ" link means a Flood Modeller inflow/outflow is being applied at the ESTRY node (ie. Flood Modeller sends ESTRY a +/- flow and ESTRY sends back a water level). This would be more apposite where a Flood Modeller network stops and flows into an ESTRY model. The Flood Modeller 1D node at the end of an "X1DQ" connection must be an HTBDY unit, although it isn't necessary for the HTBDY unit to contain any boundary data as this data will be overridden by the water levels provided by TUFLOW.
*The further extensionExtension of a Flood Modeller Networknetwork within ESTRY to overcome Flood Modeller node licence limits;.
*The representationRepresentation of a steeper tributary in ESTRY which can then be connected to the main river represented in Flood Modeller.
 
Flood Modeller and TUFLOW (ESTRY) nodes will beare considered linked if an ESTRY node in a 1d_nwk layer, and a Flood Modeller node in a <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/TCFCommands-1.html#tcfReadGISX1DNodes Read GIS X1D Nodes]</u> or <u>[https://docs.tuflow.com/classic-hpc/manual/2025.1/TCFCommands-1.html#tcfReadGISX1DNetwork Read GIS X1D Network]</u> layer are snapped together, or are within the snap tolerance distance specified.
 
ESTRY nodes are automatically generated at the upstream and downstream extremities of an ESTRY link, so manuallymanual generation generatingof a node is not mandatory. If no node is manually added, then the Flood Modeller-ESTRYModeller–ESTRY link is assumed to be an “X1DH” link. If an ESTRY node is manually generated, then the ESTRY node can have a 1d_nwk layer Conn_1D_2D attribute of either “X1DH” or “X1DQ”.
 
An "X1DH" link means a Flood Modeller 1D water level is being applied at the ESTRY node (iei.e. Flood Modeller sends ESTRY a water level and ESTRY sends back a +/- flow to Flood Modeller). An ESTRY "X1DH" link (the default) wouldis betypically used for most Flood Modeller ESTRY links where ESTRY is dischargingdischarges into a Flood Modeller network. The "X1DH" link is applied to the the Flood Modeller 1D network as a lateral inflow. The Flood Modeller 1D node connected to the ESTRY node by an "X1DH" connection must not be the end node of a reach.
 
An "X1DQ" link means a Flood Modeller inflow/outflow is being applied at the ESTRY node (iei.e. Flood Modeller sends ESTRY a +/- flow and ESTRY sends back a water level). This would beis more appositeappropriate where a Flood Modeller network stopsterminates and flows into an ESTRY model. The Flood Modeller 1D node at the end of an "X1DQ" connection must be an HTBDY unit, although it isn'tis not necessary for the HTBDY unit to contain any boundary data as this data will beis overridden by the water levels provided by TUFLOW.
 
=Modify Simulation Control Files=