MIKE Flood to TUFLOW: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) |
|||
| (10 intermediate revisions by 4 users not shown) | |||
Line 1:
=Introduction=
This page provides guidance on a generalised method to convert a MIKE FLOOD model to a TUFLOW model format. MIKE
==Requirements==
Line 7:
* xsGenerator.exe (for MIKE11 conversion)
MIKE Zero is required to extract data from the MIKE FLOOD model. The xsGenerator utility is freely available from the <u>[
=Creating a TUFLOW Geometry Control File from MIKE21=
Line 48:
</ol>
More information on reading in manning’s grids into TUFLOW is provided in the <u>[https://
===TUFLOW Commands===
Line 70:
The Domain in TUFLOW can now be set up in the TGC. Below is an example of how the Domain could be created, however there are several methods that could be used. The domain should always be checked by viewing the <b>dom_check</b> file. Be careful when translating a rotation from MIKE to TUFLOW, as they process the origin slightly differently.<br><br><font color='green'><tt>! Set model domain</tt></font><br><font color='blue'><tt>Origin</tt></font> <font color='red'><tt>==</tt></font> <tt>''<X>'', ''<Y>''</tt><br><font color='blue'><tt>Orientation Angle</tt></font> <font color='red'><tt>==</tt></font> <tt>''<angle_in_degrees_relative_to_east>''</tt><br><font color='blue'><tt>Grid Size (X, Y)</tt></font> <font color='red'><tt>==</tt></font> <tt>'' <X_length>'', ''<Y_length>''</tt>
<br>More information on setting the model domain extent and rotation in TUFLOW is provided in the <u>[https://
==TUFLOW Code Layer==
The user can manually set the TUFLOW code layer by viewing the terrain data through their preferred GIS program. MIKE also uses a process of defining active cells by specifying a ‘Land’ elevation value. A ‘Land’ elevation value is defined in the .dsf2 grid file that specifies a value at which elevations equal to or greater than this value are considered ‘Land’ and will not be subject to possible wetting and drying. This value could be used as a guidance for producing a TUFLOW code layer. The 'Land' value can be found in <b>Custom Blocks</b>, the same location as grid rotation. Following the same steps as above in determining rotation, the 'Land' value can be determined, this time looking at the fourth element value.<br>[[File: MikeZero-Edit-CustomBlocks.PNG|350px|]]
Line 138:
The location of source boundaries can be found in the MIKE21 control file (.m21) in the <b>Basic Parameters</b> >> <b>Source and Sink</b> tab. The location of the boundaries are specified as a point object using the local (j, k) coordinate system. These are required to be converted to absolute coordinates so an identical boundary location can be digitised in TUFLOW. The conversion process can be undertaken using identical steps as performed with converting upstream and downstream boundaries.
It is recommended that the source boundary point from MIKE be converted to a 2d_SA polygon in TUFLOW. The 2d_SA polygon should be enlarged to encompass a larger region such that it is able to apply flow to more than one cell. This is considered to give a more stable and accurate representation of flow distribution to the model. More information on how 2d_SA polygons distributes flow can be found in the <u>[https://
The name of the boundary can be found from <B>Hydrodynamic Parameters</b> >> <b>Source and Sink</b> tab.<br>[[File: MIKE21-HP-Source-Names.PNG|750px|]]
Line 151:
==1D/2D Linking Boundaries==
The location of the 1D / 2D boundaries can be found in the MIKE Flood control file (.couple) under the <b>Link Definitions</b> tab. The (X, Y) coordinates specify the vertices of a polyline that can be digitised in TUFLOW using either ‘SX’ or ‘HX’ connections. Link Type <b>Standard</b> is similar to 'SX' connections, <b>Lateral</b> to 'HX' connections and <b>River/Urban</b> is for connections from Mike Urban package.<br>[[File: MIKEFlood-Linkages.PNG|750px|]]
More information on 1D/2D linking in TUFLOW can be found in the <u>[https://
===TUFLOW Command===
Line 179:
</ol>
The time series will need to be formatted so that the time column units are in hours. This can be done in MS Excel or equivalent. More information on setting up inflow boundaries can be found in the <u>[https://
=Creating an Estry Control File from MIKE11=
Line 196:
* Projection.mif (or Header.mif)
* The MIKE11 .nwk11
* The MIKE11 .
* The MIKE11 exported <Cross_sections>.txt
Line 234:
<font color='blue'><tt>Read GIS Table Links</tt></font> <font color='red'><tt>==</tt></font> <tt>..\model\xs\''<1D Cross Sections>''.shp</tt>
Water Level Lines can also be used to view the 1D results in the 2D mapping. For more explanation on Water Level Lines, please see the <u>[https://
<font color='green'><tt>! Read 1D Water Level Lines</tt></font><br>
Line 277:
<li> You can obtain the start and end dates from this tab which need to be converted to hours for TUFLOW (in the screenshot below, the simulation duration is 3 hours)<br>[[File: MIKE21-Simulation-Period.PNG]]
</ol>
The 2D timestep should be set to an appropriate TUFLOW interval and not be copied directly from the MIKE21 model. It also up to the user to consider output types and time series Plot Output (PO) locations. More information on appropriate timestep intervals and map output types can be found in the <u>[https://
===TUFLOW Commands===
Line 308:
<font color='blue'><tt>Maximums and Minimums Only For Grids</tt></font> <font color='red'><tt>==</tt></font> <tt>ON</tt> <font color='green'><tt>! Writes maximums only for grid type output formats e.g. asc types</tt></font><br>
{{Tips Navigation
|uplink=[[Main_Page| Back to Main Page]]
}}
| |||