TUFLOW Empty Files: Difference between revisions
Content deleted Content added
No edit summary |
|||
| (9 intermediate revisions by 3 users not shown) | |||
Line 1:
=Introduction=
The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the <u>[https://
<center>[[File:2d zsh fields.png]]<br></center>
Line 17:
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <font color="blue"><tt>Read GIS Auto Terminate</tt></font> <font color="red"><tt>==</tt></font> || Used to define locations where auto terminate tracking is desired.
|-
| rowspan=2| '''2d_cyc_empty''' || <font color="blue"><tt>Read GIS Cyclone</tt></font> <font color="red"><tt>==</tt></font> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
Line 40:
| rowspan=2| '''1d_wllp_empty''' || <font color="blue"><tt>Read GIS XP WLL Points</tt></font> <font color="red"><tt>==</tt></font> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <font color="blue"><tt>Read GIS
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type:<br>
Line 55:
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>==</tt></font> || Used to define the location and type of 1D boundary condition input.
|-
| '''1d_iwl_empty''' || <font color="blue"><tt>Read GIS IWL </tt></font> <font color="red"><tt>==</tt></font> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
Line 77:
| '''1d_tab_empty''' || <font color="blue"><tt>Read GIS Table Links </tt></font> <font color="red"><tt>==</tt></font> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''
|-
| '''1d_wllp_empty''' || <font color="blue"><tt>Read GIS WLL Points </tt></font> <font color="red"><tt>==</tt></font> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
Line 95:
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-▼
| '''2d_ad_ic_empty''' || <font color="blue"><tt>Read GIS IGW Conc Layer N1,N2,...N Tracer M1,M2,...M</font><font color="red"> ==</tt></font> || Sets the spatial distribution (polygons) of the initial concentrations for a given tracer (M1,M2,..,M) in the TUFLOW AD module. This layer is read into the initial condition field of the AD Global Database (.csv) file.<br>
|-
| '''2d_ad_md_empty''' || <font color="blue"><tt>Read GIS IGW Conc Layer N1,N2,...N Tracer M1,M2,...M</font><font color="red"> ==</tt></font> || Sets the spatial distribution (polygons) of the minimum dispersion coefficients for a given tracer (M1,M2,...,M) in the TUFLOW AD module. This layer is read into the minimum dispersion field of the AD Global Database (.csv) file.<br>
|-
| rowspan=2|'''2d_bc_empty''' || <font color="blue"><tt>Read GIS Code BC</tt></font> <font color="red"><tt>==</tt></font> || Used to set the code status of a cell (active or inactive). <br>
Line 111 ⟶ 115:
| <font color="blue"><tt>Read GIS Code INVERT</tt></font> <font color="red"><tt>==</tt></font> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <font color="blue"><tt>Read GIS Code</tt></font> <font color="red"><tt>==</tt></font> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in <u>[[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]]</u>.
|-
|
▲|-
|-
| '''2d_fcsh_empty''' || <font color="blue"><tt>Read GIS FC Shape</tt></font> <font color="red"><tt>==</tt></font> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
Line 139 ⟶ 141:
| '''2d_rec_empty''' || <font color="blue"><tt>Read GIS Objects</tt></font> <font color="red"><tt>==</tt></font>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <font color="blue"><tt>Read GIS Soil</tt></font> <font color="red"><tt>==</tt></font> || Used to define 2D soil type inputs for infiltration parameterisation.
|-
| '''2d_sx_empty''' || <font color="blue"><tt>Read GIS Z Line</tt></font> <font color="red"><tt>==</tt></font> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
Line 191 ⟶ 193:
|-
| <font color="blue"><tt>Read GIS Streams</tt></font> <font color="red"><tt>==</tt></font>
|-
| '''2d_sa_po_empty''' || <font color="blue"><tt>Read GIS SA PO</tt></font> <font color="red"><tt>==</tt></font> || Used to define areas (polygons) of seepage or infiltration that depend on varying water level or flow rate elsewhere in the model. This model input is used with the TCF command, <font color="blue"><tt>Read GIS PO</tt></font> <font color="red"><tt>==</tt></font>.
|-
| '''2d_sa_rf_empty''' || <font color="blue"><tt>Read GIS SA RF</tt></font> <font color="red"><tt>==</tt></font> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <font color="blue"><tt>Read GIS SA Trigger</tt></font> <font color="red"><tt>==</tt></font> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| '''2d_strm_empty''' || <font color="blue"><tt>Read GIS Streams</tt></font> <font color="red"><tt>==</tt></font> || Used to define streamlines that are used in conjunction with the '<font color="blue"><tt>Read GIS SA</tt></font>' or '<font color="blue"><tt>Read GIS SA Stream Only</tt></font>' commands.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type:<br>
| |||