My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Point Flow Analysis Software for the Lower South Platte River
CWCB
>
Water Supply Protection
>
DayForward
>
5001-6000
>
Point Flow Analysis Software for the Lower South Platte River
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2013 5:04:39 PM
Creation date
3/6/2013 3:09:49 PM
Metadata
Fields
Template:
Water Supply Protection
Description
User Guide: Point Flow Module & Querying & Charting Module
State
CO
Basin
South Platte
Water Division
1
Date
12/1/1994
Author
Northern Colorado Water Conservancy District
Title
User Guide for the Point Flow Analysis Software for the Lower South Platte River Kersey to Julesburg
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
77
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
OUTPUT DATA TABLES FOR THE LOWER SOUTH PLATTE RIVER (INPUT TABLES <br />TO Q &CM) <br />As illustrated in Figure 4, tables gainout.dbf and flowout.dbf are created by the Point Flow Software in <br />the case of the Lower South Platte River. The file names were defined as part of the User's input <br />necessary in the PFM. Descriptions of these tables are as follows. <br />Subreach Gains Table (gainout.dbf). As the name implies, gainout.dbf stores the computed subreach <br />gains in the units of cfs per river mile for the Lower South Platte River. The number of fields <br />included in gainout.dbf is equal to the number of subreaches existing within a defined river segment <br />(number of nodes minus one) plus a date field. The first field, REPORTDATE, stores the <br />temporal identification of the computed gains. REPORTDATE is a 'date' type field. The <br />remainder of the fields, in river mile order, have field names that identify the subreach for which <br />they refer and are defined as being of a 'numeric' type having a length of seven characters and <br />decimal precision of one. These field names are a concatenation of the first four characters of the <br />structure code name directly above the subreach with the first four characters of the structure <br />code name directly below the subreach. An underscore (_) appears between the two 4 - character <br />codes, resulting in field names having nine characters. For example, the first two structures <br />considered in the Lower South Platte River point flow study are the Kersey gauge <br />(KERSGAUGGG) and Crow Creek (CROWCRKICI). The name of the field within gainout.dbf <br />which holds the computed subreach gain for a particular day is KERS_CROW. <br />River Flows Table (flowout.dbh. The computed river flows directly above and below each node in the <br />Lower South Platte River are output from the PFM to the flowout.dbf database. The number of <br />fields residing in flowout.dbf (created by the Point Flow Software) is equal to twice the number of <br />defined subreaches plus a date field. Similar to all other tables, the first field, REPORTDATE, <br />stores the calendar date for which the river flows are computed. The remainder of the fields <br />describe the flow in the river channel. The field names are a concatenation of the seven character <br />' structure code and a two character suffix. The suffix describes whether the field is in reference to <br />flow directly up river from the node or directly down river of the node. The suffix, therefore, is <br />either 'UP' (representing up river) or 'DW' (representing down river). The structure code and the <br />two character suffix are separated by a single underscore U. The first structure and the last <br />structure within a defined river segment (usually gauging stations) only have one associated field <br />each within flowout.dbf. The PFM calculates only the flow directly down river of the first structure, <br />' and only the flow directly up river of the last river segment structure. Using the Crow Creek <br />example, the fields CROWCRK UP and CROWCRK_DW are created by the Flow /Gain <br />' Software and store numerical values which represent the flow (in cfs) at locations directly up river <br />and directly down river from Crow Creek. <br />27 ptflguid.wpd <br />
The URL can be used to link to this page
Your browser does not support the video tag.