Icpr4 2d Manual
Icpr4 2d Manual
Volume 2, Chapter 19
        Overland Flow, Concepts and Theory
September 2017
Contents
19. Overland Flow, Concepts and Theory ......................................................................................... 5
   19.1 Basic Concepts ...................................................................................................................... 5
   19.2 Equations of Flow .................................................................................................................. 9
      19.2.1 Mass Balance Equation ................................................................................................... 9
      19.2.2 Momentum Equation.................................................................................................... 11
      19.2.3 Energy Equation ........................................................................................................... 11
      19.2.4 Diffusive Wave Equation............................................................................................... 12
      19.2.5 Manning’s n for Overland Flow ..................................................................................... 12
      19.2.6 Damping Threshold ...................................................................................................... 13
      19.2.7 Area Reduction Factor .................................................................................................. 13
      19.2.8 Edge Length and Slope ................................................................................................. 14
   19.3 Time Marching Algorithms .................................................................................................. 15
Water is moved from honeycomb to honeycomb along the sides of the triangles. Diamonds are
formed along the triangle sides and extend from the connecting vertices and the adjacent triangle
centroids as shown below. The diamonds are idealized into equivalent rectangles with averaged 2D
ground slopes.
The triangular mesh is constructed first and then the honeycomb and diamond meshes are derived
from the triangles. A quick overview of the mesh creation process and parameterization are
discussed in this section.
The honeycomb is formed around the triangle vertices as previously described and shown below.
Each honeycomb is treated as a drainage basin. The honeycomb is intersected with various polygon
mapping layers such as a soil zone map layer and a land cover zone map layer as shown above and to
the right. Sub-polygons (referred to as “basin polygons”) within each honeycomb are formed by this
intersection and a water balance is performed on each of them accounting for rainfall, surface
ponding, infiltration, evapotranspiration and applied irrigation. Once the losses are accounted for,
any remaining water is “rainfall excess”. The rainfall excess for all basin polygons within a given
honeycomb are summed and then applied directly to the 2D node located at the vertex of a triangle.
The hydraulics then move the rainfall excess from node to node.
Diamonds are intersected with a polygon map layer of “roughness zones”. These roughness zones
are used in conjunction with a roughness zone lookup table for setting Manning’s n, dampening
thresholds and area reduction factors. Area weighted values of each of these parameters are set at
runtime.
To summarize:
    1. ICPR constructs the triangular mesh from various graphical map features.
    2. Nodes are placed at the vertices.
    3. The honeycomb and diamond meshes are derived from the triangular mesh.
    4. Basins (catchment areas) are formed by the honeycombs.
    5. Links connect nodes along the sides of the triangles and are idealized as equivalent
       rectangles and average 2D slopes are calculated for the diamond.
    6. Ground elevations and initial water elevations at the nodes are extracted from DEMs.
    7. The diamond mesh is intersected with a roughness zone map layer to determine area-
       weighted Manning’s n, dampening threshold and area reduction factor.
    8. The honeycomb mesh is intersected with various map layers (e.g., soil, land cover, rainfall
       zones) to form basin polygons, each with its own set of infiltration and impervious
       characteristics.
                Q  Qout  
         dz   in            dt
               A
                   surface   
where,
and,
Q linkin sum of all link flow rates entering control volume (f3s-1, m3s-1)
Q linkout sum of all link flow rates leaving control volume (f3s-1, m3s-1)
Q excess sum of rainfall excess rates for all basin polygons (f 3s-1, m3s-1)
Q irrigation sum of irrigation water pulled from surface node (f3s-1, m3s-1)
As previously mentioned, an individual honeycomb is a basin or catchment area in ICPR. This basin
is further discretized by intersecting soil and land use polygons with the honeycomb as shown
below. The polygons formed by these intersections are referred to
as basin polygons. As will be discussed subsequently, additional
basin polygons can be formed by intersecting rainfall zone
polygons such as a NEXRAD fishnet or weather station Thiessen
polygons.
used to satisfy ET and can also infiltrate into the soil column. Consequently, it is possible to have a
negative rainfall excess value during a simulation.
The following form of the St. Venant equation is used in ICPR to calculate flow along the sides of
triangles (overland flow links). The solution algorithm is like that used in the EPA SWMM model (v5)
for 1D flow, but minor losses have been dropped for overland flow. The momentum equation
includes inertial terms for local and convective acceleration.
         Q   Q / A 
                  2
                             Z
                        gA     gAS f  0
         t      x          x
                    Qt  Qgravity  Qinertial
         Qt t 
                          1  Q friction
Qgravity  g A( Z1  Z 2 )t / L
                                        2
         Qinertial 2V ( A  At )  V ( A2  A1 ) t / L
                         gn 2 V t
         Q friction            4/3
                          k2 R
                V12       V2
         Z1         Z2  2  hf
                2g        2g
                                              1/ 2
                                           
                                           
                        Z1  Z 2           
         Q                                
            1  1  1   xC              
            2 g  A2 2 A12   f
                                            
Z1  Z 2  h f
n  nshallowe( k )( d )
                n     
            ln  deep 
                n
         k   shallow 
                d max
Shallow and deep Manning’s n values are specified by roughness zone in the 2D overland flow
roughness zone lookup tables.
When the absolute value of the difference in water levels at both ends of a link fall within the specified
“Damping Threshold”, the calculated flow is reduced in accordance with the equation below:
Q '  fd Q
Where f d is a flow reduction factor determined from a parabolic function of the change in stage and
Q ' is the reduced flow.
This parameter is used to help smooth out instabilities. Typically, when used, values range from
0.0001’ to 0.01’ and rarely should it exceed 0.1’. In general, the stability improves as the threshold
increases and it allows for larger computational time increments than would otherwise be possible.
However, it also increases head losses along the link for which it is used.
W '  f arf W
The area reduction factor is set by roughness zone, like the damping threshold. If you do not wish to
reduce the width, then set the area reduction factor to 1.0.
L = (2/3) x LA-B
W = ADIAMOND / L
If the “Edge Length Option” is set to “Manual”, then an “Edge Length Factor” must be set to a decimal
value greater than zero but less than or equal to 1. The resulting edge length and average width are
calculated as follows:
L = FEDGE (LA-B)
W = ADIAMOND / L
The manual edge length option and edge length factor can be used to help calibrate a model. As the
edge length factor is increased, the average width decreases and consequently, the overall flow of
water tends to slow down. In effect, attenuation of flows can be achieved by increasing the edge
length factor. This parameter has a similar effect as the peak rate factor for the unit hydrograph
method (the smaller the peak rate factor, the slower the water moves through a drainage basin).
Keep in mind that it is impossible to perfectly account for all the storage and the intricate flow paths
in natural systems with any 2D model. The edge length factor provides a mechanism to somewhat
offset the impact of those inherent inaccuracies related to the model setup.
If the edge length factor is set to 1, the average slope is set to:
The Successive Approximation with Over-Relaxation (SAOR) technique, the first time marching
method, employs an iterative solution and has an adaptive time step, meaning that the time step
changes throughout the simulation. However, the time step does not change spatially and a single
time step is used for the entire surface hydraulics portion of the model at a given point in time.
Consequently, the time step is typically driven by the node with the least amount of storage. The
method does lend itself well to parallel processing. Details of the SAOR method are described below
and is like the time marching scheme used in the EPA SWMM model.
The FIREBALL method is the second option for time marching and is a technique that is unique to
ICPR. Time steps vary not only in time, but also spatially. The potential speed gains are enormous
for large 2D models. Although parallel processing does take place with the FIREBALL method, it is
not as efficient as the SAOR method. Also, there is some additional overhead needed to set local
time steps in complex networks. But even with these caveats, the FIREBALL method can be up to 30
times faster than the SAOR method for large projects. Details of the method are described in
Section 17.4.1.2
In general, the SAOR method is more stable than the FIREBALL method. Consequently, tighter
stability criteria are required for the FIREBALL method. Mass balance checks are important with
both methods. Details of these time marching algorithms and specific input parameters for each
method are discussed in Section 17.4.1.
September 2017
Contents
20. Overland Flow Regions............................................................................................................... 5
   20.1 Creating an Overland Flow Region ........................................................................................ 5
      20.1.1 Create and Draw Region in ICPR ..................................................................................... 5
      20.1.2 Importing an Overland Flow Region ............................................................................... 7
   20.2 Overland Flow Region Manager ............................................................................................ 9
      20.2.1 Roughness Zones (required) ......................................................................................... 13
      20.2.2 Soil Zones (required) .................................................................................................... 13
      20.2.3 Land Cover Zones (required)......................................................................................... 13
      20.2.4 Rainfall Zones (optional) .............................................................................................. 14
      20.2.5 Mapped Basin Map Layer (optional) ............................................................................. 15
      20.2.6 Infiltration Method Zones (optional) ............................................................................ 16
      20.2.7 Reference ET Zones (optional) ...................................................................................... 16
      20.2.8 Crop Coefficient Zones (required when ET is included) ..................................................17
At least one overland flow region must be created to model 2D overland flow. Mapping features are
placed in the region and are used to construct the computational mesh. Generally, a single region is
used for most 2D projects but multiple regions can be used as a management tool for large complex
projects.
The purpose of this chapter is to describe how to create a region, and once it is created, how to
manage the various layers of information needed to parameterize the computational mesh.
A simple example is shown below where the region boundary is snapped to the reference grid at
several locations. The region polygon is closed by pressing “C” or with a right mouse click. Notice
that the region name (circled in red and designated “OFR-001”) appears on the tool bar located at
the top of the graphic view. This is the “active” region and any other 2D overland flow map features
created are assigned to the active region. A dropdown list of regions is available if more than one
region has been created, allowing you to change the active region.
A tree structure exists on the left side of the general tab that allows you to toggle various graphic
elements on and off as shown below left. Graphic elements associated with overland flow regions
are circled in red. Notice the name “OFR-001” appears directly below “Overland Flow Regions” in the
data tree. The region boundary can be toggled on and off by checking the box next to shape, directly
below “OFR-001”.
There are several ways to delete a region, but you need to be extremely
careful because not only will the region graphic be deleted, but all data
and features assigned to a region will also be deleted. The “Delete
Single” icon shown to the right allows you to pick a specific feature or
graphic element to delete.
Here are some important things to keep in mind when importing regions from other sources:
    1. You should use as few points as possible to define the region boundary without
       compromising accuracy. For example, there are ArcHydro tools available with
       ArcGIS that automatically delineate watershed boundaries from DEMs. These
       routines trace along the edges of the DEM cells and result in thousands of very
       short line segments (e.g. 5 feet). When ICPR generates the triangular mesh, a
       vertex is placed at every point along the region polygon. If the ArcHydro generated
       line work is not simplified, it will quickly make the ICPR overland flow model
       unwieldy and computationally inefficient.
   2. If you are using ArcGIS generated shapefiles, make sure you are exporting the file
      with a consistent projection system if you haven’t defined a CRS for the ICPR
      project. If you have defined a CRS, then ICPR will utilize the projection file that
      accompanies the shapefile to translate it into the ICPR CRS.
   3. The shapefile should be a polygon type and accompanied by a dbf file with a name
      field. Also, you should explode multi-part features.
   4. For DXF files, use the AutoCAD R12 format. You will need to know the layer names
      for line work and text. ICPR can import only lines, arcs and closed polylines for
      polygons. Make sure that the region boundary is a closed polygon – i.e. snap the
      ends. DXF files do not have projection files, so you must ensure that the spatial data
      is consistent with the CRS used in your ICPR project.
You can view the imported region boundary by first toggling off
the grid and then clicking the zoom extents icon as shown to
the right. This is equivalent to zooming to the extents of visible
entities. The color of the boundary and line width can be
adjusted using the “Graphic Element Properties Manager” as shown below. Also, shown below is
an imported region boundary.
One of the first things you might notice about the overland flow region manager is that you cannot
create a new region inside the manager. Regions can only be created graphically in ICPR in the
graphic view form or by importing a region boundary from a shape file or a DXF file. You can,
however, delete a region by clicking the delete button at the bottom of the form. Once again, if you
delete a region, you will simultaneously delete all data associated with it. So be very careful with the
delete button. The name of the region can be changed in the region manager, but the scenario
cannot be changed.
The minimum triangulation angle affects the shape and number of triangles. In general, as the angle
increases, so do the number of triangles. We have found a minimum angle of about 21 degrees to be
optimal in terms of number of triangles. But, 45 degrees generally produces better shaped triangles,
although many more of them. For example, the triangular meshes for 21- and 45-degree minimum
angles are shown below and generate 241 and 422 triangles, respectively.
ICPR goes through a triangle refinement process using the Delaunay method of triangulation to meet
the minimum angle constraint. Situations can occur where thousands of tiny triangles are created to
satisfy the minimum angle criteria. Consequently, a second constraint is used to stop the refinement
process. If, during the refinement process, a triangle area drops below a specified minimum
triangulation area, then the refinement process stops. A minimum triangulation area of about 150
square feet (14 square meters) works well in most cases.
After the diamond and honeycomb meshes have been created (using the Scenario Build), they are
rasterized for subsequent polygon processing with other mapping layers. The cell size data fields
establish the pixel size for this rasterization process. In general, these should be relatively small
numbers such as 1 foot as shown in the region manager on the previous page. But larger cell sizes
might be needed for larger projects due to memory issues. Just keep in mind that these cell sizes
must be even multiples of polygon map layer cell sizes. For example, if the cell size for a land cover
polygon map layer is set to 4 feet, then the diamond and honeycomb cell sizes would have to be
either 0.25, 0.50, 1, 2 or 4. Diamond and honeycomb cell sizes should be less than or equal to other
map layer cell sizes.
There are 2 surfaces (DEMs) that need to be set in the region manager: (1) the ground surface; and,
(2) the initial stage surface. If the overland flow plane is expected to be dry at the onset of the
simulation, then the ground surface DEM can be used for the initial stage surface. Otherwise a
separate DEM is required.
It is possible to use a single elevation for either the ground surface or initial stage surface by checking
the appropriate box and typing in an elevation. This is convenient for testing hypothetical situations
or specific features of the program, but is rarely used for actual conditions.
The following sections describe the various map layer types that are used for 2D overland flow
modeling. Note that you can right click in most of the data fields to select from a list of available map
layers.
Mapped Basin data forms must be completed for each of the basins
as shown below. The mapped basin layer is intersected with other
map layers such as soil zones, land cover zones and rainfall zones.
In most cases, a single infiltration method is used throughout a given region. To implement a single
method, check the box as shown below and select the method you propose to use.
Reference ET stations apply only if the “Include Evapotranspiration” box is checked as shown below.
It is possible to use a single reference ET station by checking the box as shown below and typing the
name of the station. A text file must be placed in the resource folder with the appropriate data.
September 2017
Contents
21. Overland Flow Graphic Elements ............................................................................................... 5
   21.1 Exclusion ............................................................................................................................... 7
   21.2 Extrusion ............................................................................................................................... 9
   21.3 Breakpoint ............................................................................................................................. 9
   21.4 Breakline ............................................................................................................................. 10
   21.5 Pond Control Volume .......................................................................................................... 13
   21.6 Channel Control Volume ..................................................................................................... 16
   21.7 Channel (Feature) .................................................................................................................17
   21.8 Cove .................................................................................................................................... 18
   21.9 1D Node Interface ............................................................................................................... 18
   21.10 Weir (Feature) .................................................................................................................... 20
      21.10.1 Drawing a Weir Feature ............................................................................................... 21
   21.11 Basin Interface Point .......................................................................................................... 23
   21.12 Basin Interface Line ........................................................................................................... 23
   21.13 Mapped Basin (Feature) ..................................................................................................... 24
   21.14 Boundary Stage Point ........................................................................................................ 25
   21.15 Boundary Stage Line.......................................................................................................... 25
   21.16 External Hydrograph Point ................................................................................................ 27
   21.17 External Hydrograph Line .................................................................................................. 28
   21.18 Simplification Feature ....................................................................................................... 28
The following dropdown list is taken from ICPR’s Graphic View and depicts the options specifically
related to 2D overland flow. It is possible to have multiple regions for a given project. Graphic
elements are always placed on the active region for the active scenario. Typically, only one scenario
is used for a project. However, if more than one is used, then you must set the active scenario in the
bottom right corner of the main ICPR window. Graphic elements are created by first setting the
“active graphic element” and then clicking the “create graphic element” icon. Instructions appear in
a prompt at the lower-left corner of the graphic view editor after clicking the create icon.
It is possible to create all the 2D overland flow graphic elements (except the weir feature) in a GIS
and then import them to ICPR via shapefiles or CSV files. To do this, expand “Feature Types” on the
data tree below “Overland Flow Regions” as shown below. Move the cursor over any of the features
(except “Weir (Feature)”) and right click. Then select “Import Shape(s) – Create New” and follow the
instructions. Note that there are other tools available, depending on the feature type. For example,
you can export a shapefile for most features by selecting “Generate Shape”.
Attribute tables are not included when importing and exporting shapefiles.
If a projection file is included with a shapefile and if a CRS is set for the ICPR project, the shapefile will
automatically be spatially translated into the ICPR CRS at the time of import. However, if you change
the ICPR CRS after importing the shapefile, the spatially data will not be re-projected to the new CRS.
The objective of the triangular mesh is to form a reasonable approximation of the ground surface.
More vertices in the mesh do not necessarily make for a more accurate or better model. You must
keep in mind that water moves along the edges of triangles and invert elevations of those edges are
based on ground elevations at the vertices as determined from the DEM. It is important to capture
important topographic features that affect the storage and movement of water. For example, there
is a large depression near the center of the figure shown below (light yellow) that has an east-to-west
drainage ditch as an outfall along its western shore. It is important to place triangle sides along the
bottom of that ditch to allow an outlet for the depression. Otherwise the depression would hold
more water numerically than it would naturally. Also, it is generally important to capture toe of slope
and top of bank around storage systems, local ridges and significant changes in slope.
As discussed in Section 12.1.2 of this document, time-stage nodes become outlets for the model
domain. A relationship between time and known stage elevation is established in the form of a table.
A similar approach is used for 2D overland flow regions, except boundary stages can be established
at either a point or along a line. ICPR has graphic elements for both of these.
Another type of boundary condition is the specification of known flow rates as a function of time.
These are called “external hydrographs” and for 2D overland flow regions, these can be specified at
a point or along a line.
The following sections describe each of the various 2D overland flow graphic elements.
21.1 Exclusion
Exclusions are closed polygons within an overland flow region. The area inside an exclusion graphic
element is “excluded” from the triangular mesh generation process. Consequently, there can be no
overland flow across an exclusion polygon. Furthermore, exclusions do not contribute stormwater
runoff to the region. Overland flow is permitted along its perimeter.
An example application of the exclusion feature is shown below. A wastewater effluent disposal
system is bermed around its perimeter. Stormwater runoff from adjacent areas must flow around
the outside of the berms and no discharge is expected from the site. An exclusion feature is created
along the top of the berm as shown below on the right.
The resulting triangular mesh is shown below and does not extend into the exclusion polygons, but
links are created along the perimeter, allowing flow along the berms but not across them.
Exclusions can share edges with pond and channel control volumes. Vertex points of the triangular
mesh are placed at each coordinate point of the exclusion and overland flow links are established
along the edges of the exclusion, except where those edges are shared with pond or channel control
volumes. Exclusions must be located completely inside the region boundary and not touch the
boundary.
21.2 Extrusion
Extrusions are very similar to exclusions. They are formed by closed polygons and no overland flow
is permitted to cross the polygon. Flow is permitted around the perimeter. The difference between
exclusions and extrusions is that
stormwater runoff is permitted from an
extrusion polygon. ICPR assumes the
extrusion is 100% impervious with no
initial abstraction. Flow is distributed
proportionately to each of the vertices
along the extrusion polygon based on a
line weighting. The area enclosed by the
extrusion polygon does not interact with
the 2D overland flow model.
Extrusions must be located completely inside the region boundary and not touch the boundary. No
other graphic element should intersect exclusions, although it is permissible to snap the endpoint of
a breakline to an exclusion vertex. It is also possible for extrusions to share sides with pond and
channel control volumes, but at least 2 vertices should be shared.
21.3 Breakpoint
Breakpoints are added for refinement of the triangular mesh and can be placed anywhere within an
overland flow region including inside pond and channel control volumes. However, breakpoints
placed inside exclusion and extrusion polygons and weir features are ignored. Vertices are
guaranteed at breakpoints. Honeycombs are formed around vertices and therefore a honeycomb is
formed around a breakpoint.
21.4 Breakline
Breaklines, like breakpoints, are used to refine the
triangular mesh. Although they can be placed
anywhere inside the overland flow region, they are
typically placed along low-lying collection paths and local ridgelines. Triangle vertices are
guaranteed at each coordinate point of the breakline. Furthermore, triangle edges, and
consequently overland flow links, are guaranteed along the breakline. A breakline can also be
placed parallel to a contour at significant slope changes. This tends to create overland flow links
generally perpendicular to the contours.
The following is an example of breaklines placed along the bottom of a tributary to a lake. The
breaklines are snapped at confluence points. Breakpoints are used near the top of bank to pick up
the change in grade along the side slopes of the channels. The resultant triangular mesh is also
shown along with down gradient arrows indicating the likely flow direction.
It is a good practice not to cross other 2D overland flow map features with breaklines such as pond
control volumes, channel control volumes, exclusions, etc.
The original vertices along the breakline shown below are numbered 11, 12, 13, 14 and 15. An
additional vertex was inserted between points 14 and 15 as part of the triangle refinement process.
Ground elevations at each original vertex are automatically obtained from the associated DEM.
Elevations for inserted vertices can either be obtained directly from the DEM (the default), or they
can be interpolated from ground elevations at the two adjacent original vertices. To interpolate,
double click the breakline you want to set to open its data form. And then check the “interpolate”
box. You also have the option to set a specific roughness zone for the entire breakline by checking
the “Override Roughness Zone” box and typing a name on the form and then adding that name to
the roughness lookup table.
There are ArcHydro tools that will find ridges and valleys from a DEM, both important in 2D
modeling. Although these can be imported to ICPR from a shapefile, typically the density of points
defining those lines is too great to be of any practical benefit without some thinning.
ICPR includes a “Simplify” tool that can be used to thin breaklines with high densities of points. The
tool is accessed by right clicking “Breakline” as shown below and then clicking “Simplify”. A selection
of breaklines is made and then the “Simplify Breaklines” dialog box opens as shown below. Typically,
“Make Interpolatable” and “Preserve Intersections” are checked and a “Max Vertex Spacing is
specified. The make interpolatable option will activate the “Interpolate” check box on the “Overland
Flow Breakline Feature Data” form described above.
 The black lines on the left are the original breaklines from ArcHydro. The heavy blue lines on the
right are the thinned out breaklines using the “Simplify” tool in ICPR.
Another example is shown below where breaklines are used to characterize the terrain for a relatively
steep area. In general, the breaklines are placed perpendicular to the contours from uphill to
downhill.
Pond control volumes are “attached” to a 1D node. The 1D node (stage/area node type) must be
created before the pond control volume is drawn. It is important that the largest area in the stage-
area table not exceed the area of the pond control volume polygon. For example, if the pond control
volume is placed roughly at the 40-foot contour and encloses an area of 25 acres, then the stage area
table should have a point at elevation 40 feet with a corresponding area of 25 acres.
Pond control volumes can share common sides with other pond control volumes and graphical
elements, but those sides must match exactly point-for-point. An error will occur if two control
volumes (pond or channel) touch at only a single point. Pond control volumes can also share a common
edge with the region boundary, but they should never cross over the region boundary.
There is an “Interpolate” option available for pond control volumes that works the same as the
interpolate option for breaklines. When the “interpolate” option is unchecked, elevations for inserted
vertices along the perimeter of the pond control volume are obtained directly from the DEM (the
default). If the “interpolate” option is checked, then elevations for inserted vertices are interpolated
from ground elevations at the two adjacent original vertices. You can open the pond control volume
data form by double clicking on the graphic element or by clicking “2D Features > Overland Flow >
Pond Control Volumes”.
Breakpoints can be placed inside a pond control volume as shown below. A honeycomb is created at
each breakpoint and allows percolation to “climb” up the sides of the pond as water levels increase,
exposing different soil types.
A stage-area table is required for all 1D nodes that have a pond control volume attached to them.
There is a tool in ICPR that will automatically extract stage-area tables for any or all pond control
volumes from a ground surface DEM. Right click on the pond control volume feature and select the
“Generate Stage/Area Table” option as shown below. A prompt for the selection set of pond control
volumes appears at the bottom of the graphic view. The “Generate Stage/Area of Nodes” dialog box
appears where you specify a surface DEM and stage spacing (vertical increment in feet or meters).
The stage-area tables for corresponding nodes are automatically updated.
Always keep in mind that the stage-area table is only as good as the DEM. If the DEM was derived
from standard LiDAR, bathymetry below the waterline will likely not be available, which, is an
important consideration for continuous simulation modeling.
It is important to understand that every vertex along the channel control volume becomes a point
where water can move between the 2D mesh and the 1D system. Consequently, care should be taken
to include local high and low points from the ground DEM.
Adjacent channel control volumes sharing a common side should match exactly along that common
side. An error will occur if two control volumes (pond or channel) touch at only a single point. You can
use the “trace” feature while drawing the polygons to accomplish this. Any gaps between the
adjacent control volumes will be filled with tiny triangles that can lead to other problems.
Channel control volumes can share common sides with pond control volumes and other graphical
elements, but those sides must match exactly point-for-point. An error will occur if two control
volumes (pond or channel) touch at only a single point. Channel control volumes can also share a
common edge with the region boundary, but they should never cross over the region boundary.
There is an “Interpolate” option available for channel control volumes that works the same as the
interpolate option for breaklines and pond control volumes. When the “interpolate” option is
unchecked, elevations for inserted vertices along the perimeter of the channel control volume are
obtained directly from the DEM (the default). If the “interpolate” option is checked, then elevations
for inserted vertices are interpolated from ground elevations at the two adjacent original vertices.
You can open the channel control volume data form by double clicking on its graphic element or by
clicking “2D Features > Overland Flow > Channel Control Volumes”.
Like pond control volumes, the triangular mesh is extended into the channel control volume, but only
for purposes of constructing the honeycomb. Overland flow links are not included inside the control
volume or along the edges. Vertices are guaranteed at each coordinate point along the outer edges
of the control volume.
Breakpoints and breaklines are permitted inside the control volume to further refine the honeycomb.
However, breaklines should not cross channel control volumes.
21.8 Cove
Coves are “backwater” areas along 1D
channel links that are not appropriate for 2D
modeling and not significant enough to
include in the 1D modeling effort. It is
assumed that the water surface inside the
cove behaves as a level pool at an elevation
equal to the connection point along the 1D
channel. Coves “live” inside channel control
volumes. Consequently, they are specified in
terms of a starting index and ending index of
points along the control volume, plus the
connection point. The numeric order of each
point along the channel control volume will
appear when selecting the starting index for
the cove. Always select the lower index
number for the starting index and the higher
index number for the ending index. The water
surface inside the cove is assumed to be flat
at an elevation interpolated from the water surface along the 1D channel link at the cove
connection point. The wetted surface area inside the cove is not automatically included in the
numerical computations. It should be added to the stage/area node associated with the respective
channel control volume.
To illustrate this concept, consider the figure shown below. A storm sewer system includes surface
inlets, catch basins/manholes, and pipes. A “1D Node Interface” graphic element is placed at each
inlet (shown as a black X). Catch basins and manholes are modeled as standard 1D stage/area node
types (shown as solid blue circles). 1D links are used to connect a 1D node interface to any other 1D
node in the model. For example, the storm inlets (black X’s) are connected to the catch
basins/manholes (blue circles) with weir links. 2D surface flow moves to the inlets, drops through the
weir into the catch basin and then through the pipe system. Since drop structures are composite
links consisting of a weir in series with a pipe, they can be used at upstream terminus ends of the
storm sewer system to connect a 1D node interface feature to a stage-area node.
The initial stage at 1D node interfaces are taken directly from the ground surface DEM. However,
you can override the default stage in the overland flow 1D node interface data form. Either double
click the 1D node interface graphic element or click “2D Features > Overland Flow > 1D Node
Interface” to open the data form. Check the “Override Initial Stage” box and type in the initial stage
you wish to use. It is important to use this option when you are modeling underground systems, like
a storm sewer system below a parking lot. Otherwise the initial stage will be based on the elevation
of the parking lot, resulting in substantial head on the pipe system at the start of any simulation and
high initial flows.
An irregular cross section is created for each 1D weir (created at each vertex along the centerline).
The cross sections consist of either 2 coordinate pairs for the ends of the weir feature, or 3 coordinate
pairs for the interior. The elevations at the vertices, by default, are taken from the ground surface
DEM – elevations at cross section points between the vertices are interpolated from the adjacent
vertices.
A vertical offset from the DEM elevations can be specified by opening the data form for the overland
flow weir feature (double click on it or click “2D Features > Overland Flow > Weirs”). The elevation
calculation method shown below allows you to set either a “Vertical Offset” (i.e. from the DEM) or a
“User Specified Elevation”. If the vertical offset method (the default method) is chosen, then the
vertical offset distance (f, m) must be specified. In the example below, the offset is set to zero feet,
so that the weir follows the DEM. The weir type and weir discharge coefficient are also set on the
overland flow weir feature data form.
If the water level at any vertex along the weir offsets exceeds its respective weir invert elevation, then
flow is possible across that 1D weir and water is moved across the weir at that location.
The weir type and weir discharge coefficient must be set. This is accomplished by opening the “Weir
(Feature)” data form. The type is set to “Broad Crested, Vertical” and the discharge coefficient to 2.8.
Once you have placed the basin interface point, you need to identify the traditional basin you want
assigned to that point and the proportion of flow to be discharged to the 2D mesh. This is done by
basin interface point feature data form and filling out the appropriate parameters as shown above.
Note that a “1” is used to assign 100% of the basin flow.
If the proportion of flow is less than 1, then the basin flow is split accordingly between the basin
interface point and the 1D node that the basin is assigned to in the basin data form. For example,
assume that “Basin A” in the example above is assigned to stage/area node “ZZ” and that the
proportion of total flow parameter is set to 0.75. Then 75% of the runoff from “Basin A” will be
delivered to overland flow basin interface point “OFBPT-001” and 25% will be delivered to node “ZZ”.
Once you have placed the basin interface line, you need to identify the traditional basin you want
assigned along the line and the proportion of flow to be discharged to the 2D mesh. The example
shown below assigns 80% of the flow from Basin A to the basin interface line (the remaining 20% is
delivered to the node assigned to “Basin A” in its data form). The flow is then distributed along the
line proportionally based on length. The proportional length assigned to a particular vertex is half
the distance to adjacent vertices divided by the total length of the line interface.
ICPR allows 2D overland flow links along the edges of the mapped basin feature. Vertices are
guaranteed at each coordinate along the feature. Pond control volumes and channel control
volumes can be placed inside a mapped basin feature as well as straddle the edges of it.
An example is shown below where two boundary stage line features are included at the eastern end
of the region bounday. Historical stage records for the large river east of the region boundary are
used as a boundary condition.
Once the boundary stage line has been placed, the table names at each end of the line that contain
the time-stage data (boundary stage lookup tables) must be entered. A dropdown list appears if you
right click in this data field. Linear interpolation based on distance is used between the two
endpoints. It is important that the first table correspond to the first point entered on the boundary
stage line and the second table correspond to the last point. This can be determined by using the
edit polyline tool. Click the edit polyline icon then click the boundary line feature. The points are
numbered in the order that they were entered. The table for “Boundary Stage 1” corresponds to
polyline point “0” and “Boundary Stage 2” corresponds to point “11” in the example shown below.
the case and depends on the particular set of circumstances. Also, friction and other losses are not
included inside the simplification feature.
Each time a simplification feature is created, it is active by default. Individual features can be
deactivated by opening its data form (click “2D Features > Overland Flow > Simplifications”) and
uncheck the “Active” box (shown below left).
An option is available when you execute a simulation as to whether simplifications will be included.
A box labeled “Activate Simplifications” must be checked (shown in yellow below right) to include all
“active” simplifications in a particular simplification.
September 2017
Contents
22. Mesh Construction and Parameterization .................................................................................. 5
It is important that the raster view be turned off for all polygon
map layers that are to be included in the build and animations must be turned off. Otherwise errors
will occur.
To “build” a scenario, open the scenario manager, select the scenario you wish to build, and click
the build button in the lower left corner of the simulation manager as shown to the left.
The scenario build dialog box appears after clicking the build button. There are just 2 options: (1)
Check Intersections; and, (2) Generate Build XML. The check intersections option is for situations
like a breakline crossing a pond control volume. If you are certain you don’t have situations like this
then it is better to leave the “Check
Intersections” unchecked because the
build will be faster. If you check this
box and it intersections are found,
then ICPR will automatically insert a
new vertex at the intersection point.
You can almost always leave
“Generate Build XML” unchecked.
This is used occasionally for
debugging purposes, but will slow the
build process down substantially for
large projects.
Click the “Build” button to proceed. You may get the following message if a scenario build was
previously performed.
Messages appear as the build progresses, with the last message being “Build Complete” as shown
below. The build process can take just a few seconds or several hours, depending on the complexity
of the project.
Any change to 2D features including parameters specified in their data forms (except simplifications)
or to the region manager specifications require another build. For example, if you add or delete a
single break point you will need to rebuild the scenario before executing. Or, if you change the
roughness zone in the region manager, you will need to rebuild.
The “Status” button on the scenario manager indicates the version number of ICPR that was used to
construct the meshes and the log button provides details about a specific scenario build.
Once a scenario has been built, the “build” version of the triangular, diamond and honeycomb
meshes are available for viewing and can be toggled on and off from the data tree of the general tab
in the Graphic View. Furthermore, each of these meshes can be exported to a DXF file by right
clicking the preprocess label or build label. The DXF files can then be imported to GIS or CAD
programs.
After a scenario build is completed, there are tools to query specific locations on a mesh for
parameterization information. You must first turn on the triangulation “build” mesh. Click the “2D
Node Info” icon shown below; then select a triangle vertex (either overland flow or groundwater), or
window around a group of them. For surface nodes, a breakdown of basin polygons is provided along
with their various attributes. An example is shown below.
The 2D Link Info tool can be used to query triangle edges for 2D overland flow meshes.
September 2017
Contents
23. Overland Flow Example, Suburban Setting ................................................................................ 5
   23.1 Background ........................................................................................................................... 5
      23.1.1 Acknowledgements ........................................................................................................ 5
      23.1.2 Open Project ................................................................................................................... 6
      23.1.3 Basic Workflow ............................................................................................................... 8
   23.2 Base Data .............................................................................................................................. 8
      23.2.1 Background Images ........................................................................................................ 8
      23.2.2 Ground Surface DEMs .................................................................................................... 9
      23.2.3 Map Layers ................................................................................................................... 10
      23.2.4 Lookup Tables .............................................................................................................. 12
   23.3 1D Model Setup ................................................................................................................... 14
      23.3.1 1D Nodes (Stage/Area and Time/Stage Nodes) ............................................................. 14
      23.3.2 1D Node Interface Points .............................................................................................. 14
      23.3.3 Links ............................................................................................................................. 16
      23.3.4 Basins ............................................................................................................................17
      23.3.5 Boundary Conditions .....................................................................................................17
   23.4 2D Model Setup................................................................................................................... 18
      23.4.1 Overland Flow Region Boundary................................................................................... 19
      23.4.2 Pond Control Volumes .................................................................................................. 21
      23.4.3 Channel Control Volumes ............................................................................................. 21
      23.4.4 Channel Interpolation Feature ...................................................................................... 23
      23.4.5 Extrusions ..................................................................................................................... 23
      23.4.6 Breaklines ..................................................................................................................... 24
      23.4.7 Breakpoints................................................................................................................... 25
      23.4.8 Boundary Stage Line .................................................................................................... 25
   23.5 Overland Flow Region Manager .......................................................................................... 27
   23.6 The Scenario Build (Mesh Construction) .............................................................................. 29
   23.7 Simulation Control and Execution ....................................................................................... 31
      23.7.1 General Tab................................................................................................................... 31
      23.7.2 Output Increments........................................................................................................ 32
The purpose of this example is to describe the 2D model setup procedure in ICPR, including an
interface with 1D drainage components such as underground storm sewers, open channel ditches
and retention/detention ponds.
23.1.1 Acknowledgements
The lead consultant and Engineer-of-Record for this project was Singhofen & Associates, Inc. (“SAI”)
of Orlando, Florida. SAI provided all base information for this investigation to Streamline
Technologies, Inc. including but not limited to: 1-foot DEMs for existing conditions and various
alternative conditions; shapefiles for land cover/impervious areas, soils and underground
infrastructure; and time-stage data for model boundary conditions. The City of Tallahassee provided
historical rainfall data and stream gage data and complaint files for the study area as well as original
LiDAR and various base GIS layers such as parcel maps.
The coordinate refence system for this project is “NAD83(HARN) / Florida North (ftUS). You can
verify this by hovering over the CRS in the lower right corner of the main ICPR window.
Open the Graphic View, maximize it and apply the following “Graphic View Port Settings”.
You should see something like the following. This is the existing condition 1D nodal network and
includes the storm sewer system, open channel system and a few stormwater ponds. The 1D model
setup is discussed in Section 23.3. A “Parcel Map” layer is toggled on and used for reference
purposes only.
The background images can be toggled on and off under the general tab of the graphic view as shown
below.
The map layers were imported from shapefiles and can be viewed in vector form by toggling on their
respective polylines as shown below. Do not turn the labels on for the “Impervious Zones” or the
“Parcels” …it will be very slow because of the extremely large number of text labels.
You can view the raster version of the map layer on the “Raster” panel of the Graphic View as shown
below. The zone description at the cursor location appears in the lower right corner of the Graphic
View.
The complete set of CNs used in this example are shown below.
computational mesh to the 1D nodal network. It is called a “1D Node Interface”. These are placed at
every storm inlet.
The 1D node interface points appear as X’s as shown below. A weir link is connected “from” the 1D
node interface point (“N042.1VS”) at street level and “to” the stage/area node (“N042VS”) at the
bottom of the catch basin. Pipe links are connected from and to the stage/area nodes below the
ground. Later, during the mesh construction process, a triangle vertex (2D node) is placed at 1D node
interface point.
The throat of the storm inlet is below the street elevation and is set in the weir data form as its invert
elevation. However, ICPR uses the street elevation (obtained from the DEM) at the 1D node interface
as the initial stage at that location unless an adjustment is made. The initial stage should be set at
the throat elevation. The adjustment is made in the 1D node interface data form.
The data form for the 1D node interface point (“N042.1VS”) is shown below. The weir data form for
link “W042.1VS” is also shown. Notice that the “Override Initial Stage” option is checked and that
the initial stage is set to 110.38 feet, which corresponds to the weir invert elevation. The warning
stage is also set to 110.38 feet in this example.
The 1D node interface point data forms can be accessed from the menu system as follows. There are
69 1D node interfaces in this example.
23.3.3 Links
There are 155 1D links in this model including channels, pipes, weirs, drop structures and a rating
curve. The rating curve link represents a bridge under the CSX railroad at the Park Avenue Ditch
located in the southeast corner of the study area. The bridge is hydraulically represented as a family
of rating curves reflecting a relationship between headwater elevation, tailwater elevation and flow
rate. These were obtained from an older ICPR3 model of the Park Avenue Ditch system. Irregular
channel cross sections are used to describe the geometry for the various channel links. These were
field surveyed.
Weirs are used to model storm inlet hydraulics as previously mentioned. Consider the sketch shown
below. The catch basin below ground is modeled as a stage/area node and pipes are connected to it
and from it. Flow on the street moves overland and drops into the inlet and catch basin. The inlet in
the example below is modeled as a vertical weir with a 0.5-foot (6 inches) vertical opening that is 9
feet wide. This link behaves as a weir until the inlet is completely submerged and then it transitions
to orifice flow.
Street flow in this example is modeled as 2D overland flow. Consequently, a standard 1D stage/area
node cannot be used in the street. A special 2D graphical element called a “1D node Interface” is
needed as discussed in the previous section.
23.3.4 Basins
Since this project is modeled as 2D overland flow, no traditional basins are required or used in this
example.
example. Both are along the Park Avenue Ditch. Two boundary stage sets are used in this example
as shown below – one for the 25-year storm and the other for the 100-year storm. To view the various
tables within a given set, open the “Boundary Stage” tab. Data for these tables were obtained from
a regional model of the Park Avenue Ditch.
The boundary stage tables are referenced on the node data form as shown below.
The following dropdown list is taken from ICPR’s Graphic View and depicts the options specifically
related to 2D overland flow. Graphic elements are created by first setting the “active graphic
element” and then clicking the “create graphic element” icon. Instructions appear in a prompt at the
lower-left corner of the Graphic View after clicking the create icon.
        The overland flow region boundary must be created first before any graphical elements
             are added. Graphical elements should never be drawn outside of their region.
There are two primary ways to create an overland flow region. The first is to draw it in ICPR and the
second is to import either a shapefile or a DXF file.
The Overland Flow (OF) Region Boundary is shown below in red, superimposed with the parcel map
layer.
Click the “Entity ID” icon and then click the region boundary. The perimeter length (18,978 feet) and
area (283 acres) of the polygon appear in an information window.
Pond control volumes can be toggled on and off under the “Feature Types” as shown below.
An example channel control volume is shown below. Note that channel control volumes can and
normally do share a common side. They can also share common sides with pond control volumes and
region boundaries. It is important that common edges match exactly without any gaps and that at
least 2 points are placed on common edges. Notice also that channel control volumes extend
approximately halfway upstream and downstream along any 1D channel links connected to or from
the respective node.
Channel control volumes should be approximately as wide as the cross section used for the 1D
channel links. The cross sections should not extend an appreciable distance beyond the channel
control volume and into the 2D overland flow area, otherwise storage would be double accounted.
Channel control volumes can be toggled on and off under the “Feature Types” as shown below.
23.4.5 Extrusions
Extrusions are polygons and are used to model obstructions to overland flow, like buildings. They
are treated as 100% impervious and runoff from an extrusion is distributed along the perimeter of
the extrusion based on a line weighting. Although it is often possible to obtain a GIS layer with
building footprints, they usually need to be simplified before importing to ICPR to reduce the number
of vertices. Always keep in mind that a triangle vertex will be placed at every point in the extrusion
polygon.
23.4.6 Breaklines
Breaklines are polylines used to characterize the terrain. Triangle edges are guaranteed along
breaklines. Recall that water flows along the triangle edges in ICPR. Breaklines are usually placed
along local valleys to define flow paths. They are also placed along local ridges to define drainage
divides.
Several of the breaklines used in this project are shown below. They are used along the roadways and
between houses.
23.4.7 Breakpoints
A triangle vertex is guaranteed at each breakpoint. Like breaklines, they are used to characterize the
terrain and to refine the computational mesh.
A single boundary stage line is used along the eastern end of the study area.
corner of the region manager form. This is useful for evaluating triangle densities based on map
features prior to execution of the simulation.
Leave “Check Intersections” and “Generate Honeycomb” unchecked. Click the “Build” button at the
lower left corner of the “Preprocess” window. It will take a minute or two to construct the mesh.
2D feature such that the “short” triangle side is eliminated. For example, if you happen to have a
breakpoint very close to a breakline, you might want to delete the breakpoint.
When the build is complete, click the “Exit” button and then close the scenario manager.
                                        1                       0.01
                                        2                       0.02
                                        3                       0.04
                                        4                       0.08
                                        5                       0.16
                                        6                       0.32
                                        7                       0.64
                                        8                       1.28
                                        9                       2.56
The maximum error percent for is a fraction of a percent (about 0.23%) which is not an issue.
Set the “Sleep Rate” to 0.1 sec (#1), click the “Rewind”
button (#2) and the “Play” button (#3) to animate the
flood depths. The sleep rate displays each output
increment at the designated time interval.
Click the “Power” button if it’s not already turned on, then click the “End” button.
Move the cursor anywhere over the animation and right click. The “Animation Export Form” appears.
Set the “File Root Name” to “Max_Elev_100yr”, set the “DEM Cell Size” to 5 feet and check the
“Generate DEM Hdr/Flt File Pair” box. Then, click OK.
A notice appears when the operation is complete. Click OK. A DEM has been created and placed in
the “Surfaces” folder for the project.
Open the “Surface Manager” and click the “Batch Import” button.
Close the surface manager. Zoom into the area shown below and toggle the breaklines on. Click the
“Display Profile” icon and then select the breakline that is highlight below. This is along the centerline
of the roadway.
Check both surfaces and then click OK. The 100-year water surface profile is shown below
superimposed with the ground surface profile. There is approximately 3 feet of flooding.
Make sure the “Power” is on and then “Go To Relative Time” 4 hours.
Try playing an animation from the beginning with the sleep rate set to 0.1 seconds.
Open the “Report” panel of the Graphic View. “Quick Charts” are in the middle of the panel. Set the
“Item Type” to “2D Nodes” and the “Chart Type” to “Stage”. Click the “Select/Display” button and
then move the cursor over the 1D node interface as shown below and click.
The discharge hydrographs for the 2 storms representing the total inflow to the 3 selected nodes is
shown below. They peak at about 47 cfs and 76 cfs for the 25-year and 100-year storms, respectively.
September 2017
Contents
24. 2D Groundwater, Concepts and Theory ..................................................................................... 5
   24.1 Basic Concepts ...................................................................................................................... 5
   24.2 Interaction with the Vadose Zone ......................................................................................... 7
      24.2.1 Groundwater Interaction with the Green-Ampt Method................................................. 8
      24.2.2 Groundwater Interaction with Vertical Layers .............................................................. 11
   24.3 Groundwater Interactions with the Surface ......................................................................... 11
      24.3.1 Surface Water – Groundwater Interactions with Mapped Basins................................... 14
      24.3.2 Surface Water – Groundwater Interactions with Pond Control Volumes ....................... 14
      24.3.3 Surface Water – Groundwater Interactions with Channel Control Volumes .................. 15
      24.3.4 Surface Water – Groundwater Interactions with 2D Overland Flow Nodes ................... 15
   24.4 Groundwater Interaction Below the Confining Layer (Leakage) .......................................... 15
Conceptually, ICPR models saturated horizontal flow in the surficial aquifer system above a confining
layer. Heads (elevations) are calculated at the nodes. Spatially and temporally variable leakage
through the confining layer can be included in the model.
Like 2D overland flow, a triangular computational mesh is formed from graphic elements and then a
honeycomb mesh is derived from the triangles. However, honeycombs are formed not only around
the triangle vertices, but also the mid-nodes as shown below.
The triangle mesh is intersected with porosity zone and conductivity zone map layers to determine
area weighted average porosities and conductivities by triangle. The honeycomb mesh is intersected
with a leakage zone map layer to determine average leakage coefficient values by individual
honeycomb. Triangle nodes (vertices and mid-nodes) are intersected with various DEMs to
determine ground, confining layer, initial water table and potentiometric elevations needed for the
computations.
The 2D groundwater module in ICPR can interact the surface in several ways. Infiltration into the
unsaturated portion of the soil column can move vertically downward and “recharge” the surficial
aquifer. Seepage can flow into the groundwater system from surface water bodies and from surface
water bodies into the groundwater system. For example, a rapidly rising open channel system might
initially seep from the channel into the adjacent groundwater system, but when water levels in the
channel recede, seepage can flow from the adjacent groundwater system into the channel. Leakage
across a confining layer can also be incorporated into the groundwater computations. These various
interactions are described in detail in the following sections.
In addition to using either the Green-Ampt method or vertical layers for rainfall excess computations,
an overland flow region is required to connect surface hydrology to the groundwater module.
Manual basins do not interact with the groundwater module. Mapped basins inside an overland flow
region and 2D overland flow can both interact with the groundwater module.
             1.   surface honeycomb ID
             2.   groundwater honeycomb ID
             3.   soil type
             4.   land cover type
             5.   crop coefficient type
             6.   rainfall station
             7.   ET station
Rainfall excess is delivered to the surface node associated with the surface honeycomb ID. And,
groundwater recharge is delivered to the groundwater node associated with the groundwater
honeycomb ID. However, groundwater recharge assigned to a groundwater triangle vertex is
redistributed proportionally to the mid-nodes (as of release v4.03.02). We have found that
redistributing to the mid-nodes avoids abrupt spikes at the vertices and fewer instability issues.
The groundwater honeycomb is also intersected with mapped basins. The surface node attribute for
the polygon soil cylinder becomes the 1D node assigned to the corresponding basin instead of the
surface honeycomb ID.
Various lookup tables are used in conjunction with the soil, land cover and crop coefficient attributes
to determine infiltration, evapotranspiration, rainfall excess, unsaturated flow in the soil column, and
recharge to the water table.
where,
                  2
         n  3
                  
                 pore size index
The recharge rate delivered to the groundwater model for a given water table elevation is the
unsaturated conductivity for the transmission zone multiplied by the sub-polygon area (i.e. the soil
cylinder area). The rate is converted to a volume based on the hydrology computational time
increment, and the volumes are aggregated for all sub-polygons assigned to the same groundwater
node and delivered at the next groundwater computational increment.
As the water table moves up or down, a recharge correction is calculated that reconciles the
difference between the current moisture content as tracked by the Green-Ampt method and the
specified fillable porosity in the groundwater model. The recharge and recharge correction volumes
are aggregated for all sub-polygons assigned to a groundwater node and for each hydrology time
increment within a given groundwater time increment. These volumes are delivered to the
respective groundwater node at the next groundwater time increment.
It is possible to incorporate perched water tables with the Green-Ampt method in conjunction with
the groundwater model. Consider the sketch below where a localized perched water table exists due
to a hard pan layer. If a specific soil zone is set up for hard pan areas, then the “allow recharge” option
for that zone can be set to “No”. If it is set to “No”, then any sub-polygon soil cylinders in that zone
will not interact with the groundwater model directly. Instead, once the soil column becomes
saturated, rainfall excess moves overland for 2D surface models and can then interact with other soil
cylinders that allow recharge.
If the “Refined” option is selected in the Green-Ampt data form, then the soil column is vertically
discretized into a specified number of cells for the user defined layer thickness. Each cell has the
same soil properties. Once discretized, ICPR uses the vertical layers methodology described in
Section 7.5 and Section 24.2.2.
            In general, the “unrefined” Green-Ampt method is used for higher water table
           conditions (e.g season high water table within 6 feet of the ground surface) and
                    the “refined” method is used for deep water table conditions.
There are two things that must be considered when the water table intercepts the ground surface.
The first is related to storage and the second is related to seepage rates. A change in porosity occurs
above the ground surface which affects storage characteristics. Fillable porosity lookup tables are
discussed in Section 7.3. A distinction is made in that lookup table between above ground porosity
and below ground porosity. If the water table intercepts the ground surface at a surface node that is
inundated (e.g. a lake), that groundwater node is converted to a known head condition with its head
dictated by the surface node. The above ground porosity is used at that node. Once all known head
nodes have been set, an area weighted average porosity is calculated for each triangle before
proceeding with the groundwater computations. The weightings are set to 1/12 th for the vertices and
3/12th for the mid-nodes. It is possible to have some nodes above the ground and others below the
ground for a given triangle, and that is factored into the averaging.
A more accurate representation of the storage can be obtained by refining the mesh along the edge
of the pond like that shown below. Notice how smaller triangles straddle the edge of the pond (dark
blue line). The penalty for the increased accuracy is a more complex groundwater model and the
associated extra computational effort. As the modeler, you must decide if the extra accuracy is
warranted. A similar situation occurs along open channels.
Seepage as related to ICPR is the direct exchange of water between the groundwater system and the
surface system without passing through the vadose zone. Two primary types of seepage are
calculated and tracked by ICPR:
The first type, seepage at a known head node, occurs at all user specified boundary stage nodes. But,
it can also occur when the water table is above the ground surface and the corresponding surface
node is inundated. For example, if a groundwater node coincides with a lake, then that groundwater
node is forced to a known head condition and the elevation is dictated by the lake. Seepage rates
are calculated as described in Section D.7 and Equation D.31. In terms of mass balance, the “above
ground” porosity is factored in for that portion of the water table above the ground surface.
The second type, seepage at an unknown head groundwater node, typically occurs along a sloping
ground surface like a river bank or a seepage face on a hill. In these cases, the groundwater model
calculates a water table elevation above the ground as if it were still in the soil column, even though
there is nothing on the surface to physically support that elevation. In other words, the water flows
overland to another location farther downstream and does not pond on the surface. In this situation,
ICPR pulls the groundwater elevation down to the ground surface and simultaneously sends a volume
of water to the corresponding surface node equal to the honeycomb area multiplied by the depth
above the ground and the average “below ground” porosity of the honeycomb. The following
seepage rate is applied to the corresponding surface node for a full groundwater time increment.
QSeepage   h1  h2   ( A)    / dt gw
where,
ICPR also tracks “undelivered” seepage. This can occur for both seepage types described above if
the groundwater node is located outside of an overland flow region. It can also occur when the user
specifies a known head condition within an overland flow region, but below the ground surface.
When the groundwater table exceeds the ground surface, seepage is calculated as described in the
previous section and sent directly to the surface node. The groundwater elevation at that node is
pulled back down to the ground surface elevation. Groundwater never exceeds the ground surface
inside a mapped basin.
groundwater node when the soil column is saturated and the surface is inundated. The known head
condition is based on the level pool surface water elevation.
    1. no leakage
    2. leakage based on a leakance value
    3. leakage based on Darcy’s equation
QLeakage  ( L)   h1  h2   ( A)
where,
         L        is a leakance value expressed as a flow rate (f3s-1, m3s-1) per foot (meter) of head per
                  unit area (f2, m2). The units for the leakage value become “per second” (s-1).
         h1 , h2   are the water table and potentiometric elevations, respectively (f, m). If the
                   potentiometric elevation drops below the top of the confining layer, then h2 is set to
                   the top of the confining layer
                            h  h  
         QLeakage  ( K )   1 2   ( A)
                               t     
where,
September 2017
Contents
25. Groundwater Regions................................................................................................................. 5
   25.1 Creating a Groundwater Region ............................................................................................ 5
      25.1.1 Create and Draw Region in ICPR ..................................................................................... 5
      25.1.2 Importing a Groundwater Region ................................................................................... 7
   25.2 Groundwater Region Manager .............................................................................................. 7
      25.2.1 Surface DEMs ................................................................................................................. 9
      25.2.2 Map Layers ................................................................................................................... 11
ICPR does include parallel processing and surface hydrology and routing have been optimized to take
advantage of multi-core processors. The groundwater module on the other hand is finite element
based which does not lend itself directly to parallel processing. Decomposition of the mesh into
smaller meshes would be required and this is not done automatically (as of this writing) in the
program. However, it is possible to create multiple independent groundwater regions within a given
project and ICPR will process these regions simultaneously if a multi-core processor is available and
invoked at simulation time. For example, two separate groundwater regions might be created with
a common edge along the centerline of a river. Both regions would interact with the river and share
the same boundary condition, but they would otherwise be independent of one another. ICPR would
process the two regions simultaneously if multiple processors are available, thus greatly speeding up
the calculations.
existing polyline. If you would like a groundwater region to exactly match an overland flow region,
you can press the “X” and then simply click on the overland flow region to copy the entire polygon.
“O” allows you to draw a geometric shape such as a circle or rectangle.
An example groundwater region is shown below. A tree structure exists on the left side of the general
tab that allows you to toggle various graphic elements on and off. Graphic elements associated with
groundwater regions are outlined with a red rectangle. Notice the name “GWR-001” appears directly
below “Groundwater Regions” in the tree structure. The region boundary can be toggled on and off
by checking the box next to shape, directly below “GWR-001”.
Vertical walls are assumed around the perimeter of the region boundary unless other
provisions are made (e.g. incorporate a boundary stage line graphic element along a portion
of the region boundary).
You cannot create a new region inside the manager. Regions can only be created graphically in ICPR
in the graphic view form or by importing a region boundary from a shapefile or a DXF file as previously
described. You can, however, delete a region by clicking the delete button at the bottom of the form.
Once again, if you delete a region, you simultaneously delete all data associated with it. So be very
careful with the delete button.
The name of the region can be changed in the region manager, but the scenario it resides in cannot
be changed. The minimum triangulation angle affects the shape and number of triangles. In general,
as the angle increases, so do the number of triangles. Although a minimum angle of about 21 degrees
is optimal in terms of minimizing the number of triangles, a 45-degree or 60-degree minimum
provides better shaped triangles.
ICPR goes through a triangle refinement process using the Delaunay method of triangulation to meet
the minimum angle constraint. If left unconstrained, situations can occur where thousands of tiny
triangles are created to satisfy the minimum angle criteria. Consequently, a second constraint is used
to stop the refinement process. If, during the refinement process, a triangle area drops below a
specified minimum triangulation area, then the refinement process stops. A minimum triangulation
area of 150 square feet works well in most cases.
A preliminary triangle mesh can be constructed by clicking the “Preprocess” button at the lower-left
corner of the region manager form. This is useful for evaluating triangle densities based on map
features prior to execution of the simulation.
A tool is available to help in your evaluation of the preliminary triangular mesh in the “Search” tab of
the graphic view as previously discussed in Section 20.2.
After the groundwater honeycomb mesh has been created, it is automatically rasterized for
subsequent polygon processing with other map layers. The cell size data field establishes the pixel
size for this rasterization process. In general, it should be a relatively small number such as 1 foot as
shown. But larger cell sizes might be needed for larger projects due to memory issues. Just keep in
mind that these cell sizes must be even multiples of polygon map layer cell sizes (discussed in
Sections 8.2.3) and cell sizes specified in the overland flow region manager (see Section 20.2).
For example, if the cell size for a conductivity zones polygon map layer is set to 4 feet, then the
honeycomb cell size would have to be 0.25, 0.5, 1, 2 or 4. Honeycomb cell sizes should be less than
or equal to other map layer cell sizes.
It is possible to use a single elevation for either the ground surface, initial water table surface or any
of the other surfaces used in groundwater modeling by checking the appropriate box and typing in
an elevation. This is convenient for small projects or for testing hypothetical situations or specific
features of the program.
All surfaces are DEMs that must be imported via the Surface Manager.
As mentioned in the previous section, there are three surfaces that are always required for
groundwater modeling: (1) the ground surface; (2) the top of the confining layer (the base of the
surficial aquifer); and, (3) the initial water table. A single elevation or flat surface can be specified for
any or these surfaces, or a separate DEM can be specified for each. Optional surfaces include the
bottom of the confining layer and time-dependent potentiometric surfaces. Creating and importing
surfaces is described in detail in Chapter 9 and will not be repeated here. Also, creating a DEM from
a contour map layer is described in Section 8.4.
An important concept to understand is the interface between the surface water system and the
groundwater system. Section 24.3 describes how ICPR handles the interactions between these two
systems. When lakes, ponds, rivers and other water bodies are involved, the ground surface must
follow the bathymetry (bottom) of the water body. It is not appropriate to simply project the ground
surface across the water surface. For example, LiDAR technology does not work well below water
surfaces so some post-processing is necessary to fit bathometry into the final DEM.
The “Use Surfaces with Offsets” option requires that a DEM be specified for various time increments
over the simulation period like that shown below. A single DEM can also be used repeatedly with
time-variable vertical offsets. At least two points in time must be included in the table and cover the
entire simulation period.
It is helpful to understand how each parameter affects groundwater movement before establishing
the various map layers and zones. Fillable porosity is a storage component and affects the magnitude
of vertical fluctuations in the water table. The higher the porosity, the more storage there is and the
smaller the vertical fluctuations with all else being equal. As the porosity decreases, the storage also
decreases and causes vertical fluctuations to increase. Conductivity affects the transmissivity and
consequently, the horizontal movement of groundwater. Groundwater moves faster as
conductivities increase in value.
Although the fillable porosity above ground should typically be set to 1.0, there are some situations
when it should be set to something other than 1.0. For example, an exfiltration trench consists of a
perforated pipe in a gravel envelope. The ground surface for modeling purposes would be the
bottom of the trench, so as the water table intercepts the bottom of the trench, the porosity would
change from that of the native soil (e.g. 0.15) to that of the gravel (e.g. 0.5). A fillable porosity zone
would be needed for the extents of the trench to affect the porosity differences.
Corresponding Lookup Table: Fillable Porosity Sets. Refer to Section 7.3 for details on the lookup
table associated with fillable porosity.
Corresponding Lookup Table(s): Conductivity Sets. Refer to Section 7.3 for lookup tables
associated with conductivity data.
Corresponding Lookup Table(s): Leakage Sets. Refer to Section 7.3 for lookup tables associated
with leakage data.
September 2017
Contents
26. Groundwater Graphic Elements ................................................................................................. 5
   26.1 Exclusion ............................................................................................................................... 6
   26.2 Breakpoint ............................................................................................................................ 7
   26.3 Breakline ............................................................................................................................... 7
   26.4 Drains (Point, Line, Area) ...................................................................................................... 8
   26.5 Irrigation Wells ...................................................................................................................... 9
   26.6 Injection Wells....................................................................................................................... 9
   26.7 Boundary Stage (Point, Line, Area) ..................................................................................... 11
   26.8 External Hydrograph (Point, Line, Area).............................................................................. 12
The following sketch is taken from ICPR’s graphic view editor and depicts the options specifically
related to 2D groundwater flow. Groundwater regions were discussed in detail in Chapter 25. As
mentioned in that chapter, it is possible to have multiple regions for a given project. Graphic
elements are always placed in the active region of the active scenario.
To add any of the above graphic elements to your project, select one from the dropdown list and then
click the “create graphic element” icon. A prompt will appear at the lower left corner of the graphic
view window with drawing instructions.
It is possible to create all the 2D groundwater features in a GIS and then import them to ICPR via an
XML file or a collection of CSV files or shapefiles. To import a shapefile, expand the “Feature Types”
of graphic element tree located on the left side of the “general” tab as shown below. Move the cursor
over any of the features and right click.
Data forms for any of the graphic elements can be opened by double clicking it, or using the “2D
Features > Groundwater” menu options.
26.1 Exclusion
Exclusions are closed polygons within a groundwater region. The area inside this type of feature is
“excluded” from the triangular mesh generation process. Consequently, groundwater cannot move
across an exclusion polygon. Groundwater flow is permitted along its perimeter. Exclusions can be
used to incorporate fully penetrating impermeable barriers within the groundwater region, such as a
sub-surface wall (see figure below).
26.2 Breakpoint
Breakpoints are added for refinement of the triangular mesh, like overland flow breakpoints, and can
be placed anywhere within a groundwater region. However, breakpoints placed in an exclusion
feature are ignored. Vertices are guaranteed at breakpoints.
The approach illustrated in the example above is probably adequate for a regional model, but more
detail and more accuracy in terms of seepage and recharge might be warranted for a site-specific
application. As discussed in the following
section, breaklines can be used to insure
precise locations of triangle edges.
26.3 Breakline
Breaklines, like breakpoints, are used to refine
the triangular mesh. Triangle vertices are
guaranteed at each coordinate point of the breakline. Furthermore, triangle edges are guaranteed
along the breakline.
The flow to a drain is head dependent based on a user specified conductance. The units for the
conductance value depend on the drain type and are summarized as follows:
1. Drain Point – cubic feet per second per foot of head or square feet per second
                  2. Drain Line – cubic feet per second per foot of head per lineal foot of drain or
                     feet per second
                  3. Drain Area – cubic feet per second per foot of head per square foot of drain area
                     or per second
                  4. Meters replace feet for metric units of the above.
The maximum possible flow rate is restricted by the limiting head. Note that the head is measured
as the groundwater elevation minus the elevation of the receiving 1D node or the bottom of the drain,
whichever is higher. Flow reversals are possible with drains.
The Depth / Elevation must not project below the top of the confining layer.
There are three parameters that must be set for the injection well as shown below: (1) well diameter;
(2) mesh scaling factor; and, (3) shut off elevation.
The scaling factor is used by ICPR to build the triangular computational mesh around the injection
well. Two internal breaklines are created when a “Scenario > Build” takes place (mesh construction
and parameterization). The first breakline is circular with 10-degree chord segments placed a
distance equal to the well diameter times the mesh scaling factor away from the center of the well.
The second breakline is placed 2 times this distance away from the first breakline. For example, given
a well diameter of 2 feet and a mesh scaling factor of 2, the first breakline is placed at a radius of 4
feet away from the center on the well. The second breakline is placed 8 feet away from the first
corresponding to a radius of 12 feet from the center of the well. The corresponding mesh
construction is shown below.
Once you have placed the boundary stage point, line or area, you need to identify the table name(s)
that contains the time-stage data (a boundary stage table). This is done by opening the respective
data form and filling out the boundary stage name(s) as shown below.
For the boundary stage line feature, linear interpolation based on distance is used between the two
endpoints. It is important that the first table correspond to the first point entered on the boundary
stage line and the second table correspond to the last point. This can be determined by using the
edit polyline tool. Click the edit polyline icon then click the boundary line feature. The points are
numbered in the order that they were entered.
Once you have placed the external hydrograph point, line or area, you need to identify the table
name(s) that contains the time-flow data (an external hydrograph table). This is done by opening
the data form and filling out the external hydrograph name as shown below.
The data form is the same for the three external hydrograph types. Each of them requires a single
table name and a “Proportion of Total Flow” expressed as a decimal value from zero to one. For
example, if the proportion of total flow is set to 0.75, then 75% of the flows in the corresponding
external hydrograph table would be delivered to the groundwater system. The flow is further
distributed based on proportional length for the line feature and proportional area for area features.
September 2017
Contents
27. Groundwater Examples .............................................................................................................. 5
   27.1 Example 1 – Pond Drawdown, Sloping Water Table ............................................................... 5
      27.1.1 Base Data ........................................................................................................................ 6
      27.1.2 Model Setup.................................................................................................................. 11
      27.1.3 Mesh Construction ........................................................................................................ 15
      27.1.4 Simulations and Results ................................................................................................ 16
   27.2 Example 2 – Infiltration Galleries ......................................................................................... 24
      27.2.1 Background................................................................................................................... 24
      27.2.2 Model Setup ................................................................................................................. 27
      27.2.3 Computational Meshes ................................................................................................. 34
      27.2.4 Simulation Control........................................................................................................ 35
      27.2.5 Analysis ........................................................................................................................ 36
   27.3 Example – Injection Well ...................................................................................................... 40
      27.3.1 Groundwater Region ..................................................................................................... 40
      27.3.2 Injection Well and Breaklines ........................................................................................ 41
      27.3.3 Boundary Stage Line ..................................................................................................... 42
      27.3.4 Groundwater Properties ............................................................................................... 44
      27.3.5 Groundwater Region Manager ...................................................................................... 44
      27.3.6 Analysis......................................................................................................................... 45
   27.4 French Drain and Injection Well Strategies .......................................................................... 49
      27.4.1 French Drains ................................................................................................................ 49
      27.4.2 Drain Wells ................................................................................................................... 53
Elevations range from about 90 ft (NAVD 1988) at the north end of the project to about elevation 60
ft (NAVD 1988) at the southwest end. The water table generally slopes with the ground surface with
seepage outcrops along a wetland slough located along the western and southern boundaries of the
project area. All data for this example has already been entered. These key aspects are discussed in
the following sections.
             1. Base Data
                   a. aerial background image
                   b. surface DEMs
                   c. thematic polygon map layers
                   d. lookup tables
             2. Model Setup
                   a. 1D nodal network
                   b. 2D overland flow
                   c. 2D groundwater
             3. Mesh Construction
                   a. overland flow region manager
                   b. groundwater region manager
                   c. scenario build
             4. Simulations and Results
Surface “ground” is a LiDAR-based DEM (5x5-foot grid) obtained from the SWFWMD. Surface
“aquifer_base” is the top of the confining layer and was derived from data downloaded from the
Florida Geological Survey. Surface “wt_initial” is the initial water table and was developed by running
an ICPR groundwater model for the area over an extended period until the water table reached near-
equilibrium conditions.
The three surfaces can be view on the raster panel of the Graphic View. These are shown below at an
opacity of 75% and superimposed with the aerial background image. Notice that the aquifer base and
the initial water table are undulating. Percolation from the ponds in this example would be difficult
with the percolation links. The 2D groundwater approach allows for non-flat surfaces and non-
homogeneous soils.
The “Soils” map layer was downloaded from the NRCS soils web service. The “LandCover” map layer
was originally obtained from the SWFWMD but was modified to better reflect impervious and
pervious areas in the Regency Oaks development. The “Basins” map layer was drawn inside ICPR4.
The raster versions of these 3 map layers are shown below.
more accurately accounts for travel time through the vadose zone to the saturated zone. Soil
moisture and unsaturated vertical conductivity is tracked for each cell throughout the simulation.
The soil layer thickness is set to 20 feet and 100 cells is specified – each cell is 0.2 feet thick. The initial
water table “WT Initial” is set to 999 feet, but it is replaced by the actual water table depth as
determined by the groundwater model. A partial excerpt of the Green-Ampt table is shown below.
Note that the curve number method cannot communicate with the groundwater module in ICPR4.
Impervious Percentages: Impervious and DCIA percentages were set for each “LandCover” zone. The
impervious lookup table for this example is shown below.
Fillable Porosity: Fillable porosity values are set for each soil zone. Below ground porosities were
calculated as the difference between the Green-Ampt saturated moisture content and field capacity
moisture content. Above ground porosities were set to 1. An excerpt of the fillable porosity table is
shown below.
Saturated Horizontal Conductivity: Horizontal conductivities were set for each unique soil zone.
These conductivities are set to two times the saturated Green-Ampt vertical conductivities, which
have a FOS equal to 2. An excerpt of the conductivity lookup table is shown below.
Stage/area tables for nodes A, B and E were developed using the “Generate Stage/Area Table” tool
associated with pond control volumes. A 0.25-ft vertical spacing was used. An excerpt for Node A is
shown is shown below as an example.
A pattern of breakpoints was added to each pond control volume as shown below. A uniform spacing
of 25 feet was applied.
Breakpoints were copied from the overland flow region into the groundwater region for the pond
areas (25-foot spacing). A 25-foot pattern of breakpoints was also placed along the western side of
the region for refinement purposes between ponds A and E and the region boundary. Additional
breakpoints were added at a uniform spacing of 50 feet.
Boundary stage line features were added to the groundwater model along the western side. This is
where seepage outcrops are expected along a wetland slough. Groundwater stages are forced along
these lines based on boundary stage tables. An example is shown below.
A partial display of the groundwater honeycomb is shown below. Notice the refinement of the mesh
inside the pond control volumes.
Seepage inflow and outflow rates and volumes for pond “E” are shown below. There is much more
seepage into the pond than out of it. The excess seepage flows through the outfall structure, which
continues to flow at hour 120 in the simulation. Pond “E” was excavated into the side of a hill and has
intercepted groundwater flow from east to west.
A photograph of the pond at node E is shown below on the left. The pond is usually inundated and
has a mature stand of cypress trees in it – a wetland species. Pond A is shown below right and is
typically dry. Both photographs were taken while it was raining. Groundwater profiles through these
two systems are generated in following section.
Click the “Power” button and then “Go To Relative Time” 6 hours.
Move the cursor over the animation and right click. Set the “File Root Name” to “GW-006” and the
“DEM Cell Size” to “5” feet. Check the “Generate DEM Hdr/Flt File Pair” and click “OK”.
A message will appear when the process is complete, indicating the names and locations of the three
files that were created. Notice that these files are automatically placed in the “Surfaces” folder in the
project directory.
Repeat the above process for 12, 18, 24, 36, 48, 72, 96 and 120 hours.
Next, open the “Surface Manager” and click the “Batch Import” button at the lower right corner of
the data form. Navigate to the following folder and select all of the files shown below. Click “Open”.
A list of filenames appears – click Import again.
The new surfaces are included in the surface manager as shown below.
These surfaces can be viewed on the raster panel of the Graphic View as shown below. The intent of
preparing these surfaces is not to illustrate an animation, but rather to cut groundwater profiles from
the DEMs using ICPR’s “Display Profile” tool.
Click the “Display Profile” icon and then move the cursor over the northern-most reference polyline
and click. Check the following boxes (below right) and click OK.
The groundwater profiles at different points in time should appear along with the ground profile. The
groundwater table below “B” mounds significantly and the gradient is from right to left or toward the
western region boundary and pond “E”.
And here are profiles for the other reference polyline through pond “A”.
Open the following project and then open and maximize the Graphic View. Click the “Zoom Extents”
icon.
The focus of this example is a set of infiltration galleries (exfiltration beds) used to dispose of
stormwater runoff from a parking lot for a condominium project in Destin. The infiltration galleries
are modeled in ICPR as French drains and are interfaced with the groundwater module. A typical
section through one of the galleries is shown below and includes 6 parallel 18-inch perforated ADS-
N12 conduits enclosed in gravel and filter fabric. Other galleries for the project include 4 and 9
conduits in parallel as well as a single perforated pipe in one area.
Surface runoff from the parking areas enters the infiltration galleries through various inlets. Water is
dispersped through a system of parallel perforated pipes. Storage is available in the pipes and in the
gravel pit surrounding the pipes. In addition to storage and conveyance, stormwater percolates in
the soil column both vertically and horizontally. The groundwater table then responds to the
percolation and recharge by mounding and then moving horizontally based on hydraulic gradients.
perforated pipes in parallel with a total width of 16 feet.All of the perforated pipes in the infiltration
galleries are enveloped with gravel wrapped in filter fabric. A gravel porosity of 0.4 is assumed for
all galleries.
In addition to the grading and drainage plan, Jenkins provided a “Report of Subsurface Exploration
and Geotechnical Engineering Evaluation” prepared by Nova Engineering and Environmental. The
following stormwater management system soil design parameters were included in the Nova report.
Based on the above design parameters, the following model parameters are used in this example:
Although the vertical datum for the project is unknown, the example is consistent with the grading
and drainage plan.
The French drain link data form for gallery “A” is shown below. As previously stated, this gallery
includes six parallel 18-inch perforated pipes and has a total width of 24 feet. Therefore, the trench
width is set to 4 feet and the link count is set to 6 for a total width of 24 feet. Also, the mesh scaling
factor is set to 6. ICPR4 automatically creates a special control volume internally for this link with a
length equal to the trench length and a width equal to the trench width times the mesh scaling factor.
It is important to treat the ground surface directly above the infiltration galleries as impervious (even
if they are pervious) and then direct the runoff into the French drains. It will percolate into the soil
column from there. This can be accomplished by modeling the surface areas as “Manual Basins”. The
raster view of the “Manual Basins” map layer is shown below.
Right click on Manual Basin in the data tree to process the basin polygons (i.e. intersect map layers).
Notice that the map layer “Impervious-Above” is used as both the land cover zone and soil zone map
layer. There is only one soil type for this small site, but we need to restrict the vertical conductivity
over the French drains.
We only need one map layer before mesh construction – the impervious polygons. A map layer called
“Impervious-Below” is an exact copy of “Impervious-Above” except the polygons around the
infiltration galleries are labeled “Below Trench”. All other polygons are labeled the same as before.
The overland flow region manager is shown below. Notice that a single ground elevation of 13 feet
is used. Although we could prepare a detailed DEM based on the grading plan, it is not needed since
our focus is below the ground, not above it. Also, the map layer “Impervious-Below” is used for both
the Land Cover Zones and the Soil Zones. Lookup tables are used to parameterize each unique
polygon within the map layer.
A partial excerpt of the Green-Ampt lookup table is shown below. The saturated vertical conductivity
for all soil zones is 27 fpd except for “Above Trench” which is 0.00001 fpd – a very small value designed
to restrict infiltration above the French drains. Also notice that the difference between “MC
Saturated” and “MC Initial” is 0.25, which is the fillable porosity cited by the project’s geotechnical
engineer.
The fillable porosity and saturated horizontal conductivity tables are shown below. The fillable
porosity for the groundwater model is 0.25 and the conductivity is 40 fpd.
27.2.5 Analysis
27.2.5.1 Mass Balance
Click “Reports > Mass Balance Routing” after the simulation has completed. The percent error drops
to -1.6% at about hour 3.5 in the simulation. This occurs as the soil column below the French drains
becomes saturated and is likely due to abrupt changes in porosity and the different time increments
between surface and groundwater computations. Regardless, the maximum error is within
acceptable ranges and quickly reduces to a fraction of a percent by about hour 10.
The following chart shows the change in storage based on flows and by the change in geometry.
They are very close to one another and support the small mass balance error. Note that the
maximum overall change in storage is about 18,000 cubic feet. The exact amount of storage in all of
the French drains combined is 18,372 cubic feet. Therefore, ICPR4 is accurately accounting for the
storage in the infiltration galleries.
The cumulative volume of basin inflow (surface runoff) and seepage outflow (percolation) is shown
below. The system has almost fully recovered by hour 72 which is 48 hours after the rain has
subsided.
27.2.5.3 Animations
An animation sequence of the change in
groundwater elevation is shown on the
following page. The water table begins
mounding at the French drains as expected
and then pushes outward with time. The
mound between the two main infiltration
galleries is higher at hour 72 than directly
below the galleries.
A groundwater region must be created, an injection well graphical feature placed in the region and a
boundary stage line must be applied to a portion of the region boundary.
The well diameter, mesh scaling factor and shut off elevation must be set for injection wells. The
mesh scaling factor affects the mesh resolution around the well. Two internal breaklines are created
during the “Scenario > Build”. Both are circular in shape. The first is placed at a radius equal to the
mesh scaling factor times the well diameter (2 x 2 = 4 feet in this case). The second is located twice
this distance from the first breakline (i.e. 12 feet from the center of the well). Breaklines and
breakpoints can be added for further refinements.
The resulting computational mesh around the injection well is shown below.
27.3.6 Analysis
27.3.6.1 Mass Balance Check
27.3.6.4 Animations
A French drain link, like all other links in ICPR, connects two 1D nodes together, usually stage-area
node types. They can also be used to connect 1D node interface points, which are 2D overland flow
graphic elements. Percolation from a French drain link can be incorporated several ways including:
(1) adding rating curve links at the connecting nodes; (2) adding percolation links at the connecting
nodes; (3) letting ICPR automatically build OF and GW computational meshes based on the French
drain link parameters; and, (4) using a GW “drain line” feature in combination with the French drain
link.
Before discussing each of the above four approaches, it would be useful to understand a little bit
about the unique hydrogeology in southeast Florida since this is where French Drains and Injections
Wells are primarily used. There is a thin layer (e.g. less than 10 feet) of overburden on top of a
relatively thick limestone layer (e.g. more than 100 feet). The saturated horizontal conductivity is
often an order of magnitude less in the overburden than it is in the limestone. Exfiltration trenches
typically penetrate through the overburden into the highly permeable limestone. The ambient water
table is close to the surface and usually well above the bottom of the trenches and in the overburden
layer.
27.4.1.1.1 Advantages
One advantage of the rating curve approach is that vertically variable saturated horizontal
conductivities can be included in the rating curve operating table. It is also a relatively simple
approach that engineers practicing in southeast Florida are familiar with, so the learning curve would
be minimal.
27.4.1.1.2 Disadvantages
There are several disadvantages with this approach, the most significant being that the water moving
through the rating curve link is lost from the system. It is my understanding that the 2D groundwater
module of ICPR is to be used. Since the “to node” for the rating curve link must be a time-stage node
with this approach, there is no mechanism to incorporate the rating curve link discharge into the
groundwater module. Also, the time-stage relationship at the “to node” is supposed to reflect
groundwater mounding, but it is only an estimate and has no physical basis.
Like rating curve links, the “Overland Flow Region” and “Groundwater Region” data fields in the
French drain link must be left blank. Also, release v4.03.01or later is needed for this approach.
27.4.1.2.1 Advantages
As mentioned above, groundwater mounding impacts are automatically incorporated into
percolation links. These impacts are time dependent and physically based.
27.4.1.2.2 Disadvantages
Like the rating curve link approach, water moving through a percolation link cannot be delivered
(easily) to the 2D regional groundwater module in ICPR. Also, saturated horizontal conductivities
must be vertically averaged and cannot vary with depth in the trench. This is not considered a major
disadvantage considering the regional nature of the overall CFL SWMP model.
27.4.1.3 Automatic OF and GW Mesh Generation and Integration for French Drains
Assuming there are overlapping overland flow and groundwater regions encompassing one or more
French drain links, ICPR will automatically generate computational meshes and integrate them. The
only special requirements are that the “Overland Flow Region” and “Groundwater Region”
parameters be properly set in the French drain link data form and that an appropriate mesh scaling
factor be set. An example is provided in Section 27.2 of the most recent ICPR user’s manual.
27.4.1.3.1 Advantages
The greatest advantage of this approach is that surface water and groundwater integration with the
French drain is automatic and there is no need to incorporate other link types like ratings curves or
percolation links.
27.4.1.3.2 Disadvantages
Although the setup is relatively easy using this approach, the resulting computational meshes are
complex and very detailed. Depending on the number of French drains in the overall model, run times
can increase significantly. Also, the saturated horizontal conductivities in and near the French drains
are automatically derived from the conductivity map layer and corresponding lookup table. In other
words, the conductivities used for the groundwater model in French drain areas will also be used for
the French drain computations. There is no way to use separate conductivities in the overburden and
limestone layers. The very high conductivities in the limestone layer will likely create stability
problems in the French drains. Although the approach described in this section can be very effective
for smaller site plans, it might not be practical for large scale models like the CFL SWMP.
Groundwater drain lines can be implemented with French drain links as follows. The French drain link
is established as normal, except the “Overland Flow Region” and the “Groundwater Region” data
fields are left blank (like the rating curve and percolation link options described in Sections 27.4.1.1
and 27.4.1.2). Then a groundwater drain line graphic element is created and drawn directly on top of
the French drain link. The data form for the drain line must be opened and completed after it is
drawn, like that shown below. The bottom elevation of the GW drain line coincides with the bottom
of the French drain trench (elevation -10 feet in this example). The conductance is 0.009 cfs per lineal
foot of drain per foot of head. This can be easily derived from field measured permeability tests which
are usually expressed in units of cfs per square foot of side area per foot of head. It is just a matter of
multiplying this value by the number of square feet along the sides of the trench and then dividing
by the length of the drain line. Release v4.03.01 is needed for this approach.
27.4.1.4.1 Advantages
The advantages of this method are that it is easy to implement, is head dependent, allows for
different conductivities between the French drain and the underlying 2D groundwater model, and it
is more stable than the detailed mesh generation approach described in Section 2.3. Water entering
the French drain is not lost like with the rating curve link and percolation link approaches. Water
entering the French drain is delivered to the 2D groundwater module. This approach also offers a
means to generalize for regional models making it a more efficient approach for both existing
conditions and for proposed alternatives.
27.4.1.4.2 Disadvantages
The primary disadvantage is that variable vertical conductivities in the overburden layer cannot be
accommodated and an average value must be used. However, it is not likely that detailed field data
to that level will be available for a regional model.
27.4.2.1.1 Advantages
Injection wells are relatively easy to set up, although a little bit of extra effort is needed to set up the
1D surface components. If a weir link is connected to the injection well or if a head-discharge rating
curve link is connected to it, then it becomes a head-dependent system. Furthermore, adjustments
can be made to the rating curve to account for additional head losses caused by water density
differences due to high salinities in the groundwater system.
27.4.2.1.2 Disadvantages
The primary disadvantage of this approach is the GW computational mesh around the well is highly
detailed and refined. It can greatly increase the complexity of the overall groundwater mesh,
especially if a lot of wells are to be incorporated into the model, potentially increasing run times
significantly.
surface node with a weir or rating curve link, a conductance value is specified as shown below in units
of cfs per foot of head. For example, if a pump test indicates that a drain well can dispose of 600 gpm
per foot of head, the conductance would be set to 1.3368 cfs per foot of head (600 / 448.83). 1D links
are not attached to the drain point.
27.4.2.2.1 Advantages
This approach is very easy to set up and does not automatically result in a highly refined
computational mesh. It would be an efficient way to set up numerous wells in a regional model.
27.4.2.2.2 Disadvantages
The additional head loss associated with salinity differences cannot be accounted for using this
approach.
September 2017
Contents
28. Continuous Simulation Example – Hydroperiod Assessment ..................................................... 5
  28.1 Background ........................................................................................................................... 5
  28.2 Base Data .............................................................................................................................. 7
     28.2.1 Aerial Background Image................................................................................................ 7
     28.2.2 Surfaces (DEMs) ............................................................................................................. 8
     28.2.3 Map Layers ..................................................................................................................... 9
     28.2.4 Lookup Tables .............................................................................................................. 10
     28.2.5 Project Resources ......................................................................................................... 14
  28.3 Model Setup ........................................................................................................................ 16
     28.3.1 1D Nodes, Links and Cross Sections ...............................................................................17
     28.3.2 Overland Flow Region .................................................................................................. 20
     28.3.3 Groundwater Region..................................................................................................... 23
  28.4 Region Managers and Mesh Construction ........................................................................... 26
     28.4.1 Overland Flow Region Manager.................................................................................... 26
     28.4.2 Groundwater Region Manager ..................................................................................... 29
     28.4.3 The Scenario Build ........................................................................................................ 29
  28.5 Simulation Manager and Execution ..................................................................................... 30
  28.6 Analyzing Results ................................................................................................................ 33
     28.6.1 Mass Balance Error ....................................................................................................... 33
     28.6.2 Water Budget ............................................................................................................... 34
     28.6.3 Stage and Surface Area for 1D Nodes ........................................................................... 38
     28.6.4 Animations ................................................................................................................... 48
Although continuous simulation can be performed with manual basins and without consideration of
groundwater conditions, an integrated surface and groundwater model is preferred. When manual
basins are used, a constant water table elevation is assumed and the only mechanism to recover soil
storage is by evapotranspiration.
Intersecting overland flow and groundwater regions are needed to model variable water tables and
for surface water bodies to interact with groundwater bodies. Furthermore, the curve number
method should never be used for continuous simulation because it has no mechanism to recover soil
storage or to track soil moisture and evapotranspiration. Evapotranspiration is not possible with the
1D version of ICPR, you must have the full 1D/2D version.
In this example, a network of ditches is used for drainage and to control the water table for the 615-
acre agricultural tract shown below. There are 3 outlets (pump stations) at the west end modeled as
rating curve links. There are also several internal water control structures that are modeled as weir
links.
Two restoration alternatives are also evaluated in this example. The first alternative includes
removing the pump stations to close the outlets. The objective of this alternative is to increase
average surface water and groundwater elevations as well as the overall vertical range of water level
fluctuations to sustain a viable wetland ecosystem.
The second restoration alternative includes filling the canals and re-grading the land to create deeper
pools. There are no outlets with this alternative.
Hydroperiods of the three scenarios are quantified statistically in terms of exceedance probabilities.
Open the following project and then open the Graphic View, maximize it and zoom extents.
Map layers can be viewed in both vector and raster form. The vector and raster views of the soils map
layer are shown below as an example.
vertically through the soil column. Fillable porosity and saturated horizontal conductivity are
groundwater parameters and affect the horizontal movement of water in the saturated zone. The
crop coefficients are used to account for evapotranspiration from the soil column. Each of these
tables is discussed in the following sections.
The Green-Ampt parameters (click the “Green-Ampt” tab at the bottom left corner of the form)
affect infiltration into the soil column and percolation through the unsaturated vadose zone.
Development of the various soil parameters were derived mostly from the NRCS SSURGO database
for each soil type and equations provided in Section 7.4 of this manual.
       Saturated vertical conductivities were taken directly from the SSURGO data, but were
        reduced by 50% to introduce a factor of safety of 2.
        The saturated moisture content was derived from the bulk density published in the SSURGO
         data.
         Field capacity and wilting point were taken directly from SSURGO data.
        The initial moisture content was assumed to be equal to the field capacity.
        The residual moisture content, pore size index and bubble pressure were calculated from
         regression equations presented in Section 7.4 with percent clay, percent sand and
         saturated moisture content as independent variables.
        Percent clay and sand are available in the SSURGO data.
Although the initial water table depth is arbitrarily set to 999 feet, it is inconsequential in this example
because the water table is automatically derived from the groundwater model throughout the
simulation period.
Crop coefficient tables must be provided for each zone in the “Land Use” map layer. The crop
coefficient lookup table can be viewed by clicking “Tables > Evapotranspiration > Crop Coefficient
Sets”. As noted in the comment field of the set tab, crop coefficients are based on information
included in the “Myakka River Watershed Initiative Water Budget Model Development and
Calibration – Final Report” prepared by Interflow Engineering (December 5, 2008) and the Institute
of Food and Agricultural Sciences (IFAS) at the University of Florida.
Click the “Crop Coefficient” tab to view details for each crop coefficient zone. Note that the crop
coefficient and root depth vary with time. Irrigation sources and irrigation rules are also defined in
the crop coefficient lookup table, but are not used in this example because irrigation in this type of
farming operation is typically through water table control as opposed to applied irrigation. The
“Allow Saturated ET” option is selected for all crop types.
Albert Einstein
With Albert Einstein in mind, here is a list of key considerations when setting up an ICPR model for
this project:
        The weir is the most important component of a drop structure relative to continuous
         simulation and weir links are generally the most efficient link type in ICPR. Therefore,
         all drop structure links are modeled as weir links – the pipe component of the drop
         structure is ignored.
        An overland flow region is required to integrate surface water with groundwater.
        2D overland flow is computationally intensive and should be avoided when possible
         with continuous simulation. An alternative strategy using pond control volumes is
         applied in this example. It captures the storage accurately but ignores friction and
         travel times across the various farm fields, which is inconsequential over the long
         periods of time being modeled.
        When the groundwater table pierces the ground surface, the water surface
         elevations in the surface model should be used as known head conditions in the
         groundwater model. This is accomplished using pond control volumes instead of
         mapped basins.
        The groundwater computational mesh includes mid-nodes along the sides of
         triangles as well as at the vertices. Therefore, the groundwater mesh can be coarser
         than the surface mesh.
There are three (3) primary model setup tasks required for this example:
Instead of using traditional drainage basins in this example, the existing condition project area is
discretized into 13 level pool ponds (i.e. pond control volumes). To accomplish this, an overland flow
region is created and a special graphical element called a “pond control volume” is associated with
each of the 1D stage-area nodes. Pond control volumes are polygons. The ponds are further
discretized into a computational mesh (“the honeycomb”) that communicates directly with the
groundwater model. Each honeycomb behaves like a traditional basin except rainfall excess is
delivered directly to its corresponding node without applying a unit hydrograph. Stage-area tables
are generated for each of them from the ground surface DEM.
The ponds are connected using weir links. Some of the weir links represent the weir components of
the drop structures and others use irregular cross sections extracted from the surface DEM.
Rating curve links are used to model the 3 pump stations at the outlet locations. Each pump station
has a 5 cfs capacity. The “on” elevation is 20 feet and the “off” elevation is 19.5 feet. The pumps are
used only in the existing condition scenario. They are turned off for restoration alternative 1 and are
completely removed from restoration alternative 2.
Make sure the following options are set (include check marks in the various boxes).
Move the cursor into the graphic work area and click once, then press “Ctrl S” to view the drainage
network in the schematic mode. You should see a schematic of the 1D model setup although your
color scheme might be different.
This model consists of 16 1D nodes. Three (3) of them are time/stage nodes located along the western
edge of the study area and are designated “TW1”, “TW2” and “TW3”. All remaining nodes are
stage/area node types. Seven (7) of these are located inside the various canals, five (5) are in the
fields and one (1) is a marsh system near the southeast corner of the study area. Notice that a
stage/area node is placed in each of the basin polygons even though traditional basins are not used
in this example.
There are 14 weir links in total with 6 of them representing control structures and 8 that use irregular
cross sections extracted from the surface DEM. An example of an irregular cross section is shown
below. Cross section “X-FNE” is a graphic element (a weir type of cross section) that was manually
drawn in ICPR. The cross section was extracted from the ground surface DEM using ICPR’s cross
section extraction tool. It was then assigned to weir link “FNE-C4”.
There are also 3 rating curve links used for the pump stations at the outlets along the western side of
the project. An example is shown below. A stage-discharge rating curve operating table called “Pump
– 5 cfs” is referenced in the links, with an “Elevation On” of 20.0 feet and an “Elevation Off” of 19.5
feet.
There are 3 overland flow feature types (graphic elements) used for this project:
28.3.2.2 Breaklines
The canals and ditches are almost always inundated on this property. These become known head
locations for the groundwater model with heads forced by the surface water elevation – if the surface
model is setup properly. Triangle edges and vertices are guaranteed along breaklines. Elevations are
calculated at the vertices and these in turn are provided to the groundwater model in the form of a
known head condition. Therefore, breaklines are needed along the bottoms of the canals and major
ditches.
Notice in the sketch shown below that breaklines do not cross pond control volumes. This is
intentional and prevents the inadvertent generation of tiny triangles.
28.3.2.3 Breakpoints
Breakpoints are used to further refine the computational mesh. A pattern of breakpoints in the form
of equilateral triangles with side lengths of 100 feet is used for this example. A buffer of 100 feet from
other graphical elements has been applied.
        1. Breaklines
        2. Breakpoints
        3. Boundary Stage Line
28.3.3.1 Breaklines
All the breaklines used in the overland flow region were copied to the groundwater region using the
tool shown below. No other breaklines are needed for the groundwater region.
28.3.3.2 Breakpoints
A pattern of breakpoints in the form of equilateral triangles with side lengths of 200 feet is used for
this example. A buffer of 50 feet from other graphical elements has been applied. The groundwater
breakpoints are shown below in red superimposed with the overland flow breakpoints in black.
The boundary stage line data form is shown below and it references the boundary stage table called
“Perimeter Canals (S83_T)”.
                                   You must do a scenario build to execute this project and review the
                                   results. Click “Scenario > Scenario Manager” and then click the “Build”
                                   button in the lower left corner. Separate builds are required for each
                                   scenario.
The calculation times are shown below. The surface hydraulics are very simple for this project with
only 16 1D nodes and 17 links for the existing scenario. Most of the computational effort is in the
hydrology because of the large number of sub-polygons and the groundwater module because of its
complexity. However, much larger time increments can be used for these two modules. A 900-
second (15 minutes) time increment is used for the hydrology. Recall that we are using hourly
NEXRAD rainfall data. The groundwater module uses an 86,400-second (1 day) time increment.
Daily output increments (1,440 minutes) are used for all three modules – hydrology, surface
hydraulics and groundwater.
The rainfall and reference ET folders are set to “NEXRAD” and “USGS_ET” as shown below. These
were discussed in Section 28.2.5.
There are 6 lookup tables (discussed in Section 28.2.4) used for this project as noted below.
The SAOR time marching algorithm is used. There would be no advantage to use the FIREBALL
method because there are only 16 surface nodes in this model and the FIREBALL method is more
appropriate for very large complex surface models. Notice that the “Initial Abstraction Recovery
Time” is set to 24 hours. This is the amount of time required to fully recover (i.e. evaporate) any water
stored as initial abstraction.
The “Existing” and “Restoration Alt1” simulations took about 30 minutes each to complete on an Intel
I7 – 4.0 GHz processor and the “Restoration Alt2” took about 8 minutes.
The mass balance error for all 3 simulations is well within acceptable levels. The worst case is at the
beginning of the “Restoration Alt2” simulation at about -1.5% but is mostly between -0.2% and 0.0%.
The mass balance report volumes are cumulative and we only need the values at the end of the
simulation. If you set the start and end times to the corresponding simulation end time (January 1,
2007), then only the last output value will appear in the report.
Make sure the “Report” tab is selected and then make the following settings and then click the “View
Report” button.
Cumulative volumes, in inches, appear for the entire simulation for each of the 3 scenarios.
“Rainfall Excess” in the table above is the surface runoff delivered to the surface hydraulic network.
This is the precipitation amount minus ET, initial abstraction and infiltration. The infiltration amount
is equal to the recharge volume (delivered to the groundwater model) plus the stored volume (change
in soil storage). A negative rainfall excess volume can occur when there is ponded water with no
rainfall – ponded water can seep into the soil column or evaporate.
A summary of the hydrologic water balance for the 3 simulations, annualized over the 5-year period,
is presented below. Notice that the ET increases and infiltration decreases for the restoration
alternatives. This is due in part to change in vegetation, but it is also because the surface outlets were
eliminated with the restoration alternatives and more water was available for evapotranspiration.
           Losses
             Initial Abstraction        3.29                3.29                     3.38
             ET Actual                 34.45               38.32                    42.55
             Infiltration              10.20                7.28                     3.26
           Total Losses                47.94               48.89                    49.19
Annualized Hydrologic Water Budget Summary (all units in inches per year)
Next, let’s look at the surface water budget. The “1D Nodes > Aggregate” report is used. This report
adds volumes from multiple nodes.
Set the start and end times to January 1, 2007 again to match the simulation end time.
Select only the interior nodes (i.e. the stage – area nodes, not the time – stage nodes). You will have
to do this for each scenario.
Make the following settings and then click the “View Report” button.
The volumes are in acre-feet and are cumulative values for the entire simulation. Notice that there
are “Inflow” and “Outflow” volumes for each category. To obtain the net volume, you must subtract
the outflow volume from the inflow volume. Sometimes the net volumes will be negative meaning
there is more outflow than inflow. The “Basin” category is the rainfall excess volume or surface runoff
volume from the hydrology component of the model. Basin inflows occur when the precipitation
exceeds the sum of ET, initial abstraction and infiltration. Basin outflows occur when the sum of ET,
initial abstraction and infiltration exceed the precipitation.
Link inflows and link outflows are the sum of all links in the model. Link inflow and outflow equal each
other for the restoration projects because the outlets were eliminated.
Seepage includes groundwater flows from the perimeter ditch as well as interior seepage.
The surface water budget presented below is in inches per year over the project area (614.48 acres)
based on the 5-year simulation period.
           Losses
             Surface Outlet              53.35               0.00                     0.00
Annualized Surface Water Budget Summary (all units in inches per year)
This is the stage hydrograph for node “Field SE 1” and for simulation “Existing”. The warning stage is
the elevation at which this field begins to flood. The field is below the warning stage and in the
ditches most of the time, which is the intent of ditches and pump stations.
The stage hydrograph for Restoration Alt1 is shown below. Recall that this alternative eliminates the
pump stations. Consequently, there is no surface outlet. Field SE 1 is inundated much of the time.
The stage hydrograph for Restoration Alt2 is shown below. This alternative includes eliminating the
surface outlet, filling the ditches and re-grading the fields. Although this field dries out from time to
time, it is inundated for longer periods of time.
This is the stage for node “Field SE 1” and for simulation “Existing” expressed in terms of exceedance
probability. The straight red line is the warning stage and in this example, it represents the low field
elevation or the elevation at which this field begins to flood. The warning stage crossing the
exceedance probability curve at about 5%, meaning that stages will be higher than elevation 23.4
feet 5% of the time (about 18 days a year) on average over a long period of time.
Eliminating the pump stations (restoration alt1) causes this field to flood about 70% of the time (more
than 8 months a year). It is about 3 inches deep or greater 25% of the time (3 months a year).
Re-grading the fields, filling the ditches and eliminating the surface outlets keeps Field SE flooded
about 65% of the time (slightly less than 8 months a year). A flood depth of 6 inches or greater is
expected 25% of the time (3 months a year).
The following is the wetted surface area in square feet of node “Field SE 1” for simulation “Existing”
expressed as an exceedance probability. The wetted surface area is approximately 84,000 square
feet (1.93 acres) at the 25% exceedance probability.
The wetted surface area for restoration alt1 is about 520,000 square feet (11.94 acres) for the 25%
exceedance probability, about 6 times greater than the existing condition.
There are about 1,120,000 square feet (25.71 acres) inundated at a 25% exceedance probability for
restoration alt2. This is more than 2 times greater than alt1 and 13.3 times greater than the existing
condition. However, it is a more complicated and expensive implementation effort.
Raster charts of depth above the warning stage are presented below for the 3 scenarios. These charts
provide a visual means to determine wet and dry periods, and how the depth of flooding is dispersed
throughout the year.
28.6.4 Animations
There are thousands of data points at every surface and groundwater vertex for the 5-year simulation
period executed in this example. Although ICPR has reporting tools to access results for individual
vertices, it would be tedious at best to analyze results like that. Instead, animations provide an easier
tool for visualizing results. For example, an animation of surface water elevations at each of the daily
output increments can be played. Furthermore, surface and groundwater elevations can be
expressed in terms of exceedance probabilities, which is a much easier and useful way to visualize
and review long simulation periods.
Click the “power” button and then click the “end” button.
The maximum flood depths for the 5-year simulation period appear. Most of the flooding is in the
channels and only minor flooding occurs in the fields.
Repeat the process for “Restoration Alt1”. The maximum flood extents expand much farther into the
fields with this alternative, but the flood depths are mostly less than 1 foot except in the channels.
Repeat the process for “Restoration Alt2”. Recall that this option included filling the ditches and re-
grading the fields. There is a greater vertical fluctuation in flood depths with this alternative.
You might need to click the power button off and then on again. Set the “relative time” to 10, which
is the 10% exceedance probability for this animation option. Click the “Go To Relative Time” button.
Repeat for 20% and 30%.
The flood extents for the 10%, 20% and 30% exceedance probabilities (36.5, 73.0 and 109.5 days per
year on average, respectively) are shown below.
Restoration Alt1
You might need to click the power button off and then on again. Set the “relative time” to 21,168
(June 1, 2004 – end of the dry season). Click the “Go To Relative Time” button. Repeat for hour 24,096
(October 1, 2004 – end of rainy season).
The warmer colors are generally drier conditions and the cooler colors are generally wetter. Try
setting the “sleep rate” to 0.05 seconds and play the animation from the beginning. Try the other 2
scenarios.
Restoration Alt2
You might need to click the power button off and then on again. Set the “relative time” to 25 (the
25% exceedance probability). Click the “Go To Relative Time” button.
Right click anywhere in the viewing area to generate a DEM. These are stored in the project’s
“Surfaces” folder as *.flt, *.hdr file pairs.
Repeat this for the 50% and 75% exceedance probabilities. And then repeat the whole process for
“Restoration Alt1” and “Restoration Alt2”.
Navigate to the following folder and select the 9 files shown below. Then click the open button. A list
of the files will appear – click the Import button again. These will appear in the surface manager when
the import is complete.
The 9 surfaces that were just imported can be viewed from the raster tab of the graphic view just like
any other surface. However, the “display profile” tool will be used to evaluate the existing condition
and alternatives.
Toggle the reference polylines on for scenario “Restoration Alt2” as shown below. Click the “Display
Profile” tool and then click the northern-most reference polyline.
Existing Grade – 25% Exceedance Probability for Existing and Restoration Alt1 Scenarios
Existing Grade – 50% Exceedance Probability for Existing and Restoration Alt1 Scenarios
Existing Grade – 75% Exceedance Probability for Existing and Restoration Alt1 Scenarios
Now click the Display Profile tool again and then select the
southern-most reference polyline. Make the surface
selections shown to the right and then click OK. The
profiles are shown on the following page.
Existing and Proposed Grades – 25% Exceedance Probability for Restoration Alt2
Proposed Grade – 25%, 50% & 100% Exceedance Probabilities for Restoration Alt2
Restoration Alt2