Breach model (Water Overlay): Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
Line 48: Line 48:
* Instead of using an input area you can also define a fictitious external area, this can represent a larger water body outside the project area, e.g. a part of a sea. The external area also has it's own [[External_surface_level_(Water_Overlay)|Surface level]], [[External_water_level_(Water_Overlay)|Water level]] and [[External_area_(Water_Overlay)|Area]].
* Instead of using an input area you can also define a fictitious external area, this can represent a larger water body outside the project area, e.g. a part of a sea. The external area also has it's own [[External_surface_level_(Water_Overlay)|Surface level]], [[External_water_level_(Water_Overlay)|Water level]] and [[External_area_(Water_Overlay)|Area]].
* If no [[Breach_speed_(Water_Overlay)|BREACH_SPEED]] attribute is defined, the active breach will never grow.  
* If no [[Breach_speed_(Water_Overlay)|BREACH_SPEED]] attribute is defined, the active breach will never grow.  


{{article end
{{article end

Revision as of 16:13, 18 January 2023

A Breach can be defined as an area and is identified via the BREACH_HEIGHT key. Water flowing through the breach originates from a body of water. This body of water can be defined as an input area in the project or a conceptual external water body existing outside the project area. Water can flow through the breach from the input water body to the defined Breach area, and vice versa.

The breach is simulated as a generic weir with breach characteristics that models the energy loss, the weir input/output is dynamically mapped onto the 2D grid cells. Using the Verheij–van der Knaap method the breach can also grow over time from phase one deepening to phase two widening.

Breach placement

A breach is defined using an Area that has the key BREACH_HEIGHT set. Its base are is defined by the geometry of the breach area. The breach is also given a starting width. Optionally it can also be given an angle, which is used in the flow formula and in placing the downstream level measurement point.

The images below show two different setups. Note that the configuration of input and level measuring can also be done in a different combination, not only the two shown below.

Breach input

The origin of the water flowing through the breach can be done in two ways:

External source

When using an external source, it is quite easy to set up. This setup is useful when there is a large body of water that does not fit within your projects bounds. It is currently not possible to configure a manually changing external water level during simulation; the water level lowers or rises only based on the amount of water that has flown through the breach. Each individual breach uses its own external water body; these are not shared among breaches.

Input Area

When you want to simulate a breach with a body of water situated within your project bounds, you can also use input area. An input area is expected to be situated in a Water area . Input areas are not allowed to overlap. However, they are allowed to be situated within the same water area.

Each Breach simulation step the water level will be determined for the input are and the breach area and used to calculate the flow. The calculated amount is then removed from the input area and the water levels are recalculated for the input area. During the water simulation steps, water can flow into the input area according to the surface water model calculations.

Breach flow

The amount of water that flows through a breach is calculated each timestep based on:

  • The calculated water levels on both sides, based on the configuration mentioned in the previous section.
  • The parameters of the breach;

Breach flow direction

Water flowing through the breach will flow in the direction defined by the BREACH_ANGLE attribute, regardless of whether the water flowed onto the breach from elsewhere in the water model, or from the simulated external water body. When no BREACH_ANGLE is defined, water can flow in any direction. Adding this attribute with also convert the breach advection speed (m/s) into the 2D cell of the breach area. It is recommended to always use this attribute for optimal flow.


Breach width growth

  • The breach can grow over time, based on its initial width, critical speed and inner and outer water level, for more details see Verheij–van der Knaap growth formula.
  • If a BREACH_WIDTH attribute is defined, the breach's polygon is intersected with a circle emanating from the center-point of the polygon. It is only in that intersection, called "active", that water will flow in from the input area. The radius of the circle defining the intersection will expand as the breach grows over time.
  • If no width is defined, the width is assumed to be very large, using the full Breach area polygon.
  • With larger breaches the water level inside the breach area can become turbulent. Therefor the inner water level (used for breach growth) is measured at a distance defined in BREACH_MEASUREMENT_DISTANCE_M behind the breach area when an BREACH_ANGLE is provided.
  • Instead of using an input area you can also define a fictitious external area, this can represent a larger water body outside the project area, e.g. a part of a sea. The external area also has it's own Surface level, Water level and Area.
  • If no BREACH_SPEED attribute is defined, the active breach will never grow.

Notes

  • The elevation model covered by the entire breach area is lowered to at least the minimum height defined by its BREACH_HEIGHT attribute. This is to prevent the terrain height from interfering with the flow.
  • When using breach growth the inner water level is computed from the average value in the active breach area. For optimal flow simulation it is therefor recommended to place the breach area just behind the levee on a flat space.
  • Water on a breach area is automatically spread across the entire active breach area equally.
  • The inner/outer water levels and breach width are visualized per timeframe on the breach object in the 3D map, these can be very useful to see how the breach is progressing.
  • The Base Types Result child overlay can be used to see which part of entire the breach area is considered "active". Breach growth can be seen when checking multiple timeframes.
  • You can also optionally change the default breach weir coefficient to model energy loss by adding a WEIR_COEFFICIENT attribute to the Breach area.
  • When the water level of in the input area drops over time the flow can also reverse, flowing back into the e.g. the river/sea.

See also