DHI.Mike1D.NetworkDataAccess Namespace

A SewerNode includes cover functionality to a Node

Geometry of a basin

Class containing information on where a specific catchment is connected in the network, and the area of the catchment that goes into that part of the network.

The connection in the network is defined by a NodeID or ReachId and and up- and down-stream chainage. If the two chainages are the same, the connection is a point connection, otherwise it is a span (distributed) connection.

Class implementing a list of ICatchmentConnection's Required for generic list COM interop

Base class for cover implementations.

A coordinate that can specify whether the chainage has been user specified (fixed) or calculated.

Set of parameters that describes how and with what data the head loss calculations are performed. Parameters in this class covers the standard head loss calculations that are performed and implemented in a sewer system.

Infiltration parameters

Base class for river network nodes.

A Manhole is a sewer node where network reaches join. It includes a diameter and a cover.

Data for coupling MIKE SHE to MIKE 1D, defining a single link between the two.

Data set for coupling MIKE SHE to MIKE 1D

Defines a 1D network, nodes and reaches.

Bridge for storing and loading the network data object to/from xml.

Extension methods related to NetworkData classes

Factory for creating different classes for the DHI.Mike1D.NetworkDataAccess namespace.

Base class for river network nodes.

Class implementing a list of INode's Required for generic list COM interop

If the water level in a manhole or a basin reaches the ground level, an artificial “inundation” basin is inserted above the node. The surface area of this basin is gradually (over one meter) increased from the area in the manhole or the basin to a 1000 times larger area, thus simulating the surface inundation. The maximum level of inundation is 10 meter above the specified ground level. When the outflow from the node surmounts the inflow, the water stored in the inundation basin re-enters the system. When the water level in the node increases and is above ground level, the following is assumed: During a time step the surface area in the basin is calculated using the water level from the start of the actual time step. A situation like this is shown in Figure 8.1. If the water level passes through the transition region between the actual manhole or structure and the artificial basin, this assumption leads to generation of water. In Figure 8.1 the shaded area illustrates the generated volume of water. Figure 8.1 Simulation of the surface flooding When the increase of the water level during a time step is relatively small, then the generated water volume is negligible. If the water level is changing rapidly, the generated volume of water is important and due to that an appropriate correction is built in the program to ensure no generation of water.

An Outlet is a volume free node where water flows out of the system.

An outlet is the only type of open boundary that does not need a boundary condition

An outlet can have a boundary condition (water level/QH), in which case the water can also flow into the system.

The IOutlet extends the IVolumeNode, though it can also be used outside a sewer system, in which case the GroundLevel is set to the BottomLevel. The rest of the IVolumeNode properties are not valid for a non-sewer outlet.

Description of headloss from node outlets

Base class for Link and Branch

Class implementing a list of IReach's Required for generic list COM interop

Routing element, from previous routing element to this routing element, this interface specifies what kind of routing is applied.

A reach where water is routed through, using one or several IRoutingElement's.

Any manhole or basin can be defined as 'sealed'. If a node is defined as a sealed node, then the maximum water level at a node is set to the ground surface. In this case, the pressure will rise without any water on the ground surface. The following relations are valid: Hm=Pm for Pm SmallerOrEqual Htop (8.1) and Hm=HTop fopr where: Hm is the water level in the node [m], Pm is the pressure level in the node [m], Htop is the ground level for the node [m].

A sewer junction is connecting to two or more sewer links

A SewerNode includes cover functionality to a Node

Any manhole or basin can be defined as 'spilling'. If the water level in a node defined as a spilling node reaches the ground level, the water will start spilling irreversibly out of the system. The flow will be computed using the free overflow formula, according to the following: for Hm SmallerOrEqualTo Htop+deltaP (8.2) Qspill = 0 for Hm LargerThan Htop+deltaP (8.2) Qspill = Relative Weir Coefficient*0.63*B*sqrt(2g)*(Hm-(Htop+deltaP))^1.5 here: Qspill= the spill discharge [m3/s], B = a conceptual spill width [m], Hm = the water level in the manhole [m], Htop = the ground level in the manhole [m], deltaP = the "Buffer Pressure Level" for the spill [m], g = the acceleration of gravity [ms-2), RelativeWeirCoefficient = the linear scaling coefficient for the spill.

Special kind of outlet: When a structure is discharging directly out of the system, and no outlet has been explicitly specified, the engine will put in a StuctureOutlet downstream of the structure.

A structure reach is an "artificial" reach containing one structure and no volume. It the reach has a length, it is an "artificial" length.

A structure reach is used for two common scenarios: a structure in a node, and a structure between the main river and the side river (link channel).

A structure in a node is modelled by defining two nodes with a structure reach in between.

A volume node is a node with volume that has a physical interpretation in the real world.

A Basin is a generalization of a IManhole, it can have any shape, the geometry is defined through the BasinGeometry.

Interface for information on where a specific catchment is connected in the network, and the area of the catchment that goes into that part of the network. The connection in the network is here defined by a ReachId and and up- and down-stream chainage. If the two chainages are the same, the connection is a point connection, otherwise it is a span (distributed) connection.

Interface for a list of ICatchmentConnection's Required for generic list COM interop

A cover can be put on top of a volume/sewer node, as e.g. a manhole, set at Cover

A leaping weir is a junction node which connects three reaches. The third reach is connected through a bottom opening, named a Leaping Weir. If the water runs fast, the water may leap over the weir, i.e. the speed of the water will effect the flow through the weir.

The weir is characterised by a length (WeirLength) and a width (WeirWidth).

Based on the article of Oliveto, Giuseppe. (1998). "Sewerage overflows: new researches on bottom openings and side weirs". Excerpta. 12. 251-281.

A Manhole is a sewer node where network reaches join. It includes a diameter and a cover.

Defines a 1D network, nodes and reaches.

Interface that is implemented by all node types. That is all nodes has ID and coordinates.

The most basic node, the junction node used in river junctions, implements this interface.

Note that junction nodes are automatically created for reach connections that are based on locations, so there will be more junction nodes than actual INodes defined here.

Interface for a list of INode's Required for generic list COM interop

Normal cover, see NormalCover

An Outlet is a volume free node where water flows out of the system.

An outlet is the only type of open boundary that does not need a boundary condition

An outlet can have a boundary condition (water level/QH), in which case the water can also flow into the system.

The IOutlet extends the IVolumeNode, though it can also be used outside a sewer system, in which case the GroundLevel is set to the BottomLevel. The rest of the IVolumeNode properties are not valid for a non-sewer outlet.

A Reach is a generalization of the link and branch concepts from sewer and river models.

Specification of connection as 'start' and 'end' does not have any impact on the computations, apart that positive flow is considered from start to end. Therefore, it is recommended to specify the start-end in the direction of predominant flows, or to set the ReverseDirection flag.

The type of the reach is specified by the cross section for that reach. It may take the form of one of the 'standard' pipes (Circular, Rectangular, O Shaped, Egg-Shaped), or any closed or open cross section shape (CRS/Natural Channels).

The LocationSpan defines the geographical position of the reach.

Typical types of reaches are the sewer link and the river branch.

A sewer link is featured by:

• Connected in each end by specifying a node.
• Constant cross-section geometry, and constant friction properties along the entire length.
• It is specified as a conduit between two nodes. A link is considered as either a straight line or a drawn polyline between two nodes.
• Usually a link connects to the adjacent nodes at their bottom levels, but it may also connect above their bottom level. This is called the invert level. The start- and the end- invert level must be specified in the first and last coordinates of the LocationSpan. Specified levels below bottom level of the connecting nodes is not valid.
• A link is often characterised by material, which determines the Manning friction coefficient (Manning) or the Colebrook White coefficient (Equivalent roughness). The material is is as such not represented, though the friction formulation is specified in the cross section module.

A river branch is featured by:

• Connected to other reaches by specifying a location. Nodes usually are not specified explicitly in the setup, but created on the fly when required (at all junctions).
• Varying cross-section geometry, and varying friction properties along reach.
• At connection points, river branches usually define cross section bottom levels that equals. However, if "free outflow" properties from a tributary branch is desired, this can be achieved by specifying a higher cross section bottom level in the tributary connection end (at least 0.5 cm difference).

Interface for a list of IReach's Required for generic list COM interop

Routing element, from previous routing element to this routing element, this interface specifies what kind of routing is applied.

A reach where water is routed through, using one or several IRoutingElement's.

A sealed cover

A sewer junction is connecting to two or more sewer links

ISewerNode includes cover functionality to a Node

A spilling cover, where water spills out of the network model.

A node without volume, but with Node structure functionality.

A structure reach is an "artificial" reach containing one structure and no volume. It the reach has a length, it is an "artificial" length.

A structure reach is used for two common scenarios: a structure in a node, and a structure between the main river and the side river (link channel).

A structure in a node is modelled by defining two nodes with a structure reach in between.

Interface for a node being underground

A volume node is a node with volume that has a physical interpretation in the real world.

The types of flows being handled by a CatchmentConnection

Infiltration types, specifying how infiltration is calculated in the node.

Node relation to pressurized parts of the network.