Flood Modeller Tutorial Module02: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) No edit summary |
|||
| (18 intermediate revisions by 4 users not shown) | |||
Line 7:
*The addition of pipes and pits to represent an underground drainage network;
*Linking the pipe network to Flood Modeller; and
*The addition of an inflow into the pipe network.<br>
<br>▼
=GIS and Model Inputs=
The steps necessary to modify each of the GIS inputs are demonstrated in MapInfo, ArcGIS and QGIS. At each stage please select your GIS package to view relevant instructions.
Line 16:
* [[FM Tute M02_ARC_Define_Elevations | ArcGIS]]
* [[FM Tute M02_MI_Define_Elevations | MapInfo]]
* [[FM Tute M02_QGIS_Define_Elevations | QGIS]]<br>
==Define Surface Roughness==
We have provided the GIS layers necessary to modify the land use areas that will change as part of the proposed development. This part of the tutorial will require populating the layer attributes to assign Manning’s n roughness values to each land use. Follow the instructions below for your preferred GIS package.
Line 32 ⟶ 33:
* [[FM Tute M02_MI_Boundary_Conditions | MapInfo]]
* [[FM Tute M02_QGIS_Boundary_Conditions | QGIS]]
===Flood Modeller/ESTRY 1D/1D Link===
TUFLOW models can also be configured with Flood Modeller for dynamically linked 1D pipe network 2D overland flow modelling. The main driver for this feature is for Flood Modeller - TUFLOW models to utilise the powerful pipe network and manhole modelling capabilities of TUFLOW (see
<br>
Flood Modeller and TUFLOW (ESTRY) nodes will be considered linked if:<br>
<ol>
<li> An ESTRY node in a 1d_nwk layer, and a Flood Modeller node in a Read GIS
<li> The ESTRY node has a 1d_nwk Conn_1D_2D attribute of either "X1DH" or "X1DQ".</li>
::(i) If Conn_1D_2D is blank then “X1DH” is assumed.
Line 45 ⟶ 46:
<li> 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). </li>
<li> An ESTRY X1DH (the default) would be used for most Flood Modeller ESTRY links. An X1DQ might be more appropriate where a Flood Modeller model stops and flows into an ESTRY model.<br>
Generally, an ESTRY timestep will be smaller than the Flood Modeller timestep. In these cases, the total volume is accumulated over all ESTRY timesteps within a Flood Modeller timestep, and applied to the Flood Modeller model as a discharge by dividing the volume by the Flood Modeller timestep.
The mass balance _MB1D.csv file includes four new columns:
Line 54 ⟶ 55:
The type or existence of a connection can be checked by viewing the Conn_1D_2D attribute in the 1d_nwk_N_check layer. The _messages.mif/.shp layer contains CHECK 1393 messages at each ESTRY node linked to a Flood Modeller node.
<br>
=Modify Simulation Control Files=
Now that we have made all of the necessary changes to the GIS layers, we need to update our control files to include all the changes representing the proposed development.
Line 68 ⟶ 70:
<br>
<li>We will now add the commands to modify the topography to represent the proposed development. Add the following commands after the READ GIS Z Shape line:</li>
:<font color="blue"><tt>Create TIN Zpts WRITE TIN </tt></font><font color="red"><tt>==</tt></font> mi\
▲:<font color="blue"><tt>Create TIN Zpts WRITE TIN </tt></font><font color="red"><tt>==</tt></font> mi\2d_ztin_FMT_M02_development_001.MIF | mi\2d_ztin_ FMT_M02_development_001.MIF </li>
The <font color="blue"><tt>Create TIN Zpts Write TIN </tt></font> command creates and writes an SMS .tin file to the same location as the GIS layer (in this case the TUFLOW\model\mi folder). The TIN can be viewed, checked and modified in SMS. This can then be read into the model directly using the <font color="blue"><tt>Read TIN zpts</tt></font> command for any subsequent model simulations.
<br>
Our intention for the 2d_mat layers created in this module is for them to build upon the existing commands which modify roughness. We would like for the new layers to overwrite the existing layers at the location of the proposed development. This process of layering and building up the model is a powerful tool in TUFLOW that minimises data duplication and provides a means of quality control. We need to ensure that the commands reading in our new 2d_mat layers are read in after the existing commands.
<br>
:<font color="blue"><tt>Read GIS Mat</tt></font><font color="red"><tt>==</tt></font> mi\
:<font color="blue"><tt>Read GIS Mat</tt></font><font color="red"><tt>==</tt></font> mi\
'''QGIS or ArcGIS Users'''
<br>
<li>We will now add the commands to modify the topography to represent the proposed development. Add the following commands after the READ GIS Z Shape line:</li
:<font color="blue"><tt>Create TIN Zpts WRITE TIN </tt></font><font color="red"><tt>==</tt></font> gis\2d_ztin_FMT_M02_development_001_R.shp | gis\2d_ztin_ FMT_M02_development_001_P.SHP </li>
The <font color="blue"><tt>Create TIN Zpts Write TIN </tt></font> command creates and writes an SMS .tin file to the same location as the GIS layer (in this case the TUFLOW\model\gis folder). The TIN can be viewed, checked and modified in SMS. This can then be read into the model directly using the <font color="blue"><tt>Read TIN zpts</tt></font> command for any subsequent model simulations.
Line 91 ⟶ 88:
:<font color="blue"><tt>Read GIS Mat</tt></font><font color="red"><tt>==</tt></font> gis\2d_mat_FMT_M02_DEV_Buildings_001_R.MIF
<li> Save the file. The .tgc file is now ready to be used.</ol
==ESTRY Control File==
Line 105 ⟶ 102:
'''MapInfo Users'''<br>
<li> Add the following commands at the bottom of the file as follows:
:<font color="blue"><tt>Read GIS Network</tt></font> <font color="red"><tt>==</tt></font> mi\
:<font color="blue"><tt>Read GIS Network</tt></font> <font color="red"><tt>==</tt></font> mi\
:<font color="blue"><tt>Pit Inlet Database</tt></font> <font color="red"><tt>==</tt></font> ..\pit_dbase\pit_inlet_dbase.csv
Line 115 ⟶ 112:
:<font color="blue"><tt>Pit Inlet Database</tt></font> <font color="red"><tt>==</tt></font> ..\pit_dbase\pit_inlet_dbase.csv
<li>Save the file. The 1D control file is now ready to be used.</ol
==TUFLOW Boundary Condition File==
Line 125 ⟶ 122:
'''MapInfo Users'''<br>
<li>Insert the following commands after the existing <font color="blue"><tt>Read GIS SA</tt></font><font color="red"><tt> ==</tt></font> mi\
:<font color="blue"><tt>Read GIS SA PITS</tt></font><font color="red"><tt> ==</tt></font> mi\
'''QGIS or ArcGIS Users'''<br>
Line 151 ⟶ 148:
==Flood Modeller Simulation Files==
<ol>
<li>Open the Flood Modeller Pro model as per [[Flood_Modeller_Tutorial_Module01
<li>In the 'Links' tab with the 2D scheme set as TUFLOW, change the full path of the 2D control file to the <b>FMT_M02_DEV_001.tcf</b> from the <b>\FMT_Tutorial\FMT_M02\TUFLOW\runs</b> folder
<li>Save the Scenario Data.</li></ol>
Use your preferred method to start the model <b>FMT_M02_001.ief</b> or follow the guidance in the [[Flood_Modeller_Tutorial_Module01
=Review Check Files=
Line 170 ⟶ 167:
From the <b>TUFLOW\check\2d\</b> folder import (into MapInfo) or open (ArcMap and QGIS):
*FMT_M02_001_grd_check
The grd_check file contains information on all cells within the model extent, such as ZC elevation and the location of the cell in relation to the model origin. One of the attributes of this check layer is the Material ID assigned to each cell. A review of this check file is recommended particularly when using multiple GIS layers to define the roughness of a 2D domain. The file can be colour coded to provide a visual representation of the roughness assigned to the entire model extent by:
Line 203 ⟶ 200:
[[File:M07 ccA Results.PNG|800px]]
=Conclusion=
We have added to the model a final proposed development scenario. Using the Create TIN Zpts command, we have altered the ground elevations to represent the development. We have also added a 1D pipe network which has been linked to the 2D domain as well as feeding flows in the 1-dimensional channel represented within Flood Modeller. A pit inlet database has been created to specify a depth-discharge relationship for flow into and out of the pits. This allows us to create a fully integrated urban drainage model comprises 1D representations of the pipe network and river system together with the 2D surface.<br>
For further training opportunities see <u>[https://tuflow.com/training/training-course-catalogue/ TUFLOW Training Catalogue]</u> and/or contact <u>[mailto:training@tuflow.com training@tuflow.com]</u>. <br>
▲<br>
{{Tips Navigation
|uplink=[[Flood_Modeller_Tutorial_Model| Back to Flood Modeller Tutorial Model]]
}}
| |||