WMS:Routing HEC-1 Cards

File:Image190.jpg

Routing Data

Outlet points are used to define locations where hydrographs are combined and then routed downstream. The appropriate combined hydrograph (HC cards) stations are generated automatically when writing a HEC-1 file. However, routing data must be entered in order to simulate the movement of a flood wave through the river reaches or reservoirs. The effects of storage and flow resistance are accounted for in the shape and timing of the flood wave. In addition to these changes, volume may be lost due to channel infiltration. Most of the routing methods available in HEC-1 are based on the continuity equation and some relationship between flow and storage or stage.

Routing data is entered by selecting an outlet and then selecting the Routing Data button from the Edit HEC-1 Parameters dialog.

Outlet Names (KK)

Since outlets are used for both types (combining and routing) of hydrograph stations in the HEC-1 input file, a separate name for each type of hydrograph must be entered. The name should be six characters or less and correspond to the name used on the KK card to represent the appropriate hydrograph station. By default WMS uses the basin ID number followed by a "R" for the name, but a descriptive name is generally more useful.

Channel Losses (RL)

Constant channel losses may be defined by defining values for the RL record. These parameters include the following:

• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QLOSS} – Constant channel loss in entire routing in Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle cfs (cms)} . This value is subtracted from every ordinate of the inflow hydrograph.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle CLOSS} – Ratio of remaining flow (after Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QLOSS} ) which is lost for entire routing. After subtracting Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QLOSS} each inflow hydrograph ordinate is multiplied by Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle (1-CLOSS)} .
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle PERCRT} – Percolation rate Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle cfs/acre (cu m/sec-acre)} for wetted surface area of channel. This option is used in conjunction with storage routing and requires SA or SV/SE records to be defined.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle ELVINV} – Average invert elevation of channel Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle L} used to compute flow surface area for Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle PERCRT} .

Kinematic Wave (RK), Muskingum Cunge (RD) and Convex (RV)

The Kinematic wave, Muskingum Cunge, and Convex are defined with essentially the same parameters. A brief description follows.

• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle L} – Channel length.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle S} – Channel slope.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle N} – Manning's roughness.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle Shape} – Characteristic channel shape.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle WD} – Base width of the channel.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle Z} – Side slope of channel.

If the Muskingum-Cunge method is selected, define the channel geometry using an eight point cross-section by specifying the appropriate radio button and selecting the Define RC Record button.

NSTPS

NSTPS is the number of routing sub-reaches used to route the hydrograph in the Muskingum (RM), Straddler Stagger (RT), and Storage (RS) routing methods. To insure the Muskingum method's computational stability and the accuracy of computed hydrograph, the routing reach should be chosen so that:

Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \frac {1}{2(1-X)} \le \frac {AMSKK}{NSTPS \times \Delta t} \le \frac {1}{2X} }

Where Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} is the Muskingum weighting factor Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle (0 \le X \le 0.5)} , Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} is the travel time through the reach in minutes (multiply by 60), and Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \Delta t} is the computation time interval defined in the HEC-1 Job Control dialog in minutes.

For storage routing, Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} is usually about equal to (reach length / average velocity) / Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \Delta t} , where Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle \Delta t} is described above. Set Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} to 1 for a reservoir.

Muskingum (RM)

The Muskingum method is dependent primarily upon an input weighting factor. The parameters along with short descriptions of their meanings follow:

• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} – The number of integer steps for the Muskingum routing.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} – Muskingum Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle K} coefficient in hours for entire reach.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} – Muskingum Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle x} coefficient.

Using the basin data computed by WMS when a TIN or DEM is used to delineate the watershed, the Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} and Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} coefficients can easily be estimated. Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} is essentially the travel time for the reach, which can be estimated by noting the length of the stream segment (displayed in the Muskingum Cunge dialog even though it is dimmed) and multiplying by an assumed channel velocity (1-5 ft/s would be appropriate for most natural channels). Of course you will need to convert the estimated travel times from seconds to hours before entering it into the AMSKK edit field. The Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} value is the number of time steps the flood wave is in the channel and can be determined by dividing Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} by the computational time step found in the Job Control dialog (again, be sure that units are consistent).

The Muskingum method computes outflow from a reach using the following equation:

Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QOUR(2) = (CA - CB) \times QIN(1) + (1-CA) \times QOUT(1) + CB \times QIN(2) }

Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle CA = \frac {2 \times \Delta t}{2 \times AMSKK \times (1 - X) + \Delta t} }

Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle CB = \frac {\Delta t - 2 \times AMSKK \times X}{2 \times AMSKKK \times (1-X) + \Delta t} }

where Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QIN} is the inflow to the routing reach in Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle cfs (m^3/sec)} , Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle QOUT} is the outflow from the routing reach in Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle cfs (m^3/sec)} , Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} is the travel time through the reach in hours, and Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle X} is the Muskingum weighting factor Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle (0 \le X \le 0.5)} . The routing procedure may be repeated for several subreaches (designated as Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} ) so the total travel time through the reach is Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle AMSKK} .

Straddler Stagger (RT)

Parameters used to define the Straddler/Stagger or Tatum routing method are defined below.

• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTPS} – Should be one for Straddler/Stagger method or integer number of routing steps to be used for Tatum method.
• Failed to parse (SVG with PNG fallback (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://en.wikipedia.org/api/rest_v1/":): {\displaystyle NSTDL} – Integer number of intervals hydrograph is to be lagged in the Straddler/Stagger method or 0 if using Tatum method.
• $LAG$ – Integer number of ordinates to be averaged in the Straddler/Stagger method or 2 if using Tatum method.

Storage Routing (RS)

Storage-discharge routing can be used to define either channel or reservoir routing. When this routing option is specified the appropriate data items are dimmed and additional radio buttons are used to determine whether channel or reservoir routing is to be used.

The following parameters must be defined regardless of the storage routing option specified.

• NSTPS – Number of steps to be used in the storage routing. Typically this is approximately equal to (reach length) / (average velocity * time interval (NMIN) ). NSTPS is usually equal to 1 for a reservoir.
• ITYP – The next parameter RSVRIC can be entered in one of three different ways:
  • STOR – Storage in acre-feet (1000 cu m).
  • FLOW – Discharge in cfs (cms).
  • ELEV – Elevation in feet (m).
• RSVRIC – Storage, discharge, or elevation as defined by ITYP corresponding to the desired starting condition at the beginning of the first time period as specified on the IT record in the Job Control dialog.

HEC-1 No Routing (RN)

By default there is no routing at an outlet point. This allows for hydrographs to be combined without considering routing effects.

Output Control

For each hydrograph station (basin hydrographs, combined hydrographs, and routed hydrographs) different output controls can be specified. This dialog is accessed by selecting selecting the outlet, basin, reservoir, or diversion for which you want to edit data and then the Output Control dialog button from the Edit HEC-1 Parameters dialog. Entries which can be defined in this dialog are described below.

Routed and Combined Hydrographs at Outlets

In WMS an outlet point is used to represent locations where hydrographs are both combined and then routed. Therefore, if an outlet is selected before choosing the Output Control dialog, a radio group at the top of the dialog appears so that you may specify whether the options should be applied to the combined or routed hydrograph. If a basin is selected the radio group at the top of the dialog does not appear.

Comment Lines (KM)

Individual comments can be defined for each hydrograph station. These comments can be used to identify unique characteristics about a particular basin or outlet point. A new comment can be defined by selecting the new button in the Output Control dialog and then entering the comment in the text entry. When more than one comment card has been defined, the up and down arrow buttons can be used to scroll through the list of comments for that hydrograph station. When using WMS, comment cards always appear directly after the KK cards for each hydrograph station.

Output Control (KO)

These controls determine what information about a given hydrograph station is written to the HEC-1 ASCII output file. By default the IO record information is used. However, you may wish to print out a more (or less) complete summary for individual hydrograph stations.

By default, the option to write a hydrograph to the TAPE22 file is specified. This is the file read by WMS for display of hydrographs. Therefore, this option should only be changed to suppress particular hydrographs.

Reservoir Data

Reservoirs in HEC-1 can be defined in a few different ways, depending on the storage routing techniques that need to be modeled. The tutorial on creating topologic trees outlines the different methods that can be used to represent reservoirs. The parameters required to define the reservoir are the same in all cases. The main difference is whether the reservoir stands alone by itself or whether the routing option of the outlet is used to define the reservoir.

Reservoir Routing

If the reservoir routing option is specified then one method for volume and one method for outflow must be defined.

• Known volume – Define a known volume (SV) record using the XY Series Editor. Optionally, you can define the elevations (SE) which correspond to the known volumes.
• Computed volume – By defining an area (SA) elevation (SE) relationship the volume can be computed automatically by HEC-1. Both * records are defined using the XY Series Editor.

If a TIN has been used to define the watershed a storage capacity curve can be generated and the information used to set up the volume/elevation (SV, SE) or area/elevation (SA, SE) data. See Storage Capacity Curves for more information.

The available methods for outflow include:

• Known outflow – Define a known outflow (SQ) record using the XY Series Editor.
• Computed Weir Spillway – A combination of data records are used to define spillway characteristics (SL, SS, ST). Parameter description for these different records are as follows:

Low-Level Outlet (SL)

• ELEVL – Center line elevation of downstream end of low-level outlet.
• CAREA – Cross-sectional area in square feet (square m) in the low-level outlet orifice equation.
• COQL – Discharge coefficient in orifice outlet equation.
• EXPL – Exponent of head in orifice equation.

Spillway Characteristics (SS)

• CREL – Spillway crest elevation. This value must be less than the highest elevation on the SE card for HEC-1 to run properly.
• SPWID – Spillway length.
• COQW – Discharge coefficient in the spillway weir flow equation.
• EXPW – Exponent of head in the weir spillway flow equation, usually equals 1.5.

Dam Overtopping (ST)

• TOPEL – Elevation of the top of the dam at which overtopping begins.
• DAMWID – Length of the top-of-dam which is actively being overtopped.
• COQD – Discharge coefficient in the weir equation.
• EXPD – Exponent of head in the weir equation.

Channel Data

Constant channel losses may be defined by defining values for the RL record. These parameters include the following:

• QLOSS – Constant channel loss in entire routing in cfs (cms). This value is subtracted from every ordinate of the inflow hydrograph.
• CLOSS – Ratio of remaining flow (after QLOSS) which is lost for entire routing. After subtracting QLOSS each inflow hydrograph ordinate is multiplied by (1-CLOSS).
• PERCRT – Percolation rate cfs/acre (cu m/sec-acre) for wetted surface area of channel. This option is used in conjunction with storage routing and requires SA or SV/SE records to be defined.
• ELVINV – Average invert elevation of channel L used to compute flow surface area for PERCRT.

Channel Routing

If the channel routing option is specified, the Define button will access a dialog which allows you to choose between Normal depth and Modified-Puls methods. If Normal depth is specified, the following parameters must be defined for the RC record.

• Manning's coefficients – Manning roughness coefficients for the channel and left and right overbanks.
• Length – The length of the river reach.
• Slope – The slope of the river reach.
• Max Elevation – The maximum elevation for which storage and outflow values are to be computed.

In addition to these parameters an eight point cross section must be defined using the XY Series Editor. The first two points define the left overbank, the third point defines the left bank, the fourth and fifth points define the channel itself, the sixth point defines the right bank, and the last two points define the right overbank.

If the modified-Puls method is chosen the volume (SV) outflow (SQ) relationship must be defined. Both records are defined using the XY Series Editor.

Hydrographs

Direct Input Hydrograph (QI)

Hydrographs can be input directly using the QI record, and then routed downstream using the different routing options. To do this, select the Direct Input Hydrograph option and define the QI record using the XY Series Editor.

Pattern Hydrograph (QP)

This option is used to input a pattern hydrograph for an optimization job (OR record). A QP hydrograph can be used in conjunction with a QI and QO hydrograph to optimize routing parameters. This hydrograph can be input by selecting the check box and then defining the hydrograph using the XY Series Editor.

Related Topics

• HEC-1 Parameters
• XY Series Editor