= Introduction =
The following tutorial models are aimed at new and experienced users, stepping through the process of building and running TUFLOW SWMM together. The main objective aims to demonstrate the ability for TUFLOW to link to 1D EPA SWMM in a variety of different common use case scenarios. 

TUFLOW has supported 1D/2D dynamic coupling since its initial 2D solver development in 1989. Traditionally, 1D (1 Dimensional) linking and associated modelling has been applied using TUFLOW's 1D solver, ESTRY. As demonstrated in:
:*[[Tutorial_M03 | Module 3 - 1D Culverts]]
:*[[Tutorial_M05 | Module 5 - Integrated Urban Pipe Network Drainage]]
:*[[Tutorial_M11 | Module 11 - 1D Open Channel]] 
New in 2023, TUFLOW's 1D linking and solver options have been expanded to include EPA Storm Water Management Model (SWMM). EPA SWMM is a widely used software for simulating urban and non-urban watersheds' hydrologic and 1D hydraulic behaviour. Initially developed in the early 1970's by the USA Environmental Protection Agency (EPA), the software has since undergone numerous updates and enhancements to become one of the most used 1D stormwater runoff and water quality analysis tools globally, particularly in North America. The primary uses of EPA SWMM include designing and evaluating stormwater systems and also planning and assessment of low-impact development (also known as Water Sensitive Urban Design) techniques. For more details about EPA SWMM, please visit: [https://www.epa.gov/water-research/storm-water-management-model-swmm https://www.epa.gov/water-research/storm-water-management-model-swmm]. Note, if you are not already familiar with TUFLOW, we recommend first completing Module 1 and 2 of the [[Tutorial_Introduction | "TUFLOW Only" Tutorials]] to establish an understanding of 2D modelling, before progressing to learning how to link 1D EPA SWMM to 2D TUFLOW.

=Software Requirements=
TUFLOW uses QGIS as its Graphical User Interface (GUI), in combination with text editor and spreadsheet software, for its model creation and result viewing. The group of software creates an extremely workflow efficient and flexible modelling environment. Notably, QGIS does not experience the data load/visualisation lag and display issues some other hydraulic modelling software GUIs are limited by when working with larger datasets. 

{| class="wikitable" width="75%"

! style="background-color:#005581; font-weight:bold; color:white;"| Requirement
! style="background-color:#005581; font-weight:bold; color:white;" | Brief Description
! style="background-color:#005581; font-weight:bold; color:white;" | Download
|-
| '''TUFLOW''' || TUFLOW is a computer program for simulating depth-averaged, one and two-dimensional free-surface flows such as occurs from floods and tides, with the 2D solution occurring over a regular grid or quadtree mesh of square elements. 
It is recommended to always use the latest release version of TUFLOW. 

This tutorial model does not require a TUFLOW licence. 

This tutorial is configured to use a NVIDIA GPU card. If this is not available, your CPU can be used via the Hardware command. 
||The TUFLOW executable is provided within the [[TUFLOW_SWMM_Tutorial_Introduction#Tutorial_Data | Tutorial Download Dataset]].
|-
| '''QGIS''' QGIS TUFLOW plugin || QGIS is the Geographic Information System (GIS) Graphical User Interface (GUI) used to build models and view results. The QGIS TUFLOW plugin includes numerous tools to increase workflow efficiency.

This tutorial was developed using QGIS 3.34 and QGIS TUFLOW Plugin 3.9.0.49. Please use these or newer versions of QGIS and the plugin. Earlier releases will not include the TUFLOW SWMM automation tools demonstrated in the Tutorials .

||[https://qgis.org/en/site/forusers/download.html Latest 64-bit version of QGIS]. 

[[TUFLOW_QGIS_Plugin| QGIS TUFLOW Plugin Installation]].
|-
| '''NotePad++''' Syntax Highlighting || A text editor is required for creation of the TUFLOW control (script) files. This tutorial was developed with NotePad++. Ideally a text editor should be able to: 
*Color code the TUFLOW control files;
*Open other files from the active control file; and
*Launch a TUFLOW simulation. 
TUFLOW colour coding can be enabled using syntax highlighting.
|| [https://notepad-plus-plus.org/downloads/ Latest 64-bit version of Notepad++]. 

[https://www.tuflow.com/Download/Miscellaneous/NPP_TUFLOW_Syntax_Highlighting.zip TUFLOW syntax highlighting for Notepad++]. 

For instructions on configuring Notepad++ for TUFLOW modelling, see [[NotepadPlusPlus_Tips |Notepad++ tips]].
|-
| '''Microsoft Excel''' || A spreadsheet software is required for working with tabular data and .csv files. This tutorial has been created using Excel. ||
|}

 

=Tutorial Data=
To build the tutorial model, download the dataset below. This includes a digital elevation model (DEM), aerial photography, background model data for the tutorial model and a working version of the model. GeoPackage has been used as the GIS format for the model build tasks. For tips on using Geopackage see [https://wiki.tuflow.com/GeoPackage_Tips GeoPackage Tips].
:*[https://downloads.tuflow.com/TUFLOW/Wiki_Tute_Models/TUFLOW_SWMM_Tutorial_Models_QGIS_GPKG.zip TUFLOW SWMM Tutorial Dataset - QGIS - GPKG]

=Tutorial Modules=
The download dataset contains the input files and working version of the tutorial model for reference. Results and check files are not included to keep the size of the download file manageable, they can be created by running the model simulations. The folder should be placed in a location with write permissions. 

The tutorial model is presented in a number of modules. All modules can be completed independently, however new users are encouraged to undertake the modules in sequence:

:*[[TUFLOW_SWMM_Tutorial_M01 | TUFLOW SWMM Module 1]] - 1D SWMM Culverts
:*[[TUFLOW_SWMM_Tutorial_M02 | TUFLOW SWMM Module 2]] - 1D SWMM Pipe Network / 2D Direct Rainfall Hydrology
:*[[TUFLOW_SWMM_Tutorial_M03 | TUFLOW SWMM Module 3]] - 1D SWMM Pipe Network / 1D SWMM Urban Hydrology

=Recommended Further Reading=
For users who wish to get a better understanding of either 1D EPA SWMM or 2D TUFLOW, the following resources may be of use:
*[https://www.epa.gov/water-research/storm-water-management-model-swmm EPA SWMM User Manual]
*[https://www.tuflow.com/downloads/#tuflow TUFLOW User Manual]
*[https://docs.tuflow.com/classic-hpc/release/2023-03-AD TUFLOW 2023-03-AD release notes]
*[[Tutorial_Introduction#Tutorial_Modules | TUFLOW Tutorial Models]]

{{Tips Navigation
|uplink=[[Main_Page| Back to Main Page]]
}}

File:Bridge rail debris.jpg

2021-02-10T05:12:38Z

Bill Syme:

2020-09-22T04:04:51Z

Bill Syme:

1D Bridges

2020-07-20T01:53:34Z

Bill Syme:

Page Under Construction
 
 
 
=Introduction=
The following section looks at bridges using the 1D component of TUFLOW. Reference should also be made to the section on 1D bridges in the TUFLOW Manual. For information on bridges in the 2D domain please see the following section on [[TUFLOW_2D_Hydraulic_Structures | 2D hydraulic Structures]] and [[Tutorial_Module06#Bridge_Modelling_Option_3:_2D_Layered_Flow_Constriction | Module 6]]. 
1D Bridge channels do not require length, Manning's n, divergence or bed slope (so they are effectively zero-length channels in terms of conveyance) and rely on a reasonable estimate of energy losses associated with re-expansion of water after the vena-contracta (often referred to as entrance losses), expansion of water downstream (exit losses), pier losses, bridge deck and guard rail losses. Other factors include accounting for occurrence of bridge deck pressure flow and the effects of bridge skew and multiple bridges (shielding effects of an upstream bridge on a downstream bridge). 

Care must be taken when choosing the approach to modelling the bridge and setting appropriate loss values.

TUFLOW offers two 1D bridge channels, B and BB. BB channels were introduced for Build 2016-03-AA and are a more advanced solution than B channels, which are retained for legacy models. By default, BB channels are superior to B channels as they: (a) adjust the entrance and exit losses every timestep according the approach and departure velocities (in the same manner as for other structures such as culverts); (b) automatically simulates pressure flow conditions. The only loss coefficients required to be specified for BB channels are those due to any piers, and the bridge deck when it is submerged and not under pressure flow.

Note: For TUFLOW Builds prior to 2020-01-AC, if the BB bridge is linked directly to a 2D domain (typically via a SX link), there is no adjustment of entrance / exit losses on the sides connected to 2D (adjustment of losses according to approach/departure velocities is the default from 1D to 1D to 1D. This capability was introduced for 2D to 1D to 2D, losses can be automatically adjusted based on the approach/departure 2D velocities across the SX connections by setting "???????????????" in Build 2020-01-AC onwards. In the case of 2D connections, refer to the links from the TUFLOW Library below for a discussion on the intricacies and challenges of taking into account contraction and expansion losses for 1D structures connected directly to 2D domains. For B bridges the default is not to adjust losses (please refer to the manual for more information).

https://www.tuflow.com/Download/Presentations/2012/2012%20Aust%20Workshops%20-%20TUFLOW%20Modelling%20Bends,%20Structures%20and%20Obstructions.pdf
https://www.tuflow.com/Download/Publications/Modelling%20of%20Bends%20and%20Hydraulic%20Structures%20in%20a%202D%20Scheme,%20Syme,%202001.pdf

As a typical rule-of-thumb, if the channel upstream &/or downstream of the bridge is modelled in 1D then the bridge should also be modelled in 1D. Ideally any change in the channel from ESTRY 1D to 2D or vice-versa should also occur at a structure (i.e. bridge, culvert, etc) to facilitate the transition in solution schemes. The images below displays a typical preferred setup, however as is the case with hydraulic modeling your particular model situation may be different and therefore not always conform to these ideals. 

<div><ul>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|300px|1D channel to 1D bridge to 1D channel]] </li>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_2d_Channel.JPG|thumb|none|306px|1D channel to 1D bridge to 2D channel]] </li>
<li style="display: inline-block;"> [[File:2d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|307px|2D channel to 1D bridge to 1D channel]] </li>
</ul></div>

'''Example of a bridge that could be modelled in 1D'''
 
[[File:Photo 04-12-2014 13 16 25.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 

=Loss Theory=

==Pier Losses==
Peir loss coefficients are treated as a direct energy (form) loss and can be derived from information in publications such as ''Hydraulics of Bridge Waterways'' ([http://www.ciccp.es/ImgWeb/Castilla%20y%20Leon/Documentaci%C3%B3n%20T%C3%A9cnica/Hydraulics%20of%20Bridge%20Waterways%20(1978).pdf FHA, 1978] or [https://austroads.com.au/publications/bridges/agbt08 AUSTROADS, 2019]).

Energy loss estimates from bridge piers or other obstructions, vertical or horizontal, that do not cause upstream controlled flow regimes like pressure flow, are dependent on the ratio of the obstruction's area perpendicular to the flow direction to the gross flow area of the bridge opening, the shape of the piers or obstruction, and the angularity of the piers/obstruction to the flow direction. For example, using FHA (1978) the approach is:
<ol>
<li>Calculate the ratio of the water area occupied by piers to the gross water area of the constriction (both based on the normal water surface) and the angularity of the piers. These inputs are used to calculate "J" in the FHA documentation.</li>
<li>Use the FHA (1978) ''Incremental Backwater Coefficient for Piers'' data to calculate Kp. This is the value that will be entered into the bridge's LC (loss vs height) table as the energy or form loss coefficient. For piers or obstructions that are non-uniform in dimensions or shape the LC table can be used to vary the losses with height accordingly noting that losses will need to be proportioned with depth to reflect the combined effect of the different obstruction shapes/dimensions. 
[[File:FHA_Kp_arrow.PNG|400px]]
</li>
 

==Deck Losses and Pressure Flow==
For the legacy B channels, the deck loss coefficient was fixed at a value of 1.5625, which is derived from the discharge coefficient in Hydraulics of Bridge Waterways of 0.8 (1.56 = 1/0.8^2) to approximate pressure flow conditions. Whilst this is reasonable when the bridge deck experiences pressure flow, it will over-estimate the losses once the bridge deck starts to drown out and flow returns fully to downstream controlled. Further details on how the value of 1.56 was derived can be found [http://www.tuflow.com/forum/index.php?/topic/1419-1d-loss-coefficients-for-bridge-deck-surcharging/#comment-3673 here].
 
Due to the above limitation of B channels, BB channels were developed to automatically switch into and out of pressure flow conditions. For pressure flow, a default discharge coefficient of 0.8 is used which the user can modify using the 1d_nwk HConF_or_WC attribute. Once water commences to surcharge the bridge deck, TUFLOW tests for pressure flow or drowned flow every timestep by choosing the flow regime that gives the lower flow. For drowned bridge flow the 1d_nwk WConF_or_WEx attribute (default = 0.5) can be used to set the energy loss due to the bridge deck/rails if no LC (energy loss versus height) table is specified. When pressure flow occurs a flow regime of "P" is reported in the _TSF layer. For more information on theory and options for B and BB bridges see Section 5.7.2 in the TUFLOW Manual.
*''under construction''
 

=Irregular shaped bridges=
In the UK arch shaped bridges can often be seen on waterways, whereas in Australia these types of structures are quite uncommon. Modelling an irregular shaped bridge utilises the hydraulic properties elevation-width (CS/HW) type cross section and an irregular type culvert. 

;Methodology
<ul>
1. Create a 1d_tab HW (height vs width) .csv file for each standard shape (ie. set up a database of the irregular shapes). For the height value you can start at a value of zero so that height becomes depth (this might making the .csv files easier). As the height increases the width changes to reflect the particular irregular shape you are modeling. In the example below, the width at the top of the arch (2.1m) is set to a small value of 0.001m as opposed to zero as the HW becomes NA past the top of the irregular shape. 

[[File:HW_arch_example.JPG|border|900px]] 
 
GIS example set up: 
[[File:Irregular_culvert_attribute_details.JPG|border|500px]]
 

2. Any number of 1d_tab lines can reference the same .csv file, ie. you don't need to have a unique .csv file for every 1d_tab line. 

[[File:Arch HW attributes.JPG|border|300px]] 

3. One option is to copy and paste the 1d_tab lines across each pipe (if you use a two vertex 1d_tab line there is no requirement that the 1d_tab line is snapped to the 1d_nwk pipe line - they just need to intersect). Each line will need to reference the relevant standard irregular shape HW .csv file (this could be automated using SQL Select if you have an attribute on the pipe to indicate which irregular shape it is). 
4. The inverts of the pipes should raise or lower the standard irregular shape cross-section to the appropriate height.
</ul>
 
;Real world examples
[[File:Irregular_culvert_1.jpg|border|300px]]
[[File:Irregular_culvert_2.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 
;Useful Forum Posts
[http://www.tuflow.com/forum/index.php?/topic/608-setting-up-an-irregular-1d-culvert/#comment-1429 Setting up an irregular 1D culvert].

=Typical check files used=
The table below highlights some of the commonly used check files when reviewing 1D bridges. The full list of TUFLOW check files can be found [[TUFLOW_Check_Files | here]].
{| align="left" class="wikitable" width="20%"

! style="background-color:#005581; font-weight:bold; color:white;"| Filename prefix / suffix

|-
| [[Check_Files_1d_bc_tables | _1d_bc_tables_check.csv]]
|-
| [[Check_Files_1d_ta_tables | _1d_ta_tables_check.csv]]
|-
| [[Check_Files_1d_hydroprop | _hydroprop_check.mif _hydroprop_check_L.shp]]
|-
| [[Check_Files_1d_inverts | _inverts_check.mif _inverts_check_P.shp]]
|-
| [[Check_Files_1d_IWL | _iwl_check.mif _iwl_check_P.shp]]
|-
| [[Check_Files_1d_nwk_C | _nwk_C_check.mif _nwk_C_check_L.shp]]
|-
| [[Check_Files_1d_nwk_N | _nwk_N_check.mif _nwk_N_check_P.shp]]
|-
| [[Check_Files_1d_xsl | _xsl_check.mif _xsl_check_L.shp]]
|}

 
 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20bridges%20help support@tuflow.com]
 
Back to [[TUFLOW_1D_Hydraulic_Structures | 1D Hydraulic Structures]]

1D Bridges

2020-07-20T01:43:22Z

Bill Syme:

Page Under Construction
 
 
 
=Introduction=
The following section looks at bridges using the 1D component of TUFLOW. Reference should also be made to the section on 1D bridges in the TUFLOW Manual. For information on bridges in the 2D domain please see the following section on [[TUFLOW_2D_Hydraulic_Structures | 2D hydraulic Structures]] and [[Tutorial_Module06#Bridge_Modelling_Option_3:_2D_Layered_Flow_Constriction | Module 6]]. 
1D Bridge channels do not require length, Manning's n, divergence or bed slope (so they are effectively zero-length channels in terms of conveyance) and rely on a reasonable estimate of energy losses associated with re-expansion of water after the vena-contracta (often referred to as entrance losses), expansion of water downstream (exit losses), pier losses, bridge deck and guard rail losses. Other factors include accounting for occurrence of bridge deck pressure flow and the effects of bridge skew and multiple bridges (shielding effects of an upstream bridge on a downstream bridge). 

Care must be taken when choosing the approach to modelling the bridge and setting appropriate loss values.

TUFLOW offers two 1D bridge channels, B and BB. BB channels were introduced for Build 2016-03-AA and are a more advanced solution than B channels, which are retained for legacy models. By default, BB channels are superior to B channels as they: (a) adjust the entrance and exit losses every timestep according the approach and departure velocities (in the same manner as for other structures such as culverts); (b) automatically simulates pressure flow conditions. The only loss coefficients required to be specified for BB channels are those due to any piers, and the bridge deck when it is submerged and not under pressure flow.

Note: For TUFLOW Builds prior to 2020-01-AC, if the BB bridge is linked directly to a 2D domain (typically via a SX link), there is no adjustment of entrance / exit losses on the sides connected to 2D (adjustment of losses according to approach/departure velocities is the default from 1D to 1D to 1D. This capability was introduced for 2D to 1D to 2D, losses can be automatically adjusted based on the approach/departure 2D velocities across the SX connections by setting "???????????????" in Build 2020-01-AC onwards. In the case of 2D connections, refer to the links from the TUFLOW Library below for a discussion on the intricacies and challenges of taking into account contraction and expansion losses for 1D structures connected directly to 2D domains. For B bridges the default is not to adjust losses (please refer to the manual for more information).

https://www.tuflow.com/Download/Presentations/2012/2012%20Aust%20Workshops%20-%20TUFLOW%20Modelling%20Bends,%20Structures%20and%20Obstructions.pdf
https://www.tuflow.com/Download/Publications/Modelling%20of%20Bends%20and%20Hydraulic%20Structures%20in%20a%202D%20Scheme,%20Syme,%202001.pdf

As a typical rule-of-thumb, if the channel upstream &/or downstream of the bridge is modelled in 1D then the bridge should also be modelled in 1D. Ideally any change in the channel from ESTRY 1D to 2D or vice-versa should also occur at a structure (i.e. bridge, culvert, etc) to facilitate the transition in solution schemes. The images below displays a typical preferred setup, however as is the case with hydraulic modeling your particular model situation may be different and therefore not always conform to these ideals. 

<div><ul>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|300px|1D channel to 1D bridge to 1D channel]] </li>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_2d_Channel.JPG|thumb|none|306px|1D channel to 1D bridge to 2D channel]] </li>
<li style="display: inline-block;"> [[File:2d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|307px|2D channel to 1D bridge to 1D channel]] </li>
</ul></div>

'''Example of a bridge that could be modelled in 1D'''
 
[[File:Photo 04-12-2014 13 16 25.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 

=Loss Theory=

==Pier Losses==
Peir loss coefficients are treated as a direct energy (form) loss and can be derived from information in publications such as ''Hydraulics of Bridge Waterways'' ([http://www.ciccp.es/ImgWeb/Castilla%20y%20Leon/Documentaci%C3%B3n%20T%C3%A9cnica/Hydraulics%20of%20Bridge%20Waterways%20(1978).pdf FHA, 1978] or [https://austroads.com.au/publications/bridges/agbt08 AUSTROADS, 2019]).

Energy loss estimates from bridge piers or other obstructions, vertical or horizontal, that do not cause upstream controlled flow regimes like pressure flow, are dependent on the ratio of the obstruction's area relative to the gross area of the bridge opening, the type of piers (or piling in the case of pile bents) and the angularity of the piers with the direction of flood flow. The FHA (1978) guidance advises what form loss coefficient should be adopted based on these input parameters.
<ol>
<li>Calculate the ratio of the water area occupied by piers to the gross water area of the constriction (both based on the normal water surface) and the angularity of the piers. These inputs are used to calculate "J" in the FHA documentation.</li>
<li>Use the FHA (1978) ''Incremental Backwater Coefficient for Piers'' data to calculate Kp. This is the value which will be entered into TUFLOW as the form loss coefficient. 
[[File:FHA_Kp_arrow.PNG|400px]]
</li>
 

==Deck Losses and Pressure Flow==
For the legacy B channels, the deck loss coefficient was fixed at a value of 1.5625, which is derived from the discharge coefficient in Hydraulics of Bridge Waterways of 0.8 (1.56 = 1/0.8^2) to approximate pressure flow conditions. Whilst this is reasonable when the bridge deck experiences pressure flow, it will over-estimate the losses once the bridge deck starts to drown out and flow returns fully to downstream controlled. Further details on how the value of 1.56 was derived can be found [http://www.tuflow.com/forum/index.php?/topic/1419-1d-loss-coefficients-for-bridge-deck-surcharging/#comment-3673 here].
 
Due to the above limitation of B channels, BB channels were developed to automatically switch into and out of pressure flow conditions. For pressure flow, a default discharge coefficient of 0.8 is used which the user can modify using the 1d_nwk HConF_or_WC attribute. Once water commences to surcharge the bridge deck, TUFLOW tests for pressure flow or drowned flow every timestep by choosing the flow regime that gives the lower flow. For drowned bridge flow the 1d_nwk WConF_or_WEx attribute (default = 0.5) can be used to set the energy loss due to the bridge deck/rails if no LC (energy loss versus height) table is specified. When pressure flow occurs a flow regime of "P" is reported in the _TSF layer. For more information on theory and options for B and BB bridges see Section 5.7.2 in the TUFLOW Manual.
*''under construction''
 

=Irregular shaped bridges=
In the UK arch shaped bridges can often be seen on waterways, whereas in Australia these types of structures are quite uncommon. Modelling an irregular shaped bridge utilises the hydraulic properties elevation-width (CS/HW) type cross section and an irregular type culvert. 

;Methodology
<ul>
1. Create a 1d_tab HW (height vs width) .csv file for each standard shape (ie. set up a database of the irregular shapes). For the height value you can start at a value of zero so that height becomes depth (this might making the .csv files easier). As the height increases the width changes to reflect the particular irregular shape you are modeling. In the example below, the width at the top of the arch (2.1m) is set to a small value of 0.001m as opposed to zero as the HW becomes NA past the top of the irregular shape. 

[[File:HW_arch_example.JPG|border|900px]] 
 
GIS example set up: 
[[File:Irregular_culvert_attribute_details.JPG|border|500px]]
 

2. Any number of 1d_tab lines can reference the same .csv file, ie. you don't need to have a unique .csv file for every 1d_tab line. 

[[File:Arch HW attributes.JPG|border|300px]] 

3. One option is to copy and paste the 1d_tab lines across each pipe (if you use a two vertex 1d_tab line there is no requirement that the 1d_tab line is snapped to the 1d_nwk pipe line - they just need to intersect). Each line will need to reference the relevant standard irregular shape HW .csv file (this could be automated using SQL Select if you have an attribute on the pipe to indicate which irregular shape it is). 
4. The inverts of the pipes should raise or lower the standard irregular shape cross-section to the appropriate height.
</ul>
 
;Real world examples
[[File:Irregular_culvert_1.jpg|border|300px]]
[[File:Irregular_culvert_2.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 
;Useful Forum Posts
[http://www.tuflow.com/forum/index.php?/topic/608-setting-up-an-irregular-1d-culvert/#comment-1429 Setting up an irregular 1D culvert].

=Typical check files used=
The table below highlights some of the commonly used check files when reviewing 1D bridges. The full list of TUFLOW check files can be found [[TUFLOW_Check_Files | here]].
{| align="left" class="wikitable" width="20%"

! style="background-color:#005581; font-weight:bold; color:white;"| Filename prefix / suffix

|-
| [[Check_Files_1d_bc_tables | _1d_bc_tables_check.csv]]
|-
| [[Check_Files_1d_ta_tables | _1d_ta_tables_check.csv]]
|-
| [[Check_Files_1d_hydroprop | _hydroprop_check.mif _hydroprop_check_L.shp]]
|-
| [[Check_Files_1d_inverts | _inverts_check.mif _inverts_check_P.shp]]
|-
| [[Check_Files_1d_IWL | _iwl_check.mif _iwl_check_P.shp]]
|-
| [[Check_Files_1d_nwk_C | _nwk_C_check.mif _nwk_C_check_L.shp]]
|-
| [[Check_Files_1d_nwk_N | _nwk_N_check.mif _nwk_N_check_P.shp]]
|-
| [[Check_Files_1d_xsl | _xsl_check.mif _xsl_check_L.shp]]
|}

 
 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20bridges%20help support@tuflow.com]
 
Back to [[TUFLOW_1D_Hydraulic_Structures | 1D Hydraulic Structures]]

1D Bridges

2020-07-14T01:44:52Z

Bill Syme:

Page Under Construction
 
 
 
=Introduction=
The following section looks at bridges using the 1D component of TUFLOW. Reference should also be made to the section on 1D bridges in the TUFLOW Manual. For information on bridges in the 2D domain please see the following section on [[TUFLOW_2D_Hydraulic_Structures | 2D hydraulic Structures]] and [[Tutorial_Module06#Bridge_Modelling_Option_3:_2D_Layered_Flow_Constriction | Module 6]]. 
1D Bridge channels do not require length, Manning's n, divergence or bed slope (so they are effectively zero-length channels in terms of conveyance) and rely on a reasonable estimate of energy losses associated with re-expansion of water after the vena-contracta (often referred to as entrance losses), expansion of water downstream (exit losses), pier losses, bridge deck and guard rail losses. Other factors include accounting for occurrence of bridge deck pressure flow and the effects of bridge skew and multiple bridges (shielding effects of an upstream bridge on a downstream bridge). 

Care must be taken when choosing the approach to modelling the bridge and setting appropriate loss values.

TUFLOW offers two 1D bridge channels, B and BB. BB channels were introduced for Build 2016-03-AA and are a more advanced solution than B channels, which are retained for legacy models. By default, BB channels are superior to B channels as they: (a) adjust the entrance and exit losses every timestep according the approach and departure velocities (in the same manner as for other structures such as culverts); (b) automatically simulates pressure flow conditions. The only loss coefficients required to be specified for BB channels are those due to any piers, and the bridge deck when it is submerged and not under pressure flow.

Note: For TUFLOW Builds prior to 2020-01-AC, if the BB bridge is linked directly to a 2D domain (typically via a SX link), there is no adjustment of entrance / exit losses on the sides connected to 2D (adjustment of losses according to approach/departure velocities is the default from 1D to 1D to 1D. This capability was introduced for 2D to 1D to 2D, losses can be automatically adjusted based on the approach/departure 2D velocities across the SX connections by setting "???????????????" in Build 2020-01-AC onwards. In the case of 2D connections, refer to the links from the TUFLOW Library below for a discussion on the intricacies and challenges of taking into account contraction and expansion losses for 1D structures connected directly to 2D domains. For B bridges the default is not to adjust losses (please refer to the manual for more information).

https://www.tuflow.com/Download/Presentations/2012/2012%20Aust%20Workshops%20-%20TUFLOW%20Modelling%20Bends,%20Structures%20and%20Obstructions.pdf
https://www.tuflow.com/Download/Publications/Modelling%20of%20Bends%20and%20Hydraulic%20Structures%20in%20a%202D%20Scheme,%20Syme,%202001.pdf

As a typical rule-of-thumb, if the channel upstream &/or downstream of the bridge is modelled in 1D then the bridge should also be modelled in 1D. Ideally any change in the channel from ESTRY 1D to 2D or vice-versa should also occur at a structure (i.e. bridge, culvert, etc) to facilitate the transition in solution schemes. The images below displays a typical preferred setup, however as is the case with hydraulic modeling your particular model situation may be different and therefore not always conform to these ideals. 

<div><ul>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|300px|1D channel to 1D bridge to 1D channel]] </li>
<li style="display: inline-block;"> [[File:1d_Channel_to_1d_Bridge_to_2d_Channel.JPG|thumb|none|306px|1D channel to 1D bridge to 2D channel]] </li>
<li style="display: inline-block;"> [[File:2d_Channel_to_1d_Bridge_to_1d_Channel.JPG|thumb|none|307px|2D channel to 1D bridge to 1D channel]] </li>
</ul></div>

'''Example of a bridge that could be modeled in 1D'''
 
[[File:Photo 04-12-2014 13 16 25.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 

=Loss Theory=

==Pier Losses==
*''under construction''
 

==Deck Losses and Pressure Flow==
For the legacy B channels, the deck loss coefficient was fixed at a value of 1.5625, which is derived from the discharge coefficient in Hydraulics of Bridge Waterways of 0.8 (1.56 = 1/0.8^2) to approximate pressure flow conditions. Whilst this is reasonable when the bridge deck experiences pressure flow, it will over-estimate the losses once the bridge deck starts to drown out and flow returns fully to downstream controlled. Further details on how the value of 1.56 was derived can be found [http://www.tuflow.com/forum/index.php?/topic/1419-1d-loss-coefficients-for-bridge-deck-surcharging/#comment-3673 here].
 
Due to the above limitation of B channels, BB channels were developed to automatically switch into and out of pressure flow conditions. For pressure flow, a default discharge coefficient of 0.8 is used which the user can modify using the 1d_nwk HConF_or_WC attribute. Once water commences to surcharge the bridge deck, TUFLOW tests for pressure flow or drowned flow every timestep by choosing the flow regime that gives the lower flow. For drowned bridge flow the 1d_nwk WConF_or_WEx attribute (default = 0.5) can be used to set the energy loss due to the bridge deck/rails if no LC (energy loss versus height) table is specified. When pressure flow occurs a flow regime of "P" is reported in the _TSF layer. For more information on theory and options for B and BB bridges see Section 5.7.2 in the TUFLOW Manual.
*''under construction''
 

=Irregular shaped bridges=
In the UK arch shaped bridges can often be seen on waterways, whereas in Australia these types of structures are quite uncommon. Modelling an irregular shaped bridge utilises the hydraulic properties elevation-width (CS/HW) type cross section and an irregular type culvert. 

;Methodology
<ul>
1. Create a 1d_tab HW (height vs width) .csv file for each standard shape (ie. set up a database of the irregular shapes). For the height value you can start at a value of zero so that height becomes depth (this might making the .csv files easier). As the height increases the width changes to reflect the particular irregular shape you are modeling. In the example below, the width at the top of the arch (2.1m) is set to a small value of 0.001m as opposed to zero as the HW becomes NA past the top of the irregular shape. 

[[File:HW_arch_example.JPG|border|900px]] 
 
GIS example set up: 
[[File:Irregular_culvert_attribute_details.JPG|border|500px]]
 

2. Any number of 1d_tab lines can reference the same .csv file, ie. you don't need to have a unique .csv file for every 1d_tab line. 

[[File:Arch HW attributes.JPG|border|300px]] 

3. One option is to copy and paste the 1d_tab lines across each pipe (if you use a two vertex 1d_tab line there is no requirement that the 1d_tab line is snapped to the 1d_nwk pipe line - they just need to intersect). Each line will need to reference the relevant standard irregular shape HW .csv file (this could be automated using SQL Select if you have an attribute on the pipe to indicate which irregular shape it is). 
4. The inverts of the pipes should raise or lower the standard irregular shape cross-section to the appropriate height.
</ul>
 
;Real world examples
[[File:Irregular_culvert_1.jpg|border|300px]]
[[File:Irregular_culvert_2.jpg|border|400px]]
 
London, UK (pht: Rohan King)
 
;Useful Forum Posts
[http://www.tuflow.com/forum/index.php?/topic/608-setting-up-an-irregular-1d-culvert/#comment-1429 Setting up an irregular 1D culvert].

=Typical check files used=
The table below highlights some of the commonly used check files when reviewing 1D bridges. The full list of TUFLOW check files can be found [[TUFLOW_Check_Files | here]].
{| align="left" class="wikitable" width="20%"

! style="background-color:#005581; font-weight:bold; color:white;"| Filename prefix / suffix

|-
| [[Check_Files_1d_bc_tables | _1d_bc_tables_check.csv]]
|-
| [[Check_Files_1d_ta_tables | _1d_ta_tables_check.csv]]
|-
| [[Check_Files_1d_hydroprop | _hydroprop_check.mif _hydroprop_check_L.shp]]
|-
| [[Check_Files_1d_inverts | _inverts_check.mif _inverts_check_P.shp]]
|-
| [[Check_Files_1d_IWL | _iwl_check.mif _iwl_check_P.shp]]
|-
| [[Check_Files_1d_nwk_C | _nwk_C_check.mif _nwk_C_check_L.shp]]
|-
| [[Check_Files_1d_nwk_N | _nwk_N_check.mif _nwk_N_check_P.shp]]
|-
| [[Check_Files_1d_xsl | _xsl_check.mif _xsl_check_L.shp]]
|}

 
 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20bridges%20help support@tuflow.com]
 
Back to [[TUFLOW_1D_Hydraulic_Structures | 1D Hydraulic Structures]]

1D Bridges

2020-06-17T01:20:28Z

Bill Syme:

2014-06-02T00:10:42Z

Bill Syme:

The 2xxx TUFLOW messages refer to issues that occur neither in the 2D model. Click on number to follow link to TUFLOW message description, grey numbers are reserved and do not yet have messages assigned, and red numbers have been allocated to new messages.

See also:
* [[0xxx TUFLOW Messages]]
* [[1xxx TUFLOW Messages]]
* [[9xxx TUFLOW Messages]]

{| Border ="1" cellpadding="8" style="text-align:center"
|2000 || [[TUFLOW Message 2001|2001 ]] || [[TUFLOW Message 2002|2002 ]] || [[TUFLOW Message 2003|2003 ]] || [[TUFLOW Message 2004|2004 ]] || [[TUFLOW Message 2005|2005 ]] || [[TUFLOW Message 2006|2006 ]] || [[TUFLOW Message 2007|2007 ]] || [[TUFLOW Message 2008|2008 ]] || [[TUFLOW Message 2009|2009 ]] || [[TUFLOW Message 2010|2010 ]] || [[TUFLOW Message 2011|2011 ]] || [[TUFLOW Message 2012|2012 ]] || [[TUFLOW Message 2013|2013 ]] || [[TUFLOW Message 2014|2014 ]] || [[TUFLOW Message 2015|2015 ]] || [[TUFLOW Message 2016|2016 ]] || [[TUFLOW Message 2017|2017 ]] || [[TUFLOW Message 2018|2018 ]] || [[TUFLOW Message 2019|2019 ]]
|-
|[[TUFLOW Message 2020|2020 ]] || [[TUFLOW Message 2021|2021 ]] || [[TUFLOW Message 2022|2022 ]] || [[TUFLOW Message 2023|2023 ]] || [[TUFLOW Message 2024|2024 ]] || [[TUFLOW Message 2025|2025 ]] || [[TUFLOW Message 2026|2026 ]] || [[TUFLOW Message 2027|2027 ]] || [[TUFLOW Message 2028|2028 ]] || [[TUFLOW Message 2029|2029 ]] || [[TUFLOW Message 2030|2030 ]] || [[TUFLOW Message 2031|2031 ]] || [[TUFLOW Message 2032|2032 ]] || [[TUFLOW Message 2033|2033 ]] || [[TUFLOW Message 2034|2034 ]] || [[TUFLOW Message 2035|2035 ]] || [[TUFLOW Message 2036|2036 ]] || [[TUFLOW Message 2037|2037 ]] || [[TUFLOW Message 2038|2038 ]] || [[TUFLOW Message 2039|2039 ]]
|-
|[[TUFLOW Message 2040|2040 ]] || [[TUFLOW Message 2041|2041 ]] || [[TUFLOW Message 2042|2042 ]] || [[TUFLOW Message 2043|2043 ]] || [[TUFLOW Message 2044|2044 ]] || [[TUFLOW Message 2045|2045 ]] || [[TUFLOW Message 2046|2046 ]] || [[TUFLOW Message 2047|2047 ]] || [[TUFLOW Message 2048|2048 ]] || [[TUFLOW Message 2049|2049 ]] || [[TUFLOW Message 2050|2050 ]] || [[TUFLOW Message 2051|2051 ]] || [[TUFLOW Message 2052|2052 ]] || [[TUFLOW Message 2053|2053 ]] || [[TUFLOW Message 2054|2054 ]] || [[TUFLOW Message 2055|2055 ]] || [[TUFLOW Message 2056|2056 ]] || [[TUFLOW Message 2057|2057 ]] || [[TUFLOW Message 2058|2058 ]] || [[TUFLOW Message 2059|2059 ]]
|-
|[[TUFLOW Message 2060|2060 ]] || [[TUFLOW Message 2061|2061 ]] || [[TUFLOW Message 2062|2062 ]] || [[TUFLOW Message 2063|2063 ]] || [[TUFLOW Message 2064|2064 ]] || [[TUFLOW Message 2065|2065 ]] || [[TUFLOW Message 2066|2066 ]] || [[TUFLOW Message 2067|2067 ]] || [[TUFLOW Message 2068|2068 ]] || [[TUFLOW Message 2069|2069 ]] || [[TUFLOW Message 2070|2070 ]] || [[TUFLOW Message 2071|2071 ]] || [[TUFLOW Message 2072|2072 ]] || [[TUFLOW Message 2073|2073 ]] || [[TUFLOW Message 2074|2074 ]] || [[TUFLOW Message 2075|2075 ]] || [[TUFLOW Message 2076|2076 ]] || [[TUFLOW Message 2077|2077 ]] || [[TUFLOW Message 2078|2078 ]] || [[TUFLOW Message 2079|2079 ]]
|-
|[[TUFLOW Message 2080|2080 ]] || [[TUFLOW Message 2081|2081 ]] || [[TUFLOW Message 2082|2082 ]] || [[TUFLOW Message 2083|2083 ]] || [[TUFLOW Message 2084|2084 ]] || [[TUFLOW Message 2085|2085 ]] || [[TUFLOW Message 2086|2086 ]] || [[TUFLOW Message 2087|2087 ]] || [[TUFLOW Message 2088|2088 ]] || [[TUFLOW Message 2089|2089 ]] || [[TUFLOW Message 2090|2090 ]] || [[TUFLOW Message 2091|2091 ]] || [[TUFLOW Message 2092|2092 ]] || [[TUFLOW Message 2093|2093 ]] || [[TUFLOW Message 2094|2094 ]] || [[TUFLOW Message 2095|2095 ]] || [[TUFLOW Message 2096|2096 ]] || [[TUFLOW Message 2097|2097 ]] || [[TUFLOW Message 2098|2098 ]] || [[TUFLOW Message 2099|2099 ]]
|-
|[[TUFLOW Message 2100|2100 ]] || [[TUFLOW Message 2101|2101 ]] || [[TUFLOW Message 2102|2102 ]] || [[TUFLOW Message 2103|2103 ]] || [[TUFLOW Message 2104|2104 ]] || [[TUFLOW Message 2105|2105 ]] || [[TUFLOW Message 2106|2106 ]] || [[TUFLOW Message 2107|2107 ]] || [[TUFLOW Message 2108|2108 ]] || [[TUFLOW Message 2109|2109 ]] || [[TUFLOW Message 2110|2110 ]] || [[TUFLOW Message 2111|2111 ]] || [[TUFLOW Message 2112|2112 ]] || [[TUFLOW Message 2113|2113 ]] || [[TUFLOW Message 2114|2114 ]] || [[TUFLOW Message 2115|2115 ]] || [[TUFLOW Message 2116|2116 ]] || [[TUFLOW Message 2117|2117 ]] || [[TUFLOW Message 2118|2118 ]] || [[TUFLOW Message 2119|2119 ]]
|-
|[[TUFLOW Message 2120|2120 ]] || [[TUFLOW Message 2121|2121 ]] || [[TUFLOW Message 2122|2122 ]] || [[TUFLOW Message 2123|2123 ]] || [[TUFLOW Message 2124|2124 ]] || [[TUFLOW Message 2125|2125 ]] || [[TUFLOW Message 2126|2126 ]] || [[TUFLOW Message 2127|2127 ]] || [[TUFLOW Message 2128|2128 ]] || [[TUFLOW Message 2129|2129 ]] || [[TUFLOW Message 2130|2130 ]] || [[TUFLOW Message 2131|2131 ]] || [[TUFLOW Message 2132|2132 ]] || [[TUFLOW Message 2133|2133 ]] || [[TUFLOW Message 2134|2134 ]] || [[TUFLOW Message 2135|2135 ]] || [[TUFLOW Message 2136|2136 ]] || [[TUFLOW Message 2137|2137 ]] || [[TUFLOW Message 2138|2138 ]] || [[TUFLOW Message 2139|2139 ]]
|-
|[[TUFLOW Message 2140|2140 ]] || [[TUFLOW Message 2141|2141 ]] || [[TUFLOW Message 2142|2142 ]] || [[TUFLOW Message 2143|2143 ]] || [[TUFLOW Message 2144|2144 ]] || [[TUFLOW Message 2145|2145 ]] || [[TUFLOW Message 2146|2146 ]] || [[TUFLOW Message 2147|2147 ]] || [[TUFLOW Message 2148|2148 ]] || [[TUFLOW Message 2149|2149 ]] || [[TUFLOW Message 2150|2150 ]] || [[TUFLOW Message 2151|2151 ]] || [[TUFLOW Message 2152|2152 ]] || [[TUFLOW Message 2153|2153 ]] || [[TUFLOW Message 2154|2154 ]] || [[TUFLOW Message 2155|2155 ]] || [[TUFLOW Message 2156|2156 ]] || [[TUFLOW Message 2157|2157 ]] || [[TUFLOW Message 2158|2158 ]] || [[TUFLOW Message 2159|2159 ]]
|-
|[[TUFLOW Message 2160|2160 ]] || [[TUFLOW Message 2161|2161 ]] || [[TUFLOW Message 2162|2162 ]] || [[TUFLOW Message 2163|2163 ]] || [[TUFLOW Message 2164|2164 ]] || [[TUFLOW Message 2165|2165 ]] || [[TUFLOW Message 2166|2166 ]] || [[TUFLOW Message 2167|2167 ]] || [[TUFLOW Message 2168|2168 ]] || [[TUFLOW Message 2169|2169 ]] || [[TUFLOW Message 2170|2170 ]] || [[TUFLOW Message 2171|2171 ]] || [[TUFLOW Message 2172|2172 ]] || [[TUFLOW Message 2173|2173 ]] || [[TUFLOW Message 2174|2174 ]] || [[TUFLOW Message 2175|2175 ]] || [[TUFLOW Message 2176|2176 ]] || [[TUFLOW Message 2177|2177 ]] || [[TUFLOW Message 2178|2178 ]] || [[TUFLOW Message 2179|2179 ]]
|-
|[[TUFLOW Message 2180|2180 ]] || [[TUFLOW Message 2181|2181 ]] || [[TUFLOW Message 2182|2182 ]] || [[TUFLOW Message 2183|2183 ]] || [[TUFLOW Message 2184|2184 ]] || [[TUFLOW Message 2185|2185 ]] || [[TUFLOW Message 2186|2186 ]] || [[TUFLOW Message 2187|2187 ]] || [[TUFLOW Message 2188|2188 ]] || [[TUFLOW Message 2189|2189 ]] || [[TUFLOW Message 2190|2190 ]] || [[TUFLOW Message 2191|2191 ]] || [[TUFLOW Message 2192|2192 ]] || [[TUFLOW Message 2193|2193 ]] || [[TUFLOW Message 2194|2194 ]] || [[TUFLOW Message 2195|2195 ]] || [[TUFLOW Message 2196|2196 ]] || [[TUFLOW Message 2197|2197 ]] || [[TUFLOW Message 2198|2198 ]] || [[TUFLOW Message 2199|2199 ]]
|-
|[[TUFLOW Message 2200|2200 ]] || [[TUFLOW Message 2201|2201 ]] || [[TUFLOW Message 2202|2202 ]] || [[TUFLOW Message 2203|2203 ]] || 2204 || [[TUFLOW Message 2205|2205 ]] || [[TUFLOW Message 2206|2206 ]] || 2207 || 2208 || 2209 || [[TUFLOW Message 2210|2210 ]] || [[TUFLOW Message 2211|2211 ]] || [[TUFLOW Message 2212|2212 ]] || [[TUFLOW Message 2213|2213 ]] || [[TUFLOW Message 2214|2214 ]] || [[TUFLOW Message 2215|2215 ]] || [[TUFLOW Message 2216|2216 ]] || [[TUFLOW Message 2217|2217 ]] || [[TUFLOW Message 2218|2218 ]] || [[TUFLOW Message 2219|2219 ]]
|-
|[[TUFLOW Message 2220|2220 ]] || [[TUFLOW Message 2221|2221 ]] || [[TUFLOW Message 2222|2222 ]] || [[TUFLOW Message 2223|2223 ]] || [[TUFLOW Message 2224|2224 ]] || [[TUFLOW Message 2225|2225 ]] || [[TUFLOW Message 2226|2226 ]] || [[TUFLOW Message 2227|2227 ]] || [[TUFLOW Message 2228|2228 ]] || [[TUFLOW Message 2229|2229 ]] || [[TUFLOW Message 2230|2230 ]] || [[TUFLOW Message 2231|2231 ]] || [[TUFLOW Message 2232|2232 ]] || [[TUFLOW Message 2233|2233 ]] || [[TUFLOW Message 2234|2234 ]] || [[TUFLOW Message 2235|2235 ]] || [[TUFLOW Message 2236|2236 ]] || [[TUFLOW Message 2237|2237 ]] || [[TUFLOW Message 2238|2238 ]] || 2239
|-
|2300 || 2301 || 2302 || 2303 || 2304 || 2305 || 2306 || 2307 || [[TUFLOW Message 2308|2308 ]] || [[TUFLOW Message 2309|2309 ]] || [[TUFLOW Message 2310|2310 ]] || [[TUFLOW Message 2311|2311 ]] || 2312 || [[TUFLOW Message 2313|2313 ]] || 2314 || 2315 || 2316 || 2317 || 2318 || 2319
|-
|2320 || [[TUFLOW Message 2321|2321 ]] || 2322 || 2323 || 2324 || 2325 || 2326 || 2327 || 2328 || 2329 || 2330 || 2331 || 2332 || 2333 || 2334 || 2335 || 2336 || 2337 || 2338 || 2339
|-
|2340 || 2341 || 2342 || 2343 || 2344 || 2345 || 2346 || 2347 || 2348 || 2349 || [[TUFLOW Message 2350|2350 ]] || [[TUFLOW Message 2351|2351 ]] || [[TUFLOW Message 2352|2352 ]] || [[TUFLOW Message 2353|2353 ]] || [[TUFLOW Message 2354|2354 ]] || [[TUFLOW Message 2355|2355 ]] || [[TUFLOW Message 2356|2356 ]] || [[TUFLOW Message 2357|2357 ]] || [[TUFLOW Message 2358|2358 ]] || [[TUFLOW Message 2359|2359 ]]
|-
|[[TUFLOW Message 2360|2360 ]] || [[TUFLOW Message 2361|2361 ]] || [[TUFLOW Message 2362|2362 ]] || 2363 || 2364 || [[TUFLOW Message 2365|2365 ]] || 2366 || 2367 || 2368 || 2369 || 2370 || [[TUFLOW Message 2371|2371 ]] || [[TUFLOW Message 2372|2372 ]] || [[TUFLOW Message 2373|2373 ]] || [[TUFLOW Message 2374|2374 ]] || [[TUFLOW Message 2375|2375 ]] || [[TUFLOW Message 2376|2376 ]] || [[TUFLOW Message 2377|2377 ]] || 2378 || 2379
|-
|2380 || [[TUFLOW Message 2381|2381 ]] || [[TUFLOW Message 2382|2382 ]] || [[TUFLOW Message 2383|2383 ]] || 2384 || [[TUFLOW Message 2385|2385 ]] || 2386 || 2387 || 2388 || [[TUFLOW Message 2389|2389 ]] || 2390 || 2391 || 2392 || 2393 || 2394 || 2395 || 2396 || 2397 || 2398 || 2399
|-
|2400 || [[TUFLOW Message 2401|2401 ]] || [[TUFLOW Message 2402|2402 ]] || [[TUFLOW Message 2403|2403 ]] || [[TUFLOW Message 2404|2404 ]] || [[TUFLOW Message 2405|2405 ]] || [[TUFLOW Message 2406|2406 ]] || [[TUFLOW Message 2407|2407 ]] || [[TUFLOW Message 2408|2408 ]] || 2409 || 2410 || [[TUFLOW Message 2411|2411 ]] || [[TUFLOW Message 2412|2412 ]] || [[TUFLOW Message 2413|2413 ]] || [[TUFLOW Message 2414|2414 ]] || [[TUFLOW Message 2415|2415 ]] || [[TUFLOW Message 2416|2416 ]] || 2417 || [[TUFLOW Message 2418|2418 ]] || [[TUFLOW Message 2419|2419 ]]
|-
|2420 || [[TUFLOW Message 2421|2421 ]] || [[TUFLOW Message 2422|2422 ]] || [[TUFLOW Message 2423|2423 ]] || [[TUFLOW Message 2424|2424 ]] || [[TUFLOW Message 2425|2425 ]] || [[TUFLOW Message 2426|2426 ]] || [[TUFLOW Message 2427|2427 ]] || [[TUFLOW Message 2428|2428 ]] || [[TUFLOW Message 2429|2429 ]] || [[TUFLOW Message 2430|2430 ]] || [[TUFLOW Message 2431|2431 ]] || [[TUFLOW Message 2432|2432 ]] || 2433 || 2434 || 2435 || 2436 || 2437 || 2438 || 2439
|-
|2440 || [[TUFLOW Message 2441|2441 ]] || 2442 || 2443 || 2444 || 2445 || 2446 || 2447 || 2448 || 2449 || [[TUFLOW Message 2450|2450 ]] || [[TUFLOW Message 2451|2451 ]] || 2452 || 2453 || 2454 || 2455 || 2456 || 2457 || 2458 || 2459
|-
|[[TUFLOW Message 2460|2460 ]] || 2461 || 2462 || 2463 || 2464 || 2465 || 2466 || 2467 || 2468 || 2469 || 2470 || 2471 || 2472 || 2473 || 2474 || 2475 || 2476 || 2477 || 2478 || 2479
|-
|2980 || 2981 || 2982 || 2983 || 2984 || 2985 || 2986 || 2987 || 2988 || 2989 || 2990 || [[TUFLOW Message 2991|2991 ]] || 2992 || 2993 || 2994 || 2995 || 2996 || 2997 || [[TUFLOW Message 2998|2998 ]] || [[TUFLOW Message 2999|2999 ]]
|-
|}

2xxx TUFLOW Messages

2014-06-01T23:54:10Z

Bill Syme:

The 2xxx TUFLOW messages refer to issues that occur neither in the 2D model. Click on number to follow link to TUFLOW message description, grey numbers are reserved and do not yet have messages assigned, and red numbers have been allocated to new messages.

See also:
* [[0xxx TUFLOW Messages]]
* [[1xxx TUFLOW Messages]]
* [[9xxx TUFLOW Messages]]

{| Border ="1" cellpadding="8" style="text-align:center"
|2000 || [[TUFLOW Message 2001|2001 ]] || [[TUFLOW Message 2002|2002 ]] || [[TUFLOW Message 2003|2003 ]] || [[TUFLOW Message 2004|2004 ]] || [[TUFLOW Message 2005|2005 ]] || [[TUFLOW Message 2006|2006 ]] || [[TUFLOW Message 2007|2007 ]] || [[TUFLOW Message 2008|2008 ]] || [[TUFLOW Message 2009|2009 ]] || [[TUFLOW Message 2010|2010 ]] || [[TUFLOW Message 2011|2011 ]] || [[TUFLOW Message 2012|2012 ]] || [[TUFLOW Message 2013|2013 ]] || [[TUFLOW Message 2014|2014 ]] || [[TUFLOW Message 2015|2015 ]] || [[TUFLOW Message 2016|2016 ]] || [[TUFLOW Message 2017|2017 ]] || [[TUFLOW Message 2018|2018 ]] || [[TUFLOW Message 2019|2019 ]]
|-
|[[TUFLOW Message 2020|2020 ]] || [[TUFLOW Message 2021|2021 ]] || [[TUFLOW Message 2022|2022 ]] || [[TUFLOW Message 2023|2023 ]] || [[TUFLOW Message 2024|2024 ]] || [[TUFLOW Message 2025|2025 ]] || [[TUFLOW Message 2026|2026 ]] || [[TUFLOW Message 2027|2027 ]] || [[TUFLOW Message 2028|2028 ]] || [[TUFLOW Message 2029|2029 ]] || [[TUFLOW Message 2030|2030 ]] || [[TUFLOW Message 2031|2031 ]] || [[TUFLOW Message 2032|2032 ]] || [[TUFLOW Message 2033|2033 ]] || [[TUFLOW Message 2034|2034 ]] || [[TUFLOW Message 2035|2035 ]] || [[TUFLOW Message 2036|2036 ]] || [[TUFLOW Message 2037|2037 ]] || [[TUFLOW Message 2038|2038 ]] || [[TUFLOW Message 2039|2039 ]]
|-
|[[TUFLOW Message 2040|2040 ]] || [[TUFLOW Message 2041|2041 ]] || [[TUFLOW Message 2042|2042 ]] || [[TUFLOW Message 2043|2043 ]] || [[TUFLOW Message 2044|2044 ]] || [[TUFLOW Message 2045|2045 ]] || [[TUFLOW Message 2046|2046 ]] || [[TUFLOW Message 2047|2047 ]] || [[TUFLOW Message 2048|2048 ]] || [[TUFLOW Message 2049|2049 ]] || [[TUFLOW Message 2050|2050 ]] || [[TUFLOW Message 2051|2051 ]] || [[TUFLOW Message 2052|2052 ]] || [[TUFLOW Message 2053|2053 ]] || [[TUFLOW Message 2054|2054 ]] || [[TUFLOW Message 2055|2055 ]] || [[TUFLOW Message 2056|2056 ]] || [[TUFLOW Message 2057|2057 ]] || [[TUFLOW Message 2058|2058 ]] || [[TUFLOW Message 2059|2059 ]]
|-
|[[TUFLOW Message 2060|2060 ]] || [[TUFLOW Message 2061|2061 ]] || [[TUFLOW Message 2062|2062 ]] || [[TUFLOW Message 2063|2063 ]] || [[TUFLOW Message 2064|2064 ]] || [[TUFLOW Message 2065|2065 ]] || [[TUFLOW Message 2066|2066 ]] || [[TUFLOW Message 2067|2067 ]] || [[TUFLOW Message 2068|2068 ]] || [[TUFLOW Message 2069|2069 ]] || [[TUFLOW Message 2070|2070 ]] || [[TUFLOW Message 2071|2071 ]] || [[TUFLOW Message 2072|2072 ]] || [[TUFLOW Message 2073|2073 ]] || [[TUFLOW Message 2074|2074 ]] || [[TUFLOW Message 2075|2075 ]] || [[TUFLOW Message 2076|2076 ]] || [[TUFLOW Message 2077|2077 ]] || [[TUFLOW Message 2078|2078 ]] || [[TUFLOW Message 2079|2079 ]]
|-
|[[TUFLOW Message 2080|2080 ]] || [[TUFLOW Message 2081|2081 ]] || [[TUFLOW Message 2082|2082 ]] || [[TUFLOW Message 2083|2083 ]] || [[TUFLOW Message 2084|2084 ]] || [[TUFLOW Message 2085|2085 ]] || [[TUFLOW Message 2086|2086 ]] || [[TUFLOW Message 2087|2087 ]] || [[TUFLOW Message 2088|2088 ]] || [[TUFLOW Message 2089|2089 ]] || [[TUFLOW Message 2090|2090 ]] || [[TUFLOW Message 2091|2091 ]] || [[TUFLOW Message 2092|2092 ]] || [[TUFLOW Message 2093|2093 ]] || [[TUFLOW Message 2094|2094 ]] || [[TUFLOW Message 2095|2095 ]] || [[TUFLOW Message 2096|2096 ]] || [[TUFLOW Message 2097|2097 ]] || [[TUFLOW Message 2098|2098 ]] || [[TUFLOW Message 2099|2099 ]]
|-
|[[TUFLOW Message 2100|2100 ]] || [[TUFLOW Message 2101|2101 ]] || [[TUFLOW Message 2102|2102 ]] || [[TUFLOW Message 2103|2103 ]] || [[TUFLOW Message 2104|2104 ]] || [[TUFLOW Message 2105|2105 ]] || [[TUFLOW Message 2106|2106 ]] || [[TUFLOW Message 2107|2107 ]] || [[TUFLOW Message 2108|2108 ]] || [[TUFLOW Message 2109|2109 ]] || [[TUFLOW Message 2110|2110 ]] || [[TUFLOW Message 2111|2111 ]] || [[TUFLOW Message 2112|2112 ]] || [[TUFLOW Message 2113|2113 ]] || [[TUFLOW Message 2114|2114 ]] || [[TUFLOW Message 2115|2115 ]] || [[TUFLOW Message 2116|2116 ]] || [[TUFLOW Message 2117|2117 ]] || [[TUFLOW Message 2118|2118 ]] || [[TUFLOW Message 2119|2119 ]]
|-
|[[TUFLOW Message 2120|2120 ]] || [[TUFLOW Message 2121|2121 ]] || [[TUFLOW Message 2122|2122 ]] || [[TUFLOW Message 2123|2123 ]] || [[TUFLOW Message 2124|2124 ]] || [[TUFLOW Message 2125|2125 ]] || [[TUFLOW Message 2126|2126 ]] || [[TUFLOW Message 2127|2127 ]] || [[TUFLOW Message 2128|2128 ]] || [[TUFLOW Message 2129|2129 ]] || [[TUFLOW Message 2130|2130 ]] || [[TUFLOW Message 2131|2131 ]] || [[TUFLOW Message 2132|2132 ]] || [[TUFLOW Message 2133|2133 ]] || [[TUFLOW Message 2134|2134 ]] || [[TUFLOW Message 2135|2135 ]] || [[TUFLOW Message 2136|2136 ]] || [[TUFLOW Message 2137|2137 ]] || [[TUFLOW Message 2138|2138 ]] || [[TUFLOW Message 2139|2139 ]]
|-
|[[TUFLOW Message 2140|2140 ]] || [[TUFLOW Message 2141|2141 ]] || [[TUFLOW Message 2142|2142 ]] || [[TUFLOW Message 2143|2143 ]] || [[TUFLOW Message 2144|2144 ]] || [[TUFLOW Message 2145|2145 ]] || [[TUFLOW Message 2146|2146 ]] || [[TUFLOW Message 2147|2147 ]] || [[TUFLOW Message 2148|2148 ]] || [[TUFLOW Message 2149|2149 ]] || [[TUFLOW Message 2150|2150 ]] || [[TUFLOW Message 2151|2151 ]] || [[TUFLOW Message 2152|2152 ]] || [[TUFLOW Message 2153|2153 ]] || [[TUFLOW Message 2154|2154 ]] || [[TUFLOW Message 2155|2155 ]] || [[TUFLOW Message 2156|2156 ]] || [[TUFLOW Message 2157|2157 ]] || [[TUFLOW Message 2158|2158 ]] || [[TUFLOW Message 2159|2159 ]]
|-
|[[TUFLOW Message 2160|2160 ]] || [[TUFLOW Message 2161|2161 ]] || [[TUFLOW Message 2162|2162 ]] || [[TUFLOW Message 2163|2163 ]] || [[TUFLOW Message 2164|2164 ]] || [[TUFLOW Message 2165|2165 ]] || [[TUFLOW Message 2166|2166 ]] || [[TUFLOW Message 2167|2167 ]] || [[TUFLOW Message 2168|2168 ]] || [[TUFLOW Message 2169|2169 ]] || [[TUFLOW Message 2170|2170 ]] || [[TUFLOW Message 2171|2171 ]] || [[TUFLOW Message 2172|2172 ]] || [[TUFLOW Message 2173|2173 ]] || [[TUFLOW Message 2174|2174 ]] || [[TUFLOW Message 2175|2175 ]] || [[TUFLOW Message 2176|2176 ]] || [[TUFLOW Message 2177|2177 ]] || [[TUFLOW Message 2178|2178 ]] || [[TUFLOW Message 2179|2179 ]]
|-
|[[TUFLOW Message 2180|2180 ]] || [[TUFLOW Message 2181|2181 ]] || [[TUFLOW Message 2182|2182 ]] || [[TUFLOW Message 2183|2183 ]] || [[TUFLOW Message 2184|2184 ]] || [[TUFLOW Message 2185|2185 ]] || [[TUFLOW Message 2186|2186 ]] || [[TUFLOW Message 2187|2187 ]] || [[TUFLOW Message 2188|2188 ]] || [[TUFLOW Message 2189|2189 ]] || [[TUFLOW Message 2190|2190 ]] || [[TUFLOW Message 2191|2191 ]] || [[TUFLOW Message 2192|2192 ]] || [[TUFLOW Message 2193|2193 ]] || [[TUFLOW Message 2194|2194 ]] || [[TUFLOW Message 2195|2195 ]] || [[TUFLOW Message 2196|2196 ]] || [[TUFLOW Message 2197|2197 ]] || [[TUFLOW Message 2198|2198 ]] || [[TUFLOW Message 2199|2199 ]]
|-
|[[TUFLOW Message 2200|2200 ]] || [[TUFLOW Message 2201|2201 ]] || [[TUFLOW Message 2202|2202 ]] || [[TUFLOW Message 2203|2203 ]] || 2204 || [[TUFLOW Message 2205|2205 ]] || [[TUFLOW Message 2206|2206 ]] || 2207 || 2208 || 2209 || [[TUFLOW Message 2210|2210 ]] || [[TUFLOW Message 2211|2211 ]] || [[TUFLOW Message 2212|2212 ]] || [[TUFLOW Message 2213|2213 ]] || [[TUFLOW Message 2214|2214 ]] || [[TUFLOW Message 2215|2215 ]] || [[TUFLOW Message 2216|2216 ]] || [[TUFLOW Message 2217|2217 ]] || [[TUFLOW Message 2218|2218 ]] || [[TUFLOW Message 2219|2219 ]]
|-
|[[TUFLOW Message 2220|2220 ]] || [[TUFLOW Message 2221|2221 ]] || [[TUFLOW Message 2222|2222 ]] || [[TUFLOW Message 2223|2223 ]] || [[TUFLOW Message 2224|2224 ]] || [[TUFLOW Message 2225|2225 ]] || [[TUFLOW Message 2226|2226 ]] || [[TUFLOW Message 2227|2227 ]] || [[TUFLOW Message 2228|2228 ]] || [[TUFLOW Message 2229|2229 ]] || [[TUFLOW Message 2230|2230 ]] || [[TUFLOW Message 2231|2231 ]] || [[TUFLOW Message 2232|2232 ]] || [[TUFLOW Message 2233|2233 ]] || [[TUFLOW Message 2234|2234 ]] || [[TUFLOW Message 2235|2235 ]] || [[TUFLOW Message 2236|2236 ]] || [[TUFLOW Message 2237|2237 ]] || [[TUFLOW Message 2238|2238 ]] || 2239
|-
|2300 || 2301 || 2302 || 2303 || 2304 || 2305 || 2306 || 2307 || [[TUFLOW Message 2308|2308 ]] || [[TUFLOW Message 2309|2309 ]] || [[TUFLOW Message 2310|2310 ]] || [[TUFLOW Message 2311|2311 ]] || 2312 || [[TUFLOW Message 2313|2313 ]] || 2314 || 2315 || 2316 || 2317 || 2318 || 2319
|-
|2320 || [[TUFLOW Message 2321|2321 ]] || 2322 || 2323 || 2324 || 2325 || 2326 || 2327 || 2328 || 2329 || 2330 || 2331 || 2332 || 2333 || 2334 || 2335 || 2336 || 2337 || 2338 || 2339
|-
|2340 || 2341 || 2342 || 2343 || 2344 || 2345 || 2346 || 2347 || 2348 || 2349 || [[TUFLOW Message 2350|2350 ]] || [[TUFLOW Message 2351|2351 ]] || [[TUFLOW Message 2352|2352 ]] || [[TUFLOW Message 2353|2353 ]] || [[TUFLOW Message 2354|2354 ]] || [[TUFLOW Message 2355|2355 ]] || [[TUFLOW Message 2356|2356 ]] || [[TUFLOW Message 2357|2357 ]] || [[TUFLOW Message 2358|2358 ]] || [[TUFLOW Message 2359|2359 ]]
|-
|[[TUFLOW Message 2360|2360 ]] || [[TUFLOW Message 2361|2361 ]] || [[TUFLOW Message 2362|2362 ]] || 2363 || 2364 || [[TUFLOW Message 2365|2365 ]] || 2366 || 2367 || 2368 || 2369 || 2370 || [[TUFLOW Message 2371|2371 ]] || [[TUFLOW Message 2372|2372 ]] || [[TUFLOW Message 2373|2373 ]] || [[TUFLOW Message 2374|2374 ]] || [[TUFLOW Message 2375|2375 ]] || [[TUFLOW Message 2376|2376 ]] || [[TUFLOW Message 2377|2377 ]] || 2378 || 2379
|-
|2380 || [[TUFLOW Message 2381|2381 ]] || [[TUFLOW Message 2382|2382 ]] || [[TUFLOW Message 2383|2383 ]] || 2384 || [[TUFLOW Message 2385|2385 ]] || 2386 || 2387 || 2388 || [[TUFLOW Message 2389|2389 ]] || 2390 || 2391 || 2392 || 2393 || 2394 || 2395 || 2396 || 2397 || 2398 || 2399
|-
|2400 || [[TUFLOW Message 2401|2401 ]] || [[TUFLOW Message 2402|2402 ]] || [[TUFLOW Message 2403|2403 ]] || [[TUFLOW Message 2404|2404 ]] || [[TUFLOW Message 2405|2405 ]] || [[TUFLOW Message 2406|2406 ]] || [[TUFLOW Message 2407|2407 ]] || [[TUFLOW Message 2408|2408 ]] || 2409 || 2410 || [[TUFLOW Message 2411|2411 ]] || [[TUFLOW Message 2412|2412 ]] || [[TUFLOW Message 2413|2413 ]] || [[TUFLOW Message 2414|2414 ]] || [[TUFLOW Message 2415|2415 ]] || [[TUFLOW Message 2416|2416 ]] || 2417 || [[TUFLOW Message 2418|2418 ]] || [[TUFLOW Message 2419|2419 ]]
|-
|2420 || [[TUFLOW Message 2421|2421 ]] || [[TUFLOW Message 2422|2422 ]] || [[TUFLOW Message 2423|2423 ]] || [[TUFLOW Message 2424|2424 ]] || [[TUFLOW Message 2425|2425 ]] || [[TUFLOW Message 2426|2426 ]] || [[TUFLOW Message 2427|2427 ]] || [[TUFLOW Message 2428|2428 ]] || [[TUFLOW Message 2429|2429 ]] || [[TUFLOW Message 2430|2430 ]] || [[TUFLOW Message 2431|2431 ]] || [[TUFLOW Message 2432|2432 ]] || 2433 || 2434 || 2435 || 2436 || 2437 || 2438 || 2439
|-
|2440 || [[TUFLOW Message 2441|2441 ]] || 2442 || 2443 || 2444 || 2445 || 2446 || 2447 || 2448 || 2449 || [[TUFLOW Message 2450|2450 ]] || [[TUFLOW Message 2451|2451 ]] || 2452 || 2453 || 2454 || 2455 || 2456 || 2457 || 2458 || 2459
|-
|[[TUFLOW Message 2460|2460 ]] || 2461 || 2462 || 2463 || 2464 || 2465 || 2466 || 2467 || 2468 || 2469 || 2470 || 2471 || 2472 || 2473 || 2474 || 2475 || 2476 || 2477 || 2478 || 2479
|-
|2980 || 2981 || 2982 || 2983 || 2984 || 2985 || 2986 || 2987 || 2988 || 2989 || 2990 || [[TUFLOW Message 2991|2991 ]] || 2992 || 2993 || 2994 || 2995 || 2996 || 2997 || [[TUFLOW Message 2998|2998 ]] || [[TUFLOW Message 2999|2999 ]]
|-
|}

2xxx TUFLOW Messages

2014-06-01T23:50:45Z

Bill Syme:

The 2xxx TUFLOW messages refer to issues that occur neither in the 2D model. Click on number to follow link to TUFLOW message description, grey numbers are reserved and do not yet have messages assigned, and red numbers have been allocated to new messages.

See also:
* [[0xxx TUFLOW Messages]]
* [[1xxx TUFLOW Messages]]
* [[9xxx TUFLOW Messages]]

{| Border ="1" cellpadding="8" style="text-align:center"
|2000 || [[TUFLOW Message 2001|2001 ]] || [[TUFLOW Message 2002|2002 ]] || [[TUFLOW Message 2003|2003 ]] || [[TUFLOW Message 2004|2004 ]] || [[TUFLOW Message 2005|2005 ]] || [[TUFLOW Message 2006|2006 ]] || [[TUFLOW Message 2007|2007 ]] || [[TUFLOW Message 2008|2008 ]] || [[TUFLOW Message 2009|2009 ]] || [[TUFLOW Message 2010|2010 ]] || [[TUFLOW Message 2011|2011 ]] || [[TUFLOW Message 2012|2012 ]] || [[TUFLOW Message 2013|2013 ]] || [[TUFLOW Message 2014|2014 ]] || [[TUFLOW Message 2015|2015 ]] || [[TUFLOW Message 2016|2016 ]] || [[TUFLOW Message 2017|2017 ]] || [[TUFLOW Message 2018|2018 ]] || [[TUFLOW Message 2019|2019 ]]
|-
|[[TUFLOW Message 2020|2020 ]] || [[TUFLOW Message 2021|2021 ]] || [[TUFLOW Message 2022|2022 ]] || [[TUFLOW Message 2023|2023 ]] || [[TUFLOW Message 2024|2024 ]] || [[TUFLOW Message 2025|2025 ]] || [[TUFLOW Message 2026|2026 ]] || [[TUFLOW Message 2027|2027 ]] || [[TUFLOW Message 2028|2028 ]] || [[TUFLOW Message 2029|2029 ]] || [[TUFLOW Message 2030|2030 ]] || [[TUFLOW Message 2031|2031 ]] || [[TUFLOW Message 2032|2032 ]] || [[TUFLOW Message 2033|2033 ]] || [[TUFLOW Message 2034|2034 ]] || [[TUFLOW Message 2035|2035 ]] || [[TUFLOW Message 2036|2036 ]] || [[TUFLOW Message 2037|2037 ]] || [[TUFLOW Message 2038|2038 ]] || [[TUFLOW Message 2039|2039 ]]
|-
|[[TUFLOW Message 2040|2040 ]] || [[TUFLOW Message 2041|2041 ]] || [[TUFLOW Message 2042|2042 ]] || [[TUFLOW Message 2043|2043 ]] || [[TUFLOW Message 2044|2044 ]] || [[TUFLOW Message 2045|2045 ]] || [[TUFLOW Message 2046|2046 ]] || [[TUFLOW Message 2047|2047 ]] || [[TUFLOW Message 2048|2048 ]] || [[TUFLOW Message 2049|2049 ]] || [[TUFLOW Message 2050|2050 ]] || [[TUFLOW Message 2051|2051 ]] || [[TUFLOW Message 2052|2052 ]] || [[TUFLOW Message 2053|2053 ]] || [[TUFLOW Message 2054|2054 ]] || [[TUFLOW Message 2055|2055 ]] || [[TUFLOW Message 2056|2056 ]] || [[TUFLOW Message 2057|2057 ]] || [[TUFLOW Message 2058|2058 ]] || [[TUFLOW Message 2059|2059 ]]
|-
|[[TUFLOW Message 2060|2060 ]] || [[TUFLOW Message 2061|2061 ]] || [[TUFLOW Message 2062|2062 ]] || [[TUFLOW Message 2063|2063 ]] || [[TUFLOW Message 2064|2064 ]] || [[TUFLOW Message 2065|2065 ]] || [[TUFLOW Message 2066|2066 ]] || [[TUFLOW Message 2067|2067 ]] || [[TUFLOW Message 2068|2068 ]] || [[TUFLOW Message 2069|2069 ]] || [[TUFLOW Message 2070|2070 ]] || [[TUFLOW Message 2071|2071 ]] || [[TUFLOW Message 2072|2072 ]] || [[TUFLOW Message 2073|2073 ]] || [[TUFLOW Message 2074|2074 ]] || [[TUFLOW Message 2075|2075 ]] || [[TUFLOW Message 2076|2076 ]] || [[TUFLOW Message 2077|2077 ]] || [[TUFLOW Message 2078|2078 ]] || [[TUFLOW Message 2079|2079 ]]
|-
|[[TUFLOW Message 2080|2080 ]] || [[TUFLOW Message 2081|2081 ]] || [[TUFLOW Message 2082|2082 ]] || [[TUFLOW Message 2083|2083 ]] || [[TUFLOW Message 2084|2084 ]] || [[TUFLOW Message 2085|2085 ]] || [[TUFLOW Message 2086|2086 ]] || [[TUFLOW Message 2087|2087 ]] || [[TUFLOW Message 2088|2088 ]] || [[TUFLOW Message 2089|2089 ]] || [[TUFLOW Message 2090|2090 ]] || [[TUFLOW Message 2091|2091 ]] || [[TUFLOW Message 2092|2092 ]] || [[TUFLOW Message 2093|2093 ]] || [[TUFLOW Message 2094|2094 ]] || [[TUFLOW Message 2095|2095 ]] || [[TUFLOW Message 2096|2096 ]] || [[TUFLOW Message 2097|2097 ]] || [[TUFLOW Message 2098|2098 ]] || [[TUFLOW Message 2099|2099 ]]
|-
|[[TUFLOW Message 2100|2100 ]] || [[TUFLOW Message 2101|2101 ]] || [[TUFLOW Message 2102|2102 ]] || [[TUFLOW Message 2103|2103 ]] || [[TUFLOW Message 2104|2104 ]] || [[TUFLOW Message 2105|2105 ]] || [[TUFLOW Message 2106|2106 ]] || [[TUFLOW Message 2107|2107 ]] || [[TUFLOW Message 2108|2108 ]] || [[TUFLOW Message 2109|2109 ]] || [[TUFLOW Message 2110|2110 ]] || [[TUFLOW Message 2111|2111 ]] || [[TUFLOW Message 2112|2112 ]] || [[TUFLOW Message 2113|2113 ]] || [[TUFLOW Message 2114|2114 ]] || [[TUFLOW Message 2115|2115 ]] || [[TUFLOW Message 2116|2116 ]] || [[TUFLOW Message 2117|2117 ]] || [[TUFLOW Message 2118|2118 ]] || [[TUFLOW Message 2119|2119 ]]
|-
|[[TUFLOW Message 2120|2120 ]] || [[TUFLOW Message 2121|2121 ]] || [[TUFLOW Message 2122|2122 ]] || [[TUFLOW Message 2123|2123 ]] || [[TUFLOW Message 2124|2124 ]] || [[TUFLOW Message 2125|2125 ]] || [[TUFLOW Message 2126|2126 ]] || [[TUFLOW Message 2127|2127 ]] || [[TUFLOW Message 2128|2128 ]] || [[TUFLOW Message 2129|2129 ]] || [[TUFLOW Message 2130|2130 ]] || [[TUFLOW Message 2131|2131 ]] || [[TUFLOW Message 2132|2132 ]] || [[TUFLOW Message 2133|2133 ]] || [[TUFLOW Message 2134|2134 ]] || [[TUFLOW Message 2135|2135 ]] || [[TUFLOW Message 2136|2136 ]] || [[TUFLOW Message 2137|2137 ]] || [[TUFLOW Message 2138|2138 ]] || [[TUFLOW Message 2139|2139 ]]
|-
|[[TUFLOW Message 2140|2140 ]] || [[TUFLOW Message 2141|2141 ]] || [[TUFLOW Message 2142|2142 ]] || [[TUFLOW Message 2143|2143 ]] || [[TUFLOW Message 2144|2144 ]] || [[TUFLOW Message 2145|2145 ]] || [[TUFLOW Message 2146|2146 ]] || [[TUFLOW Message 2147|2147 ]] || [[TUFLOW Message 2148|2148 ]] || [[TUFLOW Message 2149|2149 ]] || [[TUFLOW Message 2150|2150 ]] || [[TUFLOW Message 2151|2151 ]] || [[TUFLOW Message 2152|2152 ]] || [[TUFLOW Message 2153|2153 ]] || [[TUFLOW Message 2154|2154 ]] || [[TUFLOW Message 2155|2155 ]] || [[TUFLOW Message 2156|2156 ]] || [[TUFLOW Message 2157|2157 ]] || [[TUFLOW Message 2158|2158 ]] || [[TUFLOW Message 2159|2159 ]]
|-
|[[TUFLOW Message 2160|2160 ]] || [[TUFLOW Message 2161|2161 ]] || [[TUFLOW Message 2162|2162 ]] || [[TUFLOW Message 2163|2163 ]] || [[TUFLOW Message 2164|2164 ]] || [[TUFLOW Message 2165|2165 ]] || [[TUFLOW Message 2166|2166 ]] || [[TUFLOW Message 2167|2167 ]] || [[TUFLOW Message 2168|2168 ]] || [[TUFLOW Message 2169|2169 ]] || [[TUFLOW Message 2170|2170 ]] || [[TUFLOW Message 2171|2171 ]] || [[TUFLOW Message 2172|2172 ]] || [[TUFLOW Message 2173|2173 ]] || [[TUFLOW Message 2174|2174 ]] || [[TUFLOW Message 2175|2175 ]] || [[TUFLOW Message 2176|2176 ]] || [[TUFLOW Message 2177|2177 ]] || [[TUFLOW Message 2178|2178 ]] || [[TUFLOW Message 2179|2179 ]]
|-
|[[TUFLOW Message 2180|2180 ]] || [[TUFLOW Message 2181|2181 ]] || [[TUFLOW Message 2182|2182 ]] || [[TUFLOW Message 2183|2183 ]] || [[TUFLOW Message 2184|2184 ]] || [[TUFLOW Message 2185|2185 ]] || [[TUFLOW Message 2186|2186 ]] || [[TUFLOW Message 2187|2187 ]] || [[TUFLOW Message 2188|2188 ]] || [[TUFLOW Message 2189|2189 ]] || [[TUFLOW Message 2190|2190 ]] || [[TUFLOW Message 2191|2191 ]] || [[TUFLOW Message 2192|2192 ]] || [[TUFLOW Message 2193|2193 ]] || [[TUFLOW Message 2194|2194 ]] || [[TUFLOW Message 2195|2195 ]] || [[TUFLOW Message 2196|2196 ]] || [[TUFLOW Message 2197|2197 ]] || [[TUFLOW Message 2198|2198 ]] || [[TUFLOW Message 2199|2199 ]]
|-
|[[TUFLOW Message 2200|2200 ]] || [[TUFLOW Message 2201|2201 ]] || [[TUFLOW Message 2202|2202 ]] || [[TUFLOW Message 2203|2203 ]] || 2204 || [[TUFLOW Message 2205|2205 ]] || [[TUFLOW Message 2206|2206 ]] || 2207 || 2208 || 2209 || [[TUFLOW Message 2210|2210 ]] || [[TUFLOW Message 2211|2211 ]] || [[TUFLOW Message 2212|2212 ]] || [[TUFLOW Message 2213|2213 ]] || [[TUFLOW Message 2214|2214 ]] || [[TUFLOW Message 2215|2215 ]] || [[TUFLOW Message 2216|2216 ]] || [[TUFLOW Message 2217|2217 ]] || [[TUFLOW Message 2218|2218 ]] || [[TUFLOW Message 2219|2219 ]]
|-
|[[TUFLOW Message 2220|2220 ]] || [[TUFLOW Message 2221|2221 ]] || [[TUFLOW Message 2222|2222 ]] || [[TUFLOW Message 2223|2223 ]] || [[TUFLOW Message 2224|2224 ]] || [[TUFLOW Message 2225|2225 ]] || [[TUFLOW Message 2226|2226 ]] || [[TUFLOW Message 2227|2227 ]] || [[TUFLOW Message 2228|2228 ]] || [[TUFLOW Message 2229|2229 ]] || [[TUFLOW Message 2230|2230 ]] || [[TUFLOW Message 2231|2231 ]] || [[TUFLOW Message 2232|2232 ]] || [[TUFLOW Message 2233|2233 ]] || [[TUFLOW Message 2234|2234 ]] || [[TUFLOW Message 2235|2235 ]] || [[TUFLOW Message 2236|2236 ]] || [[TUFLOW Message 2237|2237 ]] || [[TUFLOW Message 2238|2238 ]] || 2239
|-
|2300 || 2301 || 2302 || 2303 || 2304 || 2305 || 2306 || 2307 || [[TUFLOW Message 2308|2308 ]] || [[TUFLOW Message 2309|2309 ]] || [[TUFLOW Message 2310|2310 ]] || [[TUFLOW Message 2311|2311 ]] || 2312 || [[TUFLOW Message 2313|2313 ]] || 2314 || 2315 || 2316 || 2317 || 2318 || 2319
|-
|2320 || [[TUFLOW Message 2321|2321 ]] || 2322 || 2323 || 2324 || 2325 || 2326 || 2327 || 2328 || 2329 || 2330 || 2331 || 2332 || 2333 || 2334 || 2335 || 2336 || 2337 || 2338 || 2339
|-
|2340 || 2341 || 2342 || 2343 || 2344 || 2345 || 2346 || 2347 || 2348 || 2349 || [[TUFLOW Message 2350|2350 ]] || [[TUFLOW Message 2351|2351 ]] || [[TUFLOW Message 2352|2352 ]] || [[TUFLOW Message 2353|2353 ]] || [[TUFLOW Message 2354|2354 ]] || [[TUFLOW Message 2355|2355 ]] || [[TUFLOW Message 2356|2356 ]] || [[TUFLOW Message 2357|2357 ]] || [[TUFLOW Message 2358|2358 ]] || [[TUFLOW Message 2359|2359 ]]
|-
|[[TUFLOW Message 2360|2360 ]] || [[TUFLOW Message 2361|2361 ]] || [[TUFLOW Message 2362|2362 ]] || 2363 || 2364 || [[TUFLOW Message 2365|2365 ]] || 2366 || 2367 || 2368 || 2369 || 2370 || [[TUFLOW Message 2371|2371 ]] || [[TUFLOW Message 2372|2372 ]] || [[TUFLOW Message 2373|2373 ]] || [[TUFLOW Message 2374|2374 ]] || [[TUFLOW Message 2375|2375 ]] || [[TUFLOW Message 2376|2376 ]] || [[TUFLOW Message 2377|2377 ]] || 2378 || 2379
|-
|2380 || [[TUFLOW Message 2381|2381 ]] || [[TUFLOW Message 2382|2382 ]] || [[TUFLOW Message 2383|2383 ]] || 2384 || [[TUFLOW Message 2385|2385 ]] || 2386 || 2387 || 2388 || [[TUFLOW Message 2389|2389 ]] || 2390 || 2391 || 2392 || 2393 || 2394 || 2395 || 2396 || 2397 || 2398 || 2399
|-
|2400 || [[TUFLOW Message 2401|2401 ]] || [[TUFLOW Message 2402|2402 ]] || [[TUFLOW Message 2403|2403 ]] || [[TUFLOW Message 2404|2404 ]] || [[TUFLOW Message 2405|2405 ]] || [[TUFLOW Message 2406|2406 ]] || [[TUFLOW Message 2407|2407 ]] || [[TUFLOW Message 2408|2408 ]] || 2409 || 2410 || [[TUFLOW Message 2411|2411 ]] || [[TUFLOW Message 2412|2412 ]] || [[TUFLOW Message 2413|2413 ]] || [[TUFLOW Message 2414|2414 ]] || [[TUFLOW Message 2415|2415 ]] || [[TUFLOW Message 2416|2416 ]] || 2417 || [[TUFLOW Message 2418|2418 ]] || [[TUFLOW Message 2419|2419 ]]
|-
|2420 || [[TUFLOW Message 2421|2421 ]] || [[TUFLOW Message 2422|2422 ]] || [[TUFLOW Message 2423|2423 ]] || [[TUFLOW Message 2424|2424 ]] || [[TUFLOW Message 2425|2425 ]] || [[TUFLOW Message 2426|2426 ]] || [[TUFLOW Message 2427|2427 ]] || [[TUFLOW Message 2428|2428 ]] || [[TUFLOW Message 2429|2429 ]] || [[TUFLOW Message 2430|2430 ]] || [[TUFLOW Message 2431|2431 ]] || [[TUFLOW Message 2432|2432 ]] || 2433 || 2434 || 2435 || 2436 || 2437 || 2438 || 2439
|-
|2440 || [[TUFLOW Message 2441|2441 ]] || 2442 || 2443 || 2444 || 2445 || 2446 || 2447 || 2448 || 2449 || [[TUFLOW Message 2450|2450 ]] || [[TUFLOW Message 2451|2451 ]] || 2452 || 2453 || 2454 || 2455 || 2456 || 2457 || 2458 || 2459
|-
|[[TUFLOW Message 2460|2460 ]] || 2461 || 2462 || 2463 || 2464 || 2465 || 2466 || 2467 || 2468 || 2469 || 2470 || 2471 || 2472 || 2473 || 2474 || 2475 || 2476 || 2477 || 2478 || 2479
|-
|2980 || 2981 || 2982 || 2983 || 2984 || 2985 || 2986 || 2987 || 2988 || 2989 || 2990 || [[TUFLOW Message 2991|2991 ]] || 2992 || 2993 || 2994 || 2995 || 2996 || 2997 || [[TUFLOW Message 2998|2998 ]] || [[TUFLOW Message 2999|2999 ]]
|-
|}