Tutorial Module04 Archive: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
Line 33:
For each cross-section there is an individual comma separated variable (.csv) file. The 1d_xs layer contains a link to the source .csv file at every cross-section location. <br>
For <u>'''SMS'''</u> Users
:* [[
For <u>'''ArcGIS, MapInfo and QGIS'''</u> Users
<ol>
Line 40:
<li> Interrogate one of the cross-section lines to inspect the attributes. Notice that each line has a unique name as shown in the '''Source''' attribute, e.g. FC01 ch0834.csv. This name describes the cross section as belonging to channel FC01 at chainage 0834. The '''Type''' attribute "XZ" indicates that this cross-section is an offset-elevation type section.</li>
<li> In the GIS platform a "hotlink" can be created to allow the user to open the .csv file in excel, allowing the user to easily visualise the section using an XY scatter chart type. To enable hotlinking select your GIS platform below:
* [[
* [[
* [[
</ol>
''Tip: The XY scatter plot can be setup as the default chart type in excel, this makes it simple to plot the cross-sections, simply open the .csv in Excel using the GIS hotlink functionality, select the data and the hit the F11 key to create a chart. Instructions for setting an x-y scatter as the default chart type can be found in this [[EXCEL_setting_default_chart | Excel tip]].<br>
''For MapInfo users with the miTools utility, the cross-sections can be viewed directly within MapInfo, instructions for doing so are in the [[
''Users with the SMS-TUFLOW interface can also directly view the cross-sections in the [[
==1D Channels==
Line 57:
<br>
As the cross sections have been provided, the digitisation of the channel is simply a matter of joining the dots. We are going to create a series of lines between the cross sections. It is important that the end of each channel snaps to a vertex along the cross-section line, so we will be using the snapping tools in the GIS. We have provided a 1d_nwk_M04_creek_001 GIS layer. This layer has the first few channels digitised for you. A revised culvert layer '''1d_nwk_M04_creek_001''' is also provided, this has the culverts connected to the new channels layer. The creation of the 1d network layers is described for the GIS packages below:
*[[
*[[
*[[
*[[
==1D/2D Links==
Line 84:
<br>
Now that we have a background in the linking approach it is time to define the 1D/2D link. This process is described for the various GIS packages in the links below:
*[[
*[[
*[[
*[[
==2D Breaklines==
As mentioned above, the water level from the 1D is transferred out to the 2D HX cells. Therefore, it is important that the 2D cell elevation reflects the level when water can spill out into the 2D. The water level computation point for the 2D cells is the cell centre, therefore it is important to use a "thick" breakline. The types of breaklines was discussed further when reviewing the check files for the previous module <u>[[
In the image below, the lightly shaded cells are the 1D/2D boundary cells. The black labels are the elevations with no breakline (elevation as read from the DEM). At the circled cell, the cell centre elevation is 44.35, this controls when water can spill from the 1D to the 2D. The red line indicates the true top of bank; the labels are elevations along this line. If this is included as a breakline, the elevations are as labelled in yellow. In this case, the level at the circled cell is actually 44.57. Including breaklines for the top of bank is important, particularly if there is an embankment or levee.
<br>
Line 96:
<br><br>
To include breaklines for the top of bank, follow the instructions outlined in your GIS package below.
*[[
*[[
*[[
*SMS: SMS automatically extracts elevations for the HX lines when we export the TUFLOW files. Please proceed to the next section.
Line 105:
<br>
As the HX line was created along the top of bank and was as wide as the cross-sections, we can snap the code polygon (which deactivates the 2D cells) to the HX line. To do this please select your GIS package from the list below:
*[[
*[[
*[[
*[[
==Define Boundary Conditions==
Line 117:
<br>
For the GIS changes please select your GIS package from the list below.
* [[
* [[
* [[
* [[
=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 utilise the new GIS layers. Now that the 1D component of the model is becoming more complex we are going to use a separate control file for the 1D inputs. The new 1D control file will have the extension .ecf, this stands for <u>'''E'''</u>STRY <u>'''C'''</u>ontrol <u>'''F'''</u>ile. ESTRY was a 1D hydraulic modelling package before TUFLOW was created. The functionality of ESTRY has been incorporated in TUFLOW but for historic reasons the 1D control file is still referred to as the ESTRY Control File and has the .ecf file extension.<br>
'''SMS''' users do not need to modify the control files manually because SMS writes out the control cards and files automatically while exporting the TUFLOW project. Please proceed to ''[[
==TUFLOW Control File (TCF)==
<ol>
Line 155:
</ol>
==ESTRY Control File (ECF)==
'''SMS''' users do not need to modify the control files manually because the control cards/files are automatically generated by SMS while exporting TUFLOW files. Follow ''[[
For all other model development platforms (eg. ArcGIS, QGIS, MapInfo etc.)<br>
Line 283:
This section contains links to some possible problems that may occur when progressing through the fourth tutorial module. If you experience an issue that is not detailed, please email support@tuflow.com or add and describe the problem on the <u>[[Talk%3ATutorial_Module04_Archive | discussion page.]]</u><br>
*[[
*[[
*[[
*[[
*[[
*[[
= Advanced - HPC Solver (Optional) =
| |||