Point Flow Analysis Software for the Lower South Platte River

Home Browse Search

GENERATION OF INPUT TABLES TO ACCOMMODATE ADDITIONAL RIVER SEGMENTS During the PFM development process, importance was given to incorporating some degree of versatility into the software so that river segments other than the Lower South Platte River could be analyzed and corresponding output tables created. The versatility of the PFM is centralized around the creation of the Control Table. Below is a rudimentary procedural outline that can be followed to assist in the creation of tables (Control Table and Historical Data Table(s)) needed to perform additional point flow studies. 1. Procure the historical data necessary to accomplish a point flow analysis for the river segment of interest. The information can be stored in multiple databases or one all- inclusive database. The structural format of the Historical Data Table(s) must be identical to that illustrated in Tables 3, 4, and 5, which contain information with respect to the Lower South Platte River. The first field in the Historical Data Tables must be REPORTDATE. The remaining fields need not be ordered in any particular manner. Care must be taken in defining the names of the fields within the Historical Data Tables. In particular, are the 8' and 10' character positions which must be coded in accordance with Figure 5. Character positions 1 through 7, and 9 are user defined. The file name given to a newly created Historical Data Table(s) is /are inconsequential as long as the User or User's realize the tables consistency. 2. Develop a Control Table that characterizes all of the fields residing in the Historical Data Table(s). Field names and field types must be identical to those listed in Table 2. The record order within the newly created Control Table is critical and must be arranged by ascending river mile. Furthermore, the 'Drying Point' record (if it is needed) must be the first record within a group of records having identical STRUCCODE. Also, when 'River Water' (direct diversion value) and 'Reservoir Water' (reservoir diversion value) are present, the 'River Water' record must immediately proceed the 'Reservoir Water' record for a given STRUCCODE. 3. Decide which information stored within the Historical Data Tables is to be utilized by the Point Flow Software in calculating subreach gains and river flows. Then set the UTILIZE logic field within the Control Table to True (.T.) if the field is to be utilized or False (.F.) if the field is to be neglected. In instances where similar information can be acquired from multiple Historical Data Tables, make certain that only one information source is used. For example, if diversion values for canal 'x' can be obtained from either Historical Data Table 'one.dbf or 'two.dbf, the UTILIZE field in the associated Control Table can only be True for one of these fields. 28 ptflguid.wpd