# 1D2D Exchange

3Di offers the possibility to make connections between the 1D and the 2D domain. This offers the possibility to preserve the complexity of the modelling domain, but to make use of the extra resolution and speed of 1D computations. In such case, the 1D elements are generally narrow compared to the dimensions of the 2D resolution.

## Calculation types

In 1D-2D schematisations, the interaction between the each 1D element and the 2D domain can be set by choosing the calculation type. The following calculation types can be chosen.

Isolated: no connection to the 2D domain

Connected: one connection to the 2D domain

Double connected: two connections to the 2D domain

Embedded: fully integrated with the 2D domain

In the figure below, three channels are drawn within a 2D domain. It shows a connected channel (orange), a double connected channel (purple) and an embedded channel (green). The squares indicate the computational points of the water level and the circles the locations of the velocity points. Their connections with the 2D domain are indicated with curved, dashed lines.

Calculation types are defined for individual 1D elements; different calculation types can be combined in one model.

### Isolated

1D elements with calculation type *isolated* do not interact with the 2D surface domain. This calculation type is also used for 1D elements in models without 2D flow.

### Connected

#### Description

When the calculation type is *connected*, a 1D2D connection is made for each calculation node, connecting it to the 2D cell it is in. Each 1D2D connection has an exchange level. Water will start flowing through the 1D2D connection when the water level exceeds the exchange level in either the 1D or the 2D computational point. This is illustrated in the figure below.

How flow through 1D2D connections is calculated is described in :flow_1d2d:

#### Customising 1D2D connections for channels

By default, 1D2D connections connect the 1D calculation point to the 2D cell it is in. For channels, this can be customised using a Exchange line. For each 1D calculation point, the closest point on the exchange line is found and the 1D2D connection is made with the 2D cell this closest point is in.

A Potential breach creates a single 1D2D exchange line from a channel to the 2D cell the end of the potential breach line is in.

These customisation options are available for channels only; not for culverts, pipes, or manholes.

#### Which exchange level is used?

Several schematisation objects have attributes to set the exchange level of 1D2D connections. When building the computational grid, 3Di uses a fixed hierarchy to process these values. If the first item in the hierachy is not available, it uses the next item; if that is not available, the next; et cetera.

Potential breach: Exchange Level (channels only)

Exchange line: Exchange level (channels only)

Maximum crest level of all intersected obstacles

Bank level (interpolated; for channels) or Drain level (for manholes)

DEM value at the 1D end of the 1D-2D connection

### Embedded

#### Description

When the calculation type is embedded, the 1D element uses the 2D calculation nodes (and its water level) instead of separate 1D nodes.

The figure below shows an embedded channel in the computational grid. 3Di fixes the locations where the 1D element crosses the 2D cells. In between those points, the 1D embedded point is defined (green stars in the figure). These are merged with the 2D calculation nodes: there is only one water level, used in both the 1D and the 2D domain. However, these 2D calculation nodes are now connected by two flowlines: the original 2D flowline, and the embedded 1D flowline. The velocities and discharges through the embedded 1D flowline are computed with the 1D flow equation.

#### Storage in embedded nodes

The embedded element modifies the storage of the 2D cell it is embedded in. The figure below shows three possible configurations: 1. The embedded channel is fully below the pixels of the 2D cell. All the storage in the 1D cross-section is added to the storage of the 2D cell. 2. The embedded cross-section is wider than the 2D cell. This is allowed in 3Di, but it is not recommended. 3. The elevations in the embedded 1D cross-section overlap with the elevations of the pixels in the 2D cell. The storage in the part of the cross-section below the pixels in the 2D domain is added to the storage of the 2D cell. The part of the 1D cross-section that is above the highest pixel in the 2D cell is ignored.

#### Cross-sectional area in embedded flowlines

The cross-sectional area that is used in the 1D flow calculation is determined in a way similar to how the storage is handled. The part of the 1D cross-section that is below the DEM pixels is used, the rest is ignored. The cross-sectional area that is used for the calculation of 2D flow is unaltered by the embedded elements that pass through the cells.

## 1D2D Flow

Flow through a 1D2D connection is computed using a reduced momentum balance:

This momentum equation in combination with a cross-section defines the flux between the computational domains.

The cross-sectional area of the 1D2D connection is the exchange depth times an exchange length. This exchange length is calculated in a different way for channels and for pipes. For pipes, the exchange length is based on the storage areas of the corresponding connection node [S]:

In case of open water elements, there calculation of the exchange length is different for connected (two banks per 1D2D connection) and double connected (one bank per 1D2D connection). For connected elements:

For double connected elements this implies:

## Breach flow

Breaches are a special case of 1D2D connections. The flow through a breach is calculated with the broad crested weir equation, more information on the exact calculation of breach flow can be found in Breach flow.