Setting Outfall Boundary Condition

In GeoSTORM, an outfall (or terminal outfall) is a terminal node in the stormwater drainage system that defines the downstream boundary condition of the modeled network.

While an outfall acts as a physical structure that releases flow into a large receiving body, such as a river, lake, or ocean, its primary role in the model is to set the boundary condition at the downstream end of the system. Refer to this article in our knowledge base to learn more about terminal outfalls.

Since an outfall defines the downstream boundary of the network, correctly describing boundary conditions is essential for obtaining reliable simulation results. An improperly defined boundary condition may lead to inaccurate hydraulic grade line (HGL) calculations, backwater effects, or flow routing errors.

Why Outfall Boundary Conditions Matter

The downstream boundary is a core model input that can highly impact computed water surface elevations near the outlet. The selected boundary condition tells the model how the downstream system behaves during the simulation.

This is important because the same drainage network can produce different results depending on whether the flow is:

• leaving freely
• entering a downstream channel
• discharging into a fixed water level, or
• responding to a time-varying tailwater condition

For example, a freely discharging pipe will generally allow flow to leave the system with minimal downstream restriction. In contrast, a pipe discharging into a river, pond, lake, or tidal water body may experience tailwater that can slow the flow, create backwater, or cause surcharge to extend upstream into the pipe network.

For this reason, the boundary condition should be selected based on the actual downstream hydraulic condition being represented.

Types of Outfall Boundary Conditions

In GeoSTORM, the boundary conditions at the terminal outfall can be described by any one of the following conditions:

Critical Depth

When Critical Depth is selected as the outfall boundary condition, the software will compute the boundary stage as the minimum of critical depth and normal depth. The user can select this boundary condition when the outfall discharges freely into the air, such as a culvert discharging above ground or into a steep drop.

Normal Depth

When Normal Depth is selected as the outfall boundary condition, the software will compute the boundary stage at the outfall node based on the normal depth of flow in the connecting conduit. The user can select this boundary condition when the downstream behaves like a long, uniform channel.

Fixed Water Surface Elevation (WSEL)

When Fixed WSEL is selected as the outfall boundary condition, the specified elevation remains constant throughout the simulation. The user can select this boundary condition when a constant downstream water level is known (e.g., discharging into a pond, lake, or controlled pool).

Tidal Boundary

When Tidal Boundary is selected as the outfall boundary condition, the software will require a data table of tidal elevation versus hour of the day. The user can select this boundary condition when the outfall is subject to tidal fluctuations.

Time Series

When Time Series is selected as the outfall boundary condition, the software will require a user-defined stage (water surface elevation) time series covering the full simulation duration. The user can select this boundary condition when downstream water levels vary with time, such as when discharging into a river or reservoir.

In GeoSTORM, the Terminal Outfall Data dialog box allows the user to select and apply these outfall boundary conditions using the Outfall type dropdown combo box entry.

Refer to this article in our knowledge base to learn more about the Terminal Outfall Data command.

Choosing the Right Outfall Boundary Condition

GeoSTORM allows the outfall boundary condition to be defined using one of the available outfall types. The correct option is dependent on how the downstream receiving system behaves during the simulation.

Common Errors While Setting the Outfall Boundary Condition

When defining outfall boundaries, the user needs to avoid these common mistakes:

• Entering depths instead of elevations
  For Tidal Boundary or Time Series outfall types, data must represent absolute water surface elevations used by the model, not depths relative to the invert. Entering depth values instead of elevation values in the data grids can lead to incorrect results.
• Not covering the full simulation duration with tailwater data
  Data gaps can result in incorrect or constant water level assumptions. Ensure that the time series or tidal table covers the entire simulation duration, including the necessary start and end periods.
• Using Critical Depth for backwater conditions
  When backwater conditions exist downstream, using the Critical Depth outfall type may underestimate tailwater impacts and give unrealistic results.
• Entering negative depths at terminal outfalls
  Negative depth values are invalid at terminal outfalls and using them for computation can result in errors.

Conclusion

The outfall boundary condition defines how the modeled drainage network interacts with the downstream receiving system. Selecting the right boundary type, using the correct elevation reference, and reviewing results near the outfall helps ensure that the model produces realistic water surface elevations, backwater effects, and surcharge behavior.