Tutorial Module04 Archive: Difference between revisions

Content deleted Content added
No edit summary
 
(One intermediate revision by one other user not shown)
Line 29:
As with Modules 2 and 3 the GIS inputs are demonstrated in ArcGIS, MapInfo, SMS and QGIS. At each stage please select your GIS package for instructions.
==1D Cross-Sections==
A 1D model requires cross-sections for processing of the channel geometry. There are a number of different formats for cross-sections to be input to TUFLOW. In this module we will be using an offset-elevation approach (XZ). This is a typical format for inputting cross-sections however, other options include height-width (HW) and MIKE11 format inputs. These are not covered in this tutorial, however the general process is very similar. To save time, the locations and XZ profiles for the 1D cross sections are provided. The XZ profiles were automatically extracted from the DEM triangulation using the 12D software (www.12d.com) with the aid of the TUFLOW utility 12da_to_from_mif12da_to_from_GIS.exe using the -xs option (see [[12da_to_from_mif12da_to_from_GIS | 12da_to_from_mif12da_to_from_GIS wiki page]]). The SMS TUFLOW interface has a similar and easier process, noting that a licence for the SMS TUFLOW interface is required to save the cross-sections. It is more common for this information to come from surveyed cross-sections. If the survey has been provided as x-y-z points, or a a GIS layer of points, the xs_Generator utility can be used to create the cross-sections in a TUFLOW format. The xs_Generator utility is described in the [[XsGenerator |XsGenerator wiki page]].<br>
<br>
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>
Line 288:
*[[TUFLOW_Message_2060 | Error 2060 - Could not find a CN connection snapped to the end of HX line]]
*[[TUFLOW_Message_2024 | Error 2024 - Could not find a 1D node snapped to CN line.]]
*[[Only_TUFLOW_DOS_Window_ArchiveOnly_TUFLOW_Console_Window_Archive | Why does the TUFLOW console window open, though the TCF isn’t read and the simulation doesn’t execute?]]
 
= Advanced - HPC Solver (Optional) =