MIKE Flood to TUFLOW: Difference between revisions
Content deleted Content added
Ellis Symons (talk | contribs) |
Ellis Symons (talk | contribs) No edit summary |
||
Line 140:
=Creating an Estry Control File from MIKE11=
This section discusses how to extract data from a MIKE11 model to create an Estry Control File (ECF). An ECF file defines the:
* 1D network – Channels, structures
* 1D cross sections
* 1D boundaries
* 1D run settings
==
To make the conversion of the MIKE11 1D network easier, the xsGenerator utility has been built to automate the bulk of the conversion. The xsGenerator.exe utility is freely available to download from the <u>[https://www.tuflow.com/Tuflow%20Utilities.aspx TUFLOW website]</u>.
To undertake the automation, a number of files will be required as inputs:
* Projection.mif (or Header.mif)
* The MIKE11 .nwk11
* The MIKE11 .bd11
* The MIKE11 exported <Cross_sections>.txt
At this time, the utility is only able to output to .mif and this would need to be converted to .shp if required.
Cross section from MIKE11 can be exported by following the steps below:
<ol>
<li> Open MIKE Zero
<li> Open the .xns11 through <b>Open</b> (or drag and drop)
<li> Select <b>File</b> >> <b>Export All Sections</b> >> <b>Export Raw Data…</b>
<li> Save the cross sections out as a .txt file<br>[[File: MIKE11-xns11-export.PNG|750px]]
</ol>
The final step is to convert the network data into TUFLOW format. This can be done by creating a batch file to run the utility. Below is an example of the arguments used to convert the MIKE11 network. Documentation on the utility can be found on the [[XsGenerator|xsGenerator wiki page]]<br><tt>xsGenerator.exe -N -m11 Projection.mif XS_example.txt HD_example.hd11 M11_example.nwk11</tt>.
After the conversion is complete it is important to check the output. Some key areas to check are:
* The 1d_nwk.mif file appears to have created channels at reasonable locations
* The 1d_nwk.mif ‘Type’ attribute is correct (currently the utility will assign all channels to type ‘S’ (see below for checking for culverts in MIKE11)
* The 1d_xs.mif file appears to be at reasonable locations (if the cross sections in MIKE11 didn’t have X,Y coordinates, then the equivalent 1d_xs cross sections can look strange)
** TUFLOW also does not require cross sections at embedded 1D/2D culverts, therefore cross sections at these locations can be deleted
* The created cross section .csv files are reasonable (geometry and manning’s values)
The following steps describe how to inspect channel locations and types in MIKE11 for the purpose of checking the utility output:
<ol>
<li> Open MIKE Zero
<li> Open the .nwk11 file through <b>Open</b> (or drag and drop)
<li> This will display the network spatially<br>[[File: MIKE11-nwk11-map.PNG]]
<li> To view the details, select <b>View</b> >> <b>Tabular View…</b>
<li> From this screen you view information on <b>Structures</b> that you can use to populate attributes in the 1d_nwk TUFLOW layer<br>[[File: MIKE11-nwk11-tablular.PNG|750px]]
</ol>
==1D Boundaries==
The following steps will help identify the types of 1D boundaries and the attributes used in MIKE11 for transfer to TUFLOW:
<ol>
<li> Open MIKE Zero
<li> Open the .bnd11 file through <b>Open</b> (or drag and drop)
<li> This will display all 1D boundaries<br>[[File: MIKE11-bnd11.PNG]]
</ol>
Identifying the boundary types and values is as simple as reading the Boundary Type, TS Type, and File/Value. The only thing to be careful of is that 1D/2D linking boundaries are usually specified as Water Level and won’t need to be transferred across (1D/2D linking conversion has already been discussed in [[MIKE_Flood_to_TUFLOW#1D.2F2D_Linking_Boundaries|Section 3.3]]).
==1D Run Settings==
The 1D run settings can be obtained from the .sim11 file. However it is recommended that appropriate run settings for TUFLOW be applied and direct copies from MIKE are not necessary.
=Creating a TUFLOW Control File from MIKE21=
| |||