TUFLOW Empty Files: Difference between revisions

Content deleted Content added
No edit summary
Line 101:
|-
| <font color="blue"><tt>Read GIS Z HX Line</tt></font> <font color="red"><tt>==</tt></font> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <font color="blue"><tt>Read GIS BG Shape</tt></font> <font color="red"><tt>==</tt></font> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
| '''2d_bg_empty_pts''' || <font color="blue"><tt>Read GIS BG 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 includes accounts for flow above and below the bridge obvert (soffit).
|-.
|-
| rowspan=2|'''2d_code_empty''' || <font color="blue"><tt>Read GIS Code</tt></font> <font color="red"><tt>==</tt></font> || Used to set the code status of a cell (1 = active or 0 = inactive).
Line 121 ⟶ 122:
|-
| <font color="blue"><tt>Read GIS GWD</tt></font> <font color="red"><tt>==</tt></font>
|-
| '''2d_hx_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.
|-
| '''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.
|-
| '''2d_iwl_empty''' || <font color="blue"><tt>Read GIS IWL</tt></font> <font color="red"><tt>==</tt></font> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
Line 144 ⟶ 149:
| '''2d_z_empty''' || <font color="blue"><tt>Read GIS Z Line</tt></font> <font color="red"><tt>==</tt></font> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <br> <font color="blue"><tt>Read GIS GIS Z Shape</tt></font> <br>
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <font color="blue"><tt>Read GIS Zpts</tt></font> <font color="red"><tt>==</tt></font> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <font color="blue"><tt>Read GIS Z Line</tt></font> <font color="red"><tt>==</tt></font> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <font color="blue"><tt>Read GIS Z Line</tt></font> <font color="red"><tt>==</tt></font> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <font color="blue"><tt>Read GIS Z Line</tt></font> <font color="red"><tt>==</tt></font> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <font color="blue"><tt>Read GIS Zpts</tt></font> <font color="red"><tt>==</tt></font> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <font color="blue"><tt>Read GIS Z Shape</tt></font> <font color="red"><tt>==</tt></font> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.