[From the U.S. Government Printing Office, www.gpo.gov]
HYDROLOGIC MODELING SYSTEM FOR NORTHERN NECK PLANNING DISTRICT ISSL Report No. 100 Information Support Systems Laboratory Department Agricultural Engineering College Agricultural and Life Sciences Virginia Polytechnic Institute and State University Blacksburg, Virginia COASTAL ZONE i GB INFORMATION CENTER 665 S53 1989 0. HYDROLOGIC MODELING SYSTEM FOR NORTHERN NECK PLANNING DISTRICT V. 0. Shanholtz and N. Zhang Information Support Systems Laboratory (VirGIS Project) Department of Agricultural Engineering College of Agriculture and Life Sciences Virginia Tech, Blacksburg, Virginia 24061-0303 Property of CSC Library ISSL Report No. 100 Northern Neck Planning Commission No. 17 P.O. Box H Calleo, Virginia 22435 December 4, 1989 U.S. DEPARTMENT OF COMMERCE NOAA COASTAL SERVICES CENTER 2234 SOUTH HOBSON AVENUE CHARLESTON , SC 29405 Acknowledgement We are grateful to Mr. Collin Powers, former Environmental Engineer, Northern Neck Planning Commission, for his vision and efforts in securing grant support without which this program could not have been initiated. To Mr. Fred Bates for his continued support of our overall program we offer our sincere thanks. To the Department of Conservation and Recreation-Division Soil and Water Conservation, a special thanks for continued support of the VirGIS program over the past five years, which has provided the potential for programs of this type over much of the Common- wealth. Richmond County, also, is acknowledged for providing access to watershed databases and generously sharing their resources for demonstrations of their GIS and related programs. And finally we are deeply indebted to a dedicated staff at the Information Support Systems Laboratory (ISSL) for their untiring efforts to quality performance without which efforts of this type would not be possible. This effort was supported by the Virginia Agricultural Experiment Station as a contributing pro- gram to Hatch Project No. 131391 through funds provided by the Northern Neck Planning Com- mission No. 17 Table of Contents 1.0 INTRODUCTION ................................................................................................................I 1. 1 Background ..................................................................................................................1 1.2 Objectives .....................................................................................................................2 2.0 MATHEMATICAL MODELINGTINITE ELEMENT STORM HYDROGRAPH MODEL ...............................................................................................3 2.1 Mathematical Modeling ...............................................................................................3 2.2 Finite Element Storm Hydrograph Model ........................... ................ 1. ....................5 2.3 Spatial Variability ................................................................................. .......................6 2.3.1 Rainfall Excess ........................................................I......................................6 2.3.2 Flow Routing .................................................................................................7 2.3.3 Issues in Defining Spatial Variability .............................................................7 2.4 Input Data Requirements for FESHM .......................................................................9 3.0 HYDROLOGIC MODELING SYSTEM ........................................................................... 10 3.1 Building FESHM Input Data Files ............................................................................ 10 3. 1.1 Standards ........................................................................................................ 12 3. 1. 1.1 Directories ......................................................................................... 12 3.1.1.2 File Naming Convention .................................................................. 13 3.1.1.2.1 VirGIS - Formatted Map Data Files ................................. 13 3.1.1.2.2 Attribute list ........................................................................ 13 3.1.1.2.3 FESHM input data files ...................................................... 14 3.1.2 Input Data Preparation .................................................................................. 14 3.1.2.1 Data Group I Output Control Options ....................................... 14 3.1.2.2 Data Group 2 Rainfall Distribution/Seasonal Infiltration Adjustment Factors ............................................................................. 14 3.1.2.2.1 Rainfall Distribution ........................................................... 14 3.1.2.2.1.1 Recorded Rainfall Record ..................................... 15 3.1.2.2.1.2 Design Storm Criteria ............................................ 15 3.1.2.2.2 Infiltration Adjustment Factors .......................................... 16 3.1.2.3 Data Group 3 Element/HRU Cross-Reference ........................... 16 3.1.2.4 Data Group 4 HRU Attribute List .............................................. 16 3.1.2.4.1 Generation of Landuse/Soil Type Attribute List ............... 20 3.1.2.5 Data Group 5 Computation Time Internal ................................. 21 3.1.2.6 Data Group 6 Flow Routing ....................................................... 22 3.1.2.6.1 Fortran Program STREAM ............................................... 22 3.1.2.6.2 Fortran Program DISCRETE ............................................ 23 3.1.2.6.3 Fortran Program SUBSHED ............................................. 27 3.1.2.7 Data Group 7 -- Channel and Overland Element Topographic Parameter ............................................................................................ 29 3.1.2.8 Data Group 8 -- Sediment Loading Input Data .............................. 29 3.2 Map Editor ................................................................................................................... 31 3.2.1 Functionality .................................................................................................. 31 3.2.2 Use of the Map Editor ................................................................................... 31 3.3 Menu System ............................................................................................................... 33 4.0 SUMMARY ........................................................................................................................... 38 5.0 SELECTED LITERATURE ON FESHM ......................................................................... 40 List of Figures Figure 1. Schematic of Hydrologic Modeling System for Northern Neck Planning District ....................................................................... I I Figure 2. Landuse theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ........................................................... 17 Figure 3. Soil type theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ........................................ 18 Figure 4. Hydrologic Response Units theme, which was derived by combining landuse (Figure 2) and soil type (Figure 3) ............................................................................................................. 19 Figure 5. Stream-order theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ........................................ 24 Figure 6. Preliminary stream-coding theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ..................... 25 Figure 7. Stream-network theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ........................................ 26 Figure 8. Final stream-coding theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ................................... 28 Figure 9. Sub-watershed map for selected segment of Haynesville quadrangle, Richmond County,* Virginia ........................................ 30 Figure 10. Screen display for editing-by-color .............................................................................. 33 Figure 11. Main menu options ...................................................................................................... 34 Figure 12. Display of multiple hydrographs generated by FESHM ............................................ 38 iv HYDROLOGIC MODELING SYSTEM FOR NORTHERN NECK PLANNING DISTRICT V. 0. Shanholtz and N. Zhang 1.0 INTRODUCTION 1. 1 Background In April 1989, the Information Support Systems Laboratory (ISSL), Department Agricultural Engineering, Virginia Tech entered into a contract with the Northern Neck Planning District Commission No. 17 to initiate the first phase of a multi-phased pro- gram for developing a comprehensive water resource management system (CWRMS) for the Northern Neck. The goal of this initiative is to provide water management tools with sufficient functionality to identify areas appropriate for local planning and regula- tory efforts and to model, assess and evaluate proposed projects and landuse activities. The basic components of the proposed "tool-kit" will include the following: 0 Information Support System ( GIS/Relational Data base/Table Lists, ect); 0 Hydrologic models (quantity and quality); 0 GIS/Relational Database/Model Interface(s); Hardware Platform; and Personnel Support. Although the above components are multi-dimensional, a significant beginning towards building a CWRMS currently exists in the Northern Neck. For example, ISSL with contracts from the Department of Conservation and Recreation-Division Soil and Water Conservation (DCR-DSWC) has developed and/or is participating in the follow- ing programs significant to improved management of water resources in the Northern Neck Planning District: 0 A digital Geographic Database from VirGIS contains base data layers for soil type and soil characteristics; elevation; surface flow drainage; landuse (cropland and pastureland); hydrologic units; and political boundaries (counties/cities). 0 A PC-based GIS system for Richmond County which includes additional data layers for wetlands (tidal and nontidal); watersheds (50-150 acres); flood plain; property boundaries; stream order; woodland; additional categories of landuse such as low density residential, commercial, etc; transportation; coastal zone erosion rates; historic sites; wildlife habitat; and Baylor grounds. A comprehensive surface and groundwater monitoring program (quantity and quality) in the upper reaches of Nomini Creek, which includes nutrient and pesticide concentrations; flow rates and volumes; rainfall (rates, volume, distribution and quality); comprehensive land use (including tillage and nu- trient and pesticide tracking on all land parcels within the study area); pesti- cide tracking on all land parcels within the study area); pesticide and nutrient movement through the vadose zone; and biological monitoring. Sediment and nutrient screening models for identifying expected annual sediment, nitrogen and phosphorus stream loading rates from agricultural land areas. 1.2 Objectives This report focuses on the development of a Hydrologic Modeling System (HMS) for assessing the impact of development and other land use changes on the quality of surface water entering receiving waters. Other programs are planned that will address ground water and interactions between surface and groundwater flow systems. The objectives of this project were: 0 To port the Finite Element Storm Hydrologic Model (FESHM) to a PC-based environment for use to simulate surface flows and sediment detachment and transport; and 0 To design, develop and implement a user friendly interface using Geographic Information System (GIS) Technology to assist with data compilation and display of simulation results. To accomplish the above objectives the workscope was divided into the following generaltasks: 1. Review of FESHM and organizing 1/0 functionality; 2 2. Porting mainframe version of FESHM to PC-base environment; 3. Developing software to automate the selection of model parameters; 4. Designing and developing a menu/prompt system for program navigation; 5. Designing and developing a procedure for conducting wh at-if- scenarios; 6. Linkage of all components for simulation of strcamflow hydrographs. The report is organized into sectinns reflecting the tasks outline above. Section 2.0 gives a summary of mathematical modeling and a brief review of concepts and functionality contained in the FESHM. The Hydrologic Modeling System is described in Section 3.0. Specific emphasis is placed on tasks 3 - 4 listed above. The application of the package for simulation of strearnflow hydrographs also is illustrated in Section 33. 2.0 MATHEMATICAL MODELING/FINITE ELEMENT STORM HYDROGRAPH MODEL 2.1 Mathematical Modeling Modeling is a technique for analyzing large complicated systems by constructing smaller systems that reflect only the characteristics of interest. With the rapid develop- mcnt of computers and computer technology during the past thirty years, it has become possible to model the hydrologic processes of a watershed as a series of interacting equations. These developments, which are often referred to as computer-based math- ematical watershed models, have generally been derived using either the 'systems' ap- proach or the 'parametric' approach. In the systems approach the watershed is conceptualized as a black box in which rainfall input and streaniflow output are related only through decision theory, systems analysis or operations research methods that need have no direct relation to the physical watershed system. 3 In the parametric approach, the rainfall input is normally operated on by em- pirical or deterministic relationships that attempt to describe specific physical processes such as infiltration, evaporation, overland flow, and channel flow. Thus each process is related to the streaniflow by some function of the related watershed parameter. A con- ceptual framework is first developed to link all the known significant system compo- nents. The components then are described by either theoretical or empirical equations. In this way the individual parameters, at least in concept, have physical meaning and can be studied by laboratory and/or field experiments. The use of modeling and simulation is increasingly becoming an acceptable tool to describe hydrologic activities within a given drainage system. Recent concern for environmental pollution with specific emphasis on improving the quality of the Chesapeake Bay, has provided renewed interest for using modeling techniques to relate land use practices to downstream water quality. Since pollutant transport is predomi- nantly a hydrologic process, there has been a major effort to interface material transport submodels with existing parametric hydrologic models. This effort has brought to light, however, an awareness that the values assigned to hydrologic parameters of a watershed vary widely within a single watershed. Thus, it is necessary to consider the spatial characteristics of the watershed such as soil boundaries, local topography, and land use, to account for the resulting water quality. Since'nonpoint pollution is tied so closely to the hydrologic system, any effort toward controlling it must consider the soil-water interface and the hydrologic transport system. Here hydrologic modeling can have its greatest benefit, The hydrologic model can be used to reduce the very complex natural watershed system to a more easily ob- servable system. The model user could then create a rational plan of attack for abate- ment of nonpoint pollution. First, it would be possible to isolate areas of the watershed where critical pollutional potential exists. Then the transport system could be examined to determine whether pollution arising at the specified location reaches the receiving 4 stream, lake or estuary or is deposited or transformed en route. Finally, the modeler could test pollution abatement schemes to be sure that the public receives the best pos- sible pollution abatement for each dollar spent. 2.2 Finite Element Storm Hydrograph Model The Finite Element Storm Hydrograph Model (FESHM) was selected for the hydrologic model sub-system because it was originally developed for the specific purpose of evaluating the impact of landuse change on flow regimes. The model structure is based on the concept that a watershed (or drainage area) can be sub-divided into smaller units that are assumed hydrologically homogeneous and that the flow responses from the individual units can be integrated to describe the watershed response. Conceptually, flows can be traced through the system and the influence of individual subsets deter- mined. The most significant advantage of this concept is that many aspects of the na- tural watershed system can be incorporated to answer specific questions about the hydrologic response due to perturbation. When the mathematical system is properly constructed it can be used with data at varying levels of resolution to analyze the water quantity and/or quality response from single farm units, entire basins, or the effect of single farm units on a larger watershed for a given rainfall occurrence. The finite element numerical method was used as the basis for the development of a spatially responsive model structure. A fundamental concept in finite element analysis is that most complex systems can be sub-divided to form some minimal number of subsets, that can be analyzed independently and the results collected to form the total system response. This concept provides a ready mechanisms For routing surface flow, given a reliable estimate of rainfall excess and reinfiltration. 5 The above procedure provides for tremendous flexibility for the incorporation of data for the purpose of generating synthetic hydrographs. All available data can be incorporated so that the spatiotemporal integrity of the area can be maintained. A new model structure is not necessary to do either micro- or macro-level modeling. 2.3 Spatial Variability Spatial variability is incorporated into FESHM to improve estimates of the spatiotemporal variations inherent in rainfall excess and the time distribution of runoff. Two discretization structures were developed to represent (1) the spatial and temporal distribution of rainfall excess and (2) the routing of the excess water through the drain- age system. 2.3.1 Rainfall Excess To improve estimates of rainfall excess FESHM utilizes a procedure that con- siders the spatial variability in soils and the spatiotemporal variability of landuse. Bas- ically, the area is subdivided into unique combinations based on soil mapping units and landuse data. The combinations are defined as Hydrologic Response Units (HRUs). The rainfall excess (i.e. water available for routing to a stream) for each HRU is calculated by a soil moisture algorithm which uses an empirical approximation to describe the in- filtration process in lieu of the partial differential equations of vertical unsaturated flow because infiltration recovery can be readily determined and the procedure has been demonstrated to provide acceptable estimates of excess rainfall. 6 2.3.2 Flow Routing To provide the best spatiotemporal representation of factors that effect flow routing, the watershed is subdivided into finite-sized elements. Watersheds (or drainage areas) are sub-divided into sub-watersheds based on the stream drainage network. Each sub-watershed then is sub-divided into overland flow strips. Each sub-watershed must have a minimurn of two flow strips (left and right of the stream). Each overland flow strip, also, can be further sub-divided into a series of elements to accommodate changes in the surface topography. For the situation where the overland flow strip is not sub- divided then it is defined as an element, which represents the basic unit in the sub- division. The sub-watersheds (tributary drainage systems) can be easily identified from a contour map. The sub-watersheds then are separated into unit source drainage areas and the strips into finite-sized elements as required for a specific analysis. An automated procedure for the delineation of watershed boundaries is described in Section 3.2. The division of the sub-watershed into overland flow strips and/or elements pro- vides additional flexibility for incorporating spatial variation.. At this level, the modeler has the option to refine the discretization of elements to the configuration that will provide the best solution to his problem. For example, if the modeler must determine the fate of nutrient applications on a particular crop, then the field or region containing the crop must be divided into elements so that flows emanating from the corn field can be separated from those originating from adjacent areas. 2.3.3 Issues in Defining Spatial Variability The first prerequisite to the application of a spatially responsive modeling system (eg FESHM) requires the creation of a data base that will adequately represent the 7 spatiotemporal character of the area being investigated. A number of watershed char- acteristics vary spatiotemporally and their variation must be described for proper eval- uation of the impact of each on the problem being addressed. The distribution of landuse is particularly important since the proximity of a given cropping system to well defined drainage channels will play a significant role in the magnitude of sediment and nutrients entering the receiving stream. The orientation of agricultural cropping systems with respect to slope and drainage channels can signif- icantly alter the hydrologic response of the area. This is particularly true for small storm events. The effect of landuse change on storm water runoff, however, tends to decrease as storm size increases. Surface retention storage varies significantly from one area to another. Values exceeding 1.5 inches may not be uncommon. The effect of such areas on storm water runoff and the associated impact on the movement and concentration of agricultural nutrients can be significant. Soils vary greatly in their hydraulic characteristics, therefore, the hydrologic re- sponse, also, often varies greatly. These variations are tempered somewhat by soil cover conditions, landuse patterns and management practices. Wet land areas, localized channelization, drainage projects, farm ponds, etc., can all impact the quantity and quality of water moved from a specific area. The preparation of a data base to include spatiotemporal variations is perhaps the most time-consuming and often challenging task that confronts a modeler (user). As previously noted FESHM is structured to provide the user with a high degree of flexibility for the inclusion of spatial detail to provide answers to a specific question. The major task that faces the user, however, is deciding on the level of discretization (i.e., spatial variability) that must be included to get a reliable simulation at the desired level 8 of predictability (accuracy). This problem is further complicated because of the general lack of objective criteria to define precisely what detail is necessary for most applica- tions. We have not, unfortunately, been able to define an exact line of demarcation. No single set of criteria appears to be usable. Rather, the separation point is a function of an incredibly complex set of factors, which not only includes physical properties of the drainage system but economic constraints. 2.4 Input Data Requirements for FESHM The input data requirements for FESHM can be grouped into the following cat- egories: 1. Control options -- Group I includes instructions for type of output listings and the time interval for discharge data listed in output. 2. Rainfall Distril)ution -- Group 2 includes data for number of raingages in the watershed, duration of storm event in hours, duration of the simulation, time interval of rainfall in seconds, antecedent soil moisture factor for the watershed, storm date (month, day, year, hour and n@iinute), and rainfall volumes per selected time interval. Also included in this group, are factors used to provide a seasonal adjustment to infiltration potential. 3. Element/HRU cross-reference -- Group 3 includes data to assign HRUs to elements with aerial extent. These data are used by FESHM to calculate weighted rainfall excess (ic an effective HRU). 4. Land use and HRU descriptors -- Group 4 includes data for FESHM param- eters relating to HRUs. The data are included in two tables for land use characteristics and HRU parameters, respectively. S. Computation time and index for flow routing -- Group 5 includes the time in- crements for routing both overland and channel flows. Additionally, this group includes the connectivity for the channel flow system. 6. Element descriptors for overland and channel flow -- Group 6 includes length, relief, channel roughness and flow cross-section data for overland and chan- nel elements. 9 3.0 HYDROLOGIC MODELING SYSTEM The Hydrologic Modeling System is PC-based and consists of a series ormodules linked via a system of menus for the purpose of simulating storm water discharge and sediment detachment and transport. The sediment detachment and transport compo- nent has not been completed. The menu navigational linkage for this segment wiil be included in the next update. A general schematic for the system configuration is given in Figure 1. The software was written using Fortran 77 and Metawindows graphics, and contains four levels of menus to provide the user access to GIS and hydrologic modeling functionality. A review of system functionality is covered in Sections 3.1, 3.2 and 3.3. The building of FESHM compatible databases is covered in Section 3.1, which is followed by a discussion of the Map Editor in Section 3.2. Finally, in Section 3.3 navigational functionality is covered. Additionally, the use of the system to simulate discharge hydrographs is illustrated with the appropriate menu options. 3.1 Building Input Databases As previously noted, the major difficulty with using distributed parameter hydrologic models is problems associated with preparing extensive databases that ade- quately reflect spatiotemporal variations that exist in watershed systems. A major effort was expended in this project to overcome many of these problems as they relate to data preparation for FESHM. The major issues involved automating the selection of topographic and soil/landuse related characteristics, keyboard entry of control in- structions and designing a linkage to provide access to all components of the system within the same computing environment. 10 mF.Nu sys rIm I DOS3. 3 FOR RAN 14ETAWN[ID I SPATI L ATTRIBUTE VIrG15 TA5LE S S DATA8ASEs LI IS IBM 386 Figure 1. Schematic of Hydrologic Modeling System for Northern Neck Planning District. The basic tasks to automate data preparation and input included the following: Designing standards for database creation and program access; Developing computer code to automate the selection of topographic char- acteristics required by FESHM; 0 Developing computer code to automate the definition of hydrologic response units; 0 Developing procedures to allow interactive entry of program control and rainfall distributions. 3. 1.1 Standards To simplify computer search for data and to improve the user interface, stand- ards for directories and for data filenames were established to represent related program functionality. 3. 1. 1.1 Directories rhe following directories were defined: 0 METAW-- This directory contains pointers to Metawindow graphics and related menu software. 0 PROGRAM -- This directory contains pointers to all Fortran programs. This package includes programs STREAM, DISCRETE, SUBSHED, HRU, EFFHRU, and FESHM. Also included are fortran procedures for system menus and prompts, and the procedures for using Metawindow graphics software. 0 DATAFILE -- This directory contains pointers to input data required by the programs in directory PROGRAM. The input data generally include VirGIS map data for soil type, landuse, elevation, stream network and stream order, user created VirGIS-formatted map data, attribute lists (tables) and FESHM input data organized into eight-groups. 0 TEMPFILE -- This directory contains pointers to all intermediate data files (temporary) that are created during program execution. These data files will usually be deleted after execution is completed. 12 3.1.1.2 File Naming Convention The standard for narning data riles was established by defining fixed file name extensions for each data type. These are presented in the following table list for VirG IS -formatted map data files, attribute lists and FESHM input data files, respec- tively. 3.1.1.2.1 VirGIS-formatted map data files Extensions Data type VirGIS Map VirGIS-formatted map Stream network VND VNF Stream order VOD VOF Landuse VLD VLF Soil type - VSD VSF Elevation VED VEF 3.1.1.2.2 Attribute list Extensions Data type Package provided User Created Soil attribute PAS UAS Landuse attribute PLS ULS 13 3.1.1.2.3 FESHM input data riles Extensions Data type VirGIS Mode Stand-alone Mode Group I GIV GIS Group 2 G2V G2S Group 3 G3V G3S Group 4 G4V G4S Group 5 G5V G5S Group 6 G6V G6S Group 7 G7V G7S Group 8 G8V G8S 3.1.2 Input Data Preparation The input data requirements for FESHM (see page 9) were reorganized into eight groups to provide better continuity between the computer code and data type that could be automated and the type that are entered interactively via the keyboard. The support provided for data automation and/or interactive data entry is discussed, by group, in Sections 3.1.2.1 through 3.1.2.8. 3.1.2.1 Data Group I -- Output Control Options The output control options provides for selective listing of output. The selection of appropriate output options is accomplished by responding to prompts through key- board. The options supported include following: 0 List HRU attributes; 0 List rainfall data; 0 Time interval for listing overland flow rates (seconds); Time interval for listing Channel flow rates (seconds); Nodes where the simulation results are to be listed; and The title of simulation run. 3.1.2.2 Data Group 2 -- Rainfall Distribution/Seasonal Infiltration Adjustment Factors 3.1.2.2.1 Rainfall Distribution This group of data is not currently included in the VirGIS database. the follow- ing two options, therefore, are provided for determining the rainfall distribution. 14 Obtain from recorded rainfall record; or Obtain from design storm criteria. 3.2.2.1.1 Recorded rainfall record The recorded rainfall distribution can be entered either interactively via the key- board or by entering a datafile created previously. Only the interactive option is cur- rently supported by the HMS package. The second option is planned at a later date when rainfall distribution data are included in the VirGIS database. The following information is requested for entry via the keyboard: 0 Number of rainfall gages for which data are being included (usually one); 0 Duration of rainfall (storm) in hours; 0 Duration of simulation (i.e. length of storm simulation) in hours; 0 Time interval of rainfall records (The intervals must be equal. The interval usually chosen is 15 minutes); Antecedent soil moisture condition for the watershed as a fraction of field capacity; Starting time of storm event (hour and minute); Month in which storm began; Day in which the storm began; Year in which storm began; and Rainfall data by time interval. 3.2.1.1.2 Design storm criteria This option is not currently supported by HMS but will involve selecting a design storm (eg rainfall expected to occur over a 24 hour period once every 10 years) and then generating a FESHM compatible rainfall distribution with appropriate computer code. This option is planned for the next update of HMS. 15 3.1.2.2.2 Infiltration Adjustment Factors To accommodate the variation of infiltration with season, FESHM uses a monthly step function to index variation. Options are provided to select system default values or to enter modifications via the keyboard. 3.1.2.3 Data Group 3 -- Element/HRU Cross-Reference In general the geometry of HRUs created by program lJRU (see Section 3.1.2.4) do not correspond to the element boundaries (sub-watersheds) defined by program SUBSHED (see Section 3.1.2.6). Since routing in FESHM is based on the element ge- metry, different HRU types within an element must be combined to provide an effective HORU, which is assumed to represent the soil-landuse characteristics for the element. Program EFFHRU was developed to create an Element/HRU cross-reference table. This table also includes the fractional aerial coverage that each HRU type occupied within a given element. These data are used by FESHM to determine effective (or weighted) parameters for each HRU. 3.1.2.4 Data Group 4 -- HRU Attribute List A Fortran program HRU was developed to over lay map data themes for soil type and landuse and to uniquely define all landu se- combinations (that is HRUS as previously defined). Each HRU is assigned a numeric code beginning with one for the first occur- rence. The maximum number of HRUs is equivalent to the number of soil types multi- plied by the number of landuse types. For a landuse data layer containing three basic landuse types, for example crop land, pasture land and non- agricultural land and a soil 16 ............ Figure 2. Landuse theme for selected segment of Haynesville quadrangle, Richmond County, Virginia ------------------------ . ......... Riton LM ME 06 4 wjO 9 5 1 erg on I'lI I L sL La I % Ier . 0 = I a IL a via sic 111 1 Figure 3. Soil type theme for selected segment of Haynesville quadrangle, Richmond County, Virginia - - - - - - - - - - - - - - - - - - - - - -- Ir a 41 ir M w 3 Ldl d .M6-Z MMMMM ' z Id IM IMMA I 0 L Mr. k, Figure 4. Hydrologic Response Units theme, which was derived by combining landuse (Figure 2) and soil type (Figure 3) type data layer containing 27 soil types, 71 unique HRUs are possible. A typical ex- ample of the process is illustrated with Figures 2, 3, and 4. Figure 4 represents all combinations resulting from overlaying landuse (Figure 2) and soil type (Figure 3). 3.2.4.1 Generation of Landuse/Soil Type Attribute List An automated procedure for the selection and building of this database is not currently supported by HMS. For the current application, attribute lists have been prepared for each landuse and soil type category existing the VirGIS database for Richmond County, Virginia. Other type (i.e. soils and /or landuse) can be entered using the Map Editor (Section 3.2). The landuse attribute list contains the following characteristics for each landuse type: Landuse code; Landuse type; Value of A in Holtan's infiltration equation; Potential depression storage; Roughness coefficients in Manning's equation; USLE cover factor; and USLE practice factor. The soil type attribute list contains the following characteristics for each soil type: 0 Soil type index code (numeric); 0 Soil type (alphanumeric); 0 Potential plant available water; 20 Potential gravitational water; Final infiltration rate; Depth of zone of maximum hydrologic activity (usually the A-horizon); Soil crodibility index; and Slope class. Program HRU uses the landuse and soil attribute lists to build FESHM param- eters for each HRU. 3.1.2.5 Data Group 5 -- Computation Time Interval The following computation time intervals must be provided by the user: Time increment for overland flow calculations; and Time increment for channel flow calculations. The stability of the time-integration procedure used in the finite element solution of the partial-differcntial equation is dependent on the value selected for the computation in- terval. When the value is too large the solution is unstable (incorrect results). When the values are significantly smaller then necessary, the execution time will be excessive. Users can enter these indexes by responding to prompts through the keyboard. Typical values have been incorporated as default. Other increments can be entered via the key- board. Error checking is provided to insure stability of the solution. 3.1.2.6 Data Group 6 -- Flow Routing 21 The following data are required by FESHM to route excess rainfall through the overland and channel flow system: Overland element N Flow length (width of element perpendicular to stream channel); 0 Relief (difference in elevation along the flow length); 0 Area; and N Top width at the downstream node of the clement. Channel element 0 Length; 0 Relief, N Roughness coefficient; and 0 Top width of the down stream node of the element (for defining channel cross-section). Routing connectivity For each overland clement, identify location relative corresponding channel clement (i.e. east or west bank/north or south bank); and For each channel element, identify up-stream tributaries. To automate the sub-division of a watershed and subsequent determinations of the above parameters, three software packages STREAM, DISCRETE and SUBSHED were developed. VirGIS map data themes for elevation, stream network and stream or- der also are required. An additional option which will be added in the next update of HMS will be user supplied watershed map. 3.1.2.6.1 FoWan program STREAM Fortran program STREAM was developed to define the connectivity of stream segments from a stream-order map. In the stream-order map, streams are classified as order I to 6. A first-order stream is defined as a unit source drainage, that is it has no 22 tributaries. A second-order is defined at the confluence of two first-order streams. For Richmond County, Virginia, the Rappahannock River was classified as a sixth-order stream. A typical stream-order map for a selected segment of the Haynesville quadrangle, is shown in Figure 5. The connectivity of the stream network is determined by first raster scanning a VirGIS-formatted stream-order map row-by-row and assigning a preliminary code to each stream cell. Numeric codes are assigned to identify the order ofthe stream segment and a count of the number of stream segments encountered from the beginning of scanning. For example, when the 58th sccond-order stream is encountered then the number of sccond-ordcr segments (58) and the second-order stream code (2) are con- catenated to give the preliminary code 582. After the scanning has been completed by program STREAM, the preliminary codes are sorted based on the connectivity of stream segments. A preliminary stream coding map based only on stream order, also, is created. The connectivities of the stream segments found during scanning and sorting are stored in a connectivity matrix based on the same coding scheme. A preliminary stream-coding map for a selected segment of the Haynesville quadrangle is shown in Figure 6. 3.1.2.6.2 Fortran Program DISCRETE A Fortran program DISCRETE was developed to further discretize the stream segments to a sub-watcrshed level based on tributaries and confluenccs determined from single center-line vectors of the stream-network map (Figure 7). The discretization of streams was accomplished by vectorizing the stream center-line and borders of stream segments to form polygons which represent the stream segments in two dimensions. 23 -- - - - - - - - - - - - - - . ......... Figure 5. Stream-order theme for selected segment of Haynesville quadrangle, Richmond County, Virginia .... ........... .......... ........... .... ..... . tr .......... J-jl Figure 6. Preliminary stream-coding theme for selected segment of Haynesville quadrangle, Richmond County, Virginia - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Figure 7. Stream-network theme for selected segment of Haynesville quadrangle, Richmond County, Virginia Each stream segment (or reach) represents the water body between two adjacent tributaries. Each stream segment then was defined as a channel element. The topographic parameters for each channel element, also, were calculated in either vector or raster mode and stored in FESHM compatible data files. The connectivity matrix was updated during the segment- to- segment analysis. The stream coding was also updated using the same coding scheme described previously. The updated connectivity matrix was stored in a data file for later use by FESHM. The final discretized stream-coding map for a selected segment of the Haynesville quadrangle is shown in Figure 8. 3.1.2.6.3 Fortran Program SUBSHED In past applications with FESHM for simulating stream flows, sub-division of watersheds were made manually from topographic maps. This procedure was very tedi- ous and became a limiting factor in the routine use of the model. A Fortran program SUBSHED, which uses VirG IS -formatted map data file for elevation and the stream- coding map described previously to automate this procedure. A raster scanning scheme is used to examine the elevation data, For each cell, the maximum cell gradient and direction with respect to adjacent cells was calculated and the relief accumulated along the flow path until a stream cell was reached. Then the code of the stream which was defined in program DISCRETE was assigned to all the cells over which the relief was accumulated. After the scanning was completed, the cell coding was sorted to remove temporary coding that was assigned during the scanning, The temporary coding resulted because scanning was conducted only in an up-to-down order. 27 -------------- .............. ..... .............. ............ po Figure 8. Final stream-coding theme for selected segment of Haynesville quadrangle, Richmond County, Virginia Because the sub-watershed coding scheme was based on digital elevation models (DEMs) at a fine resolution (1/9 ha for VirGIS database) and the stream coding was based on discretization of streams up to first order, which represents the detail that the USGS quadrangle maps (1:24000 scale) can provide, the sub-watereshed delineation scheme is accurate and flexible for various selections of areas for which the simulation is conducted. Since elevation data is the basis for sub-watershed delineations, accuracy of the elevation data is critical for the delineation of the sub-watershed boundaries. Because the delineation of sub-watershed boundaries depends on the variation of elevation (slope), accuracy is generally better for steeper topography than it is for flatter areas. After running program SUBSHED, the unidentifiable areas, i.e. those with a sink hole inside the area, represented less then 3 % of the total area. A sub-watershed map of the Haynesville quadrangle is shown in Figure 9. The topographic parameters for each sub-watershed were also calculated by SUBSHED and stored in a data file for use by FESHM. 3.1.2.7 Data Group 7 -- Channel and Overland Element Topographic Parameters This group of data is provided by programs DISCRETE and SUBSHED as pre- viously described. 3.1.2.8 Data Group 8 -- Sediment Loading Input Data Since the sediment loading component for FESHM is not completed, the support for this data group was not included. 29 -------- -------------------------------- ............... .......... bL IOLL Figure 9. Sub-watersbed map for selected segment of Haynesville quadrangle, Ricbmond County, Virginia 3.2 Map Editor 3.2.1 Functionality The Map Editor was developed to assist the user with creating and/or editing map layers. The following functionality is supported by the Map Editor: � For an available VirGIS database or a VirG IS -formatted database, users can analyze the impact of changed conditions (landuse, soil, stream network, etc) on surface runoff by editing one or more input data layers. This is expected to be the principal application of the Map Editor in local planning. � If a database is not available for the study area, or the resolution of the da- tabase that is available does not meet the requirement of the analysis, then the Map Editor can be used to create a VirG I S- formatted database. This step requires limited knowledge of the VirGIS map format and no experience with ASCII file editing. 0 For landuse and/or soil type maps, an option is provided to edit the ASCII coded attribute list while the map is being edited, which greatly simplifies the data preparation procedure. 3.2.2 Use of the Map Editor To use the Map Editor the following six steps must be followed: The user responds to prompts for input and output data name (for example, STREAMNND). If the user chooses to provide only the data file type (STREAM), i.e. the extension (VND) is not included, then directory DATAFILE is searched for all data files with file type STREAM. Only the file type having a file name extension as specified previously will be selected. The original data layers are protected from overwriting. A mouse is used to select the editing window. The user can repeatedly erase and re-select the window. To help locate the window, coordinates of the upper-left and lower-right corners are always displayed as the cursor moves. When the window is selected, the entire map will be copied to the lower-right corner of the screen, and the selected window will be enlarged and mapped in the largest possible square area (480 x 480 pixels). Grids can be attached or removed from the window by pressing the appropriate mouse control. The 31 transportation network, also, can be attached to the original map to assist in locating the proper window. During editing the user is prompted for one of the following two options: � Editing-by-color -- A total of 16 colors are supported by Metawindows through VGA. When the data range does not exceed sixteen (i.e. number of attributes), such as for landuse, stream network, and stream order maps, the user can choose editing-by- color mode. Using the mouse the user can pick up cells, erase incorrectly retrieved cells or draw an area boundary and then fill the area. The user then may choose any available value and then replace selected cells by picking up one of the color boxes. This procedure can be repeated until the editing of the selected window is completed. Figure 10 shows an editing-by-color screen. � Editing-by-Values -- For maps with the attribute values greater than 16, editing-by-values option can be used. For this option, the color boxes were replaced by value boxes. Ten values boxes with the value of 0-9 and an additional box assigned a minus sign are available in the value box area. For selecting a new value of 24, the user must pick-up the value boxes 2 and 4 in sequence, while for selecting a new value of -9 the user needs to pick-up the value box -(minus sign) and 9 in sequence. For this option, within enlarged window, cell values are displayed at the center of each cell. Due to the limitation of the screen size, maximum row and column numbers are set for the display window to insure the visibility of cell color and cell values. The maximum row and column numbers for editing-by-color mode were set at 180 x 180 pixels, while the maximum row and column numbers for editing- by-values were set at 100 x 100 pixels. � For landuse and soil maps, the user can edit the ASCII-code landuse attri- bute list or soil attribute list white editing the map. This is accomplished by pulling down an attribute list curtain. The existing attribute list is displayed on the curtain. If the user adds a new code to the map, then the attributes for the new code can be added by answering prompts via the keyboard. For example, if the user adds a fourth landuse type (for example a different crop-rotation), prompts will request all landuse attribute values needed for landuse type 4. This procedure allows editing of the attribute list without having knowledge of the attribute file format and without having previous experience in ASCII code file editing. � After editing of a window is completed, options exist to edit another window area, to save the edited window, to edit different maps or to quit the pro- gram. 3.3 Menu System 32 Figure 10. Screen display for editing@by--color m m m m m m m m m m m m m m m k Fiqure 11. Main menu options The navigation through the functionality of the package was designed using a varied mixture of menus and prompts. Selections from the menus are accomplished using a mouse-cursor tracking system. Three levels of menus are included. The main menu (menu level 1) options (Figure 11) are described as follows. 0 Display Maps -- This option allows the user to display all VirG IS -formatted data layers in a color screen. The themes include: E Stream network map; U Stream order map; W Elevation map; N Soils map; N Landuse map; 0 Preliminary stream coding map; a Final stream coding map; 0 Computer generated sub-watershed map; and Hydrologic response unit (HRU) map. The map display option allows the user to view and inspect maps and to identify the maps that are needed for an analysis. 0 Search Files -- This option allows the user to search data files by file name extension. A second-level menu for this option displays all file types. Once the user selects a file type, a third-level menu displays all existing files with the type selected and allows the user to list the ASCII files on the screen. 0 Edit maps -- This option allows the user to create or edit VirG IS -formatted map files. For landuse and soil maps, this option provides the user with the possibility of editing attribute list files. A detailed description was given in the section titled Map Editor. 0 Create Rainfall Distribution Data -- This option allows the user to edit or create rainfall distribution data by using either recorded rainfall data or de- sign storm event. A detailed description is given in section titled FESHM required input data preparation, Data Group 2. A second level menu for this option allows the user to choose from recorded data and design storm data. For each option, the user only needs to respond to the prompts through the keyboard. 0 Create Program Control Data -- This option allows user to enter program control output and simulation control options. A detailed description for these requirements was given in the section titled FESHM required input data preparation , Data Group I and Data Group 5. 35 Computer-delineated sub-watershed -- This option allows user to create sub- watershed boundaries (element) map, routing matrix, overland and channel topographic parameters needed for FESHM simulations. The map databases needed for this option are stream order, stream network and elevation maps. A second-levcI menu includes the following options: N Select input data layer file names; N Preliminary stream coding (Program STREAM); N Final stream coding (program DISCRETE); a Sub-watershed delineation (program SUBSHED); and N Return to main menu. Select Drainage Area -- This option allows the selection of the drainage area for the conduction of runoff simulations. When this option is selected, a second-level menu displays the following possible datasets from which the drainage area can be selected: N Selected from entire Richmond County, N Select from Haynesville quadrangle, 0 Select from xx .... quadrangle, These options are provided for the users to select drainage areas from relative small area in order to speed up the drainage area selection procedure. If a quadrangle is selected, utility program EXTRACT is used to extract the data from the county data file. After the area is selected, the sub-watershed map for this area is displayed on the screen. The mouse is then activated to allow the user to pick-up the the down-stream node of the drainage area. The routing matrix developed from program DISCRETE is used to identify all up-stream elements ( the influencing area) of the selected down-stream node. Then the area map will be copied and reduced to the lower-right corner of the screen, while the drainage area map (influencing area map) will be enlarged and mapped on the main 480 x 480 pixel screen area with all the non-influencing elements painted a white color. Storm water runoff simulation -- This option allows the user to conduct the FESHM simulation based on the drainage area selected in the precceding option. If this option is selected, program HRU, EFFHRU and FESHM will 36 be executed in sequence. A second-level menu then will allow the user to se- lect the mode for the FESHM simulation based on the a Stand alone mode, 0 VirGIS database mode. When the stand alone mode is selected, a third-level menu will allow the user to examine Group I - Group 8 data files. When these data files are not complete, then the user can exit and prepare the data files before returning back to this option to execute the FESHM simulation. For the VirGIS database mode, a third-level menu will allow the user to examine Group 1, 2, 5, 6, 7, and 8 data files and the input data files for programs HRU and EFFHRU, soil map, landuse map, soil attribute list and landuse attribute list. If some files are not complete then the user can exit and select other options to correct and/or create the re- quired data files. When all files are ready the programs can be executed. During program execution, a message is displayed on the screen to inform the user that execution is in progress. Display Runoff Hydrographs -- This option allows the user to display stormwater runoff simulations. To provide the capability of comparing sim- ulation results from different input data or from different locations within the same simulation, multiple hydrograph displays can be displayed. A second- level menu gives the user options for displaying the runoff curve of the new- est simulation or displaying the runoff curve from the previous simulation. When the newest simulation option is selected, the drainage area map is displayed and the mouse activated. The user then can use the mouse to select the appropriate channel or overland element for which the simulated dis- charge hydrograph will be displayed. When the second option is selected, a third-level menu will display names of all previous runoff simulation files. The user then can select the appropriate file for which the runoff hydrographs are to be displayed. The corresponding drainage map for the selected simulation will be displayed and the mouse activated so that the user can select the appropriate overland or channel elements from the drainage map for displaying the newest simulation. To avoid memory problems re- sulting from excessive simulation files, an erase file option provided in the second-level menu can be used to discard the existing runoff simulation files that are no longer needed. A multiple runoff simulation curve display is shown in Figure 12. Exit -- This option allows the user to exit to MS-DOS. 4.0 SUMMARY 37 --,. - .I - .. . @.11. .1 ... 1. 1. - - - I I I-- ... I @ . . ' .". .. . . . 1 I - -@ :: ,: : @;:Iii I@; 1:4!:. @ @:@ I ::.:i @i; @ .: .1. , ., :.:..!! -.1-1. I@I . .. ., , -.I..,, 1.1-1..jl1,j%!:j::ir;.::;t f::@@!!, .! :;@:,::1-: ... ;:-.. -.I - -@ @I,i - I... -@ ,- - I , .- @ 11 ,,,,j@,--- I.....@@@ @... ." il;-.. 1.I@,@I.. 1. .. I. @ 1I." .. -. 1.@I. - -, I I.. .;-.. - I .""" 'I-. .-@.I... 1...11I-1111-- @-'.@ -II..1. @ . II I--, @ @ @ I - I I"Ill-".. - - @o---, .... ... - 11If -.1--l I...1. @ 1 :4- ... .... @, -1, ....-I .1. ... - .. .. , @ ": :1 ., f -,-, ---@-... -::iE.t.:t@l";@:;:i@!!!t@@@!@i@@@:!;@.@@@@@@@@@@@!!@!@!!@!!!@@i;!@,,., @,@ @,;-l.; 1 :l:;!:J ;i-.@ @,::., ....., 1. @ ,1 ...'....-, .1. 13. I I.. I......I., . @. @;; -. I.. .--..- . .11, , ", .-..... - I., I I-1. I.. @ . 11 @@I 11 .... .. .@@ @ .--- @ @I. .. ..... - -1, . -. .. @. -....'...'.." .,- @.@ . @ @ I I . @ , I.... I... @.. I .-I.I......-I.- -.,....,. . @..@, -. -1@- -..-.@@..:%.1- .. ..... .I"'., .. .. @: ;.,.,.. .. ,I-.11I,. I.. ........-. -,.. ---@-1.II...I-; -.,.-...-.- - @ @ :.:., .,:@:. @ -1-111-.1. -1-1-I. @..@: ;,-1.1 :....,.. -@.s, "', -;--..-.:-,:,.-:!. .1"....-l-, 11 .-- ...- @.... - . ---@ 1-.1.1-1 .. .... 1. --..- ....- - - "..- . , 4: i:@- --;- ;@;!@,i @;!,:I:!@::!!:Ii!ii@il@@:@;@@:@!!;i!!!I .. ... ..,1.I"....".-,"I''. ., ,,@ -@.I....'' ....-- lii@t:F!P` ''. "......T:--..'.. ... - @ @...@.1.1 ...@-i,n .. 1-11 ''. I.-@. -.1-1.@.-I..... . .-@--. .-.-. - -,:33 .... , i @ @:@;, -, .... - @I......... - . II . .. -1 " @ -.1-11 . . . . . . . .@. @ .:, .1-1 , . .. .I .-.." -@.1.I....I...,11.1. ...1-1-1 I . . ,. -- I.. "'..1. @ :..... vi ,. .1 . i @.. 11 I.11 1. 1- %::::,::.1.I " I I I,,ii@@@@@@@@@i@!;@!!:@@@!i@@ill@i@ii;@i;@i@i i@T@@: .......@,-.-. .,. ,:1 -- %::::I..-- -,,,- ........ @.. I.. 11 11 @ -::-t@I..... .... ". ""I ,:1 ... ,", @, , ,:: ,,-@ :,3lll:I ...,-", ,.'...@,, . - 11.1.@::i '.1 "....111--.t- ... --@III'll .1 I-- -@ @I...... .: @, ,::.: ...- -.1-- . I... .-..@;:::II I-,.: @T: H P!!11 il@@ @@i@;I@ !!@ .::.,:.,,:- .. @. I'll... ..... ,@ @. I1: ::I ,.- @.@@...-II - .1-... -,@ 11 -S.. ....I,@11@.1---@1 .1 @.@, I:::--I I..-.1.-.-. 11 -1 -.----,, .....'.. ,II@,, --'..I -I.. tl. - I@.1 ...-..11...@ -,---v -I-.-. @I,- I. . . -, , .., @@...--. @.- I .. .-... 1. .11, -@ -.1-1- -,,. @, .. ,. @. -:..: -1,I @;- 11 .1 .. @. , @I... . 1. I.I.... I .1111, ....@.1. @, 1..-- , '.......-I . I 1. -- , I '' ". ., E ,11 1. 11-1- .. ....- .. .--@... ... I -- 11 . @-1-1.1 - I.. 1. 1- -1 -:H! @Elj:om:.: .1 ".1,.I...@. , l:tl:I.,;!s, ! ,: @ t,:-... .1. :-, V.- @ II."I..,. I - .- ,1 1;-;I....--- - -.1-1-1. @II ". .- ... ,I@.l@ V; --... - Ili.-....-I...... 1111- ..@I - 1. I - I.. @ @- I.. .. @. I- , I.I-. ''. ,@ , 1: I .@ .1 ., . -- - I ,;:@:,;; :::: .. ....- I@@.1-@. @,@@;...P:;I;. j!!!;!ImijI:It, l@:;l%i:!:F! N! iii,,.:@,I...@., I I,,..@..@ i:;@l!@@:@:l@!@i.@:...@:@l@!:@l@l;i:@@!:i:@@ill@.I @. LATO . 1:t@Y!T, @i;!!Ii!i:@@@@@;;ii,;::@@!@!:il! ,111. - -I-,,,,- - I ---1- I.;@.- ". T@ ... .1 - iI.III@.:I It I:: . I-.II-..... -, ; !.I --.1--,@ -.1- -1- , 1. @..] -...@:: t::. @ @,I.- ... a ,@--J. -II. @. !!@; 1:!1:1!!@j@ -- I !@@Iollik!i -;:i@@Uli!@!--:- ...... I. : i I: @ I . . . @ I. . ,.. ifii ILY:@i:!@!:@IJVI.jj;jl A ill ::,: -,..---' --...-, :,I ... I ". "'. ..... , '"' "....... --;I; @. . I @ @. I I -I..,..,.,..@1, .1 .1...@, ,..@i,.,.@@.@..j.3I , I@ ,, .I, -". @ -I .1. . ,,I@ - - @ ,, T; I.., .@.. .1. " -, , I- - -"IlT .. @. 1. .. @IlT . 1.II;@ @ ,.I....I.@11I::: liIt: i;iil; .II :i: I. @,; ::;@, !!1@: :i:@.it@@@,:.I 1:i !@ HIFi!!E F.:@@ @::@1,,"I,I.I.. .@.I.,,,., II.I..I @r -.1@1. @ :: @ifl:]Jh@i!r@ it.... 11 . 1-1. @-- 1. I !I:;; - -.1.1..,I, --@: %:: .::.:, ..".,... ....', .....-. ..... i, 1-1.1;: l@ ii@tI@I..,@,@Il:III:;:l:%,HTIIll 1: iikl! ;;@1i@I! ,li ilid:jo@ i@iii@,@I"!I1w, %..I-...I@.1 @@I.--, .:i@ ;::- -:. ... .. .. @ . .. I-- I....@.@'@..@@:,.;,ii.,@,.,....@,@'. ..... 1. 1. .1 . -@, -11.....@@;!@!@;::!II@il;!i@;@! il i@iiiI: I;I@:@I.@IMl@ 1i ll @iI!I,@I, . . ..lI`@11I,@... 11 II"III-,.@. i,...,@,,,II. .I11..,,.I-II, ---:I,,,1 fl.Lln I !:, :.... I,-,@ l, .1. .1 .... ... 1. ,,;II . ,.@ I.. "I@5:I@. @.-- , I.I I .1 I-- .1 - ,.. 1. E I I @I,L:-: ,::@;E ii, - - ";:: :-,@i @@:!!@!!!Iit!i@i!l@;i;@@i@@@:;@:@@@ 3!;!@Iuiiiirilii@- ;IJI!lmwi@i!!H@ 1. ,..".... ;1 I .1 I ::.::r:::: :i , @ @ I, ,.. .,.- @ I 1. .@::! if: !! @@I'! li "I1..; 1....., ::.,::A..:..I.....,.@II -:@1. ., .1 ,::.::::,:.,,,.,,@-..,".1.I-...S..I@@;! !; iI:if! q I:! if:!1. "..@,...I..I.I..I.I1...II.-@1II I,,,@: @, t:@:%1; h;@:II,1@1@.@11-;:.: :., :@hI@iII:: @,:;j:; ,lIi.I@. .1 11 . . ...II:I:1. .:I.: .:....@.II11I .@i.:,.:,::; ;@I:,-@lI.I:,-,:I:@@Ii!@ f.A11@..@ --.@1,.@@,@.. @.,.,I..I.:@I.I".."..-..1:1-I: @: Hill -:,-,,.:I;! ViIi @.,I@!@:; I :I:1..:@1I!H!I11.I..-.S@@.1 I,.1I@I,,@:@:;,@,,II,1.......-@@@II..@I. . . .. . .@.,@,.,ii@i . I- @ @@@:@@!@!@;!!@!!@@@@!@:@i:!@ii;::@i 1;@@: @@;! ,@j .. ..... -.1, @ 4 I-E .:.:I : t , 1 @i:,; 1.11,11.1 I -. @, t.. @ .." - I -. - . . .., I . . ., . . .. -, . -11@; . ", ...... I Ill III 1 @:::vli.,] . . .... '.:.:@.@I.@@-.,,I:II,"IIIPi i:I;;: 1.I.-.:I;-.;I!:Iillh:i!;;@@i,,,@!]@::@..@II.I-....,@I, 11I;.,....,.@.@jI.@ :... . ... .... ... I .,.i@@:@:, @, . I -1. -,,, @ !!! V!!::!!@; ii@ii@:f !::;:@;:!!i:@@,I.1 @ ..: @. .- ..1 ;iI11-, ...@. 1,..I. @, ;:.:l:I@I@i,:@K!I@I::.-:II:;,1:I1@;@ ::@! :: Ill, I::,!@j);1jit: 11j@1@@!@ !:@@:1: I! i; !11, j% !;...@..1@@@I,I.:,I,Hit ;j:1!i :i !; :@ :j:III0: ;1 T! !I :tti i!! ii@!i;i :1i1!ill;I!::IiI;I I@Ji@ :r l'!II-.....:.....I,I- :1-11 ... -i: i @fjv I VIA iI@:@E E7: ..... 11. @@.:-..@.I...I.-jI:. !.tIi.1 @I@Ilff: @l I@I!;@f; -,iidilivi !. @t!::.I ': i:!!;1:.-'. @, ;lI, @ I @l @I.it,:1 I,I@ :-1. @@-1,;;I : I I ... ,I@-!iFil i@ @tii@i:,;:,!!!!,!@E!!!:!:!!::Itii@@,;@l:: -.,@,.:,.::t,I1:..@.@I.:@..:..I, ,.-.I@:: I:zlj:ji;:@ jiI_@.@ @j:@f @j;lj,. I.I.II1. ... -.. .1 ...@@,-@,@..,.I@I,:%@:.@,@:@-@:,-J,0h.t,,,:,:...@@.ii::v.;Ii@Iiis; :,@ @@:li@t@f ., I:! :;h @!!:I1@t;.@@.I@:, ;; :. II,..%j::::;:@ ..@@,:I.,t."E,1:;,i@I,;11: 1;@ @i liIii @II@i, i. .-. . .11..I@ I,@.-1.II,@II.It@ . . ...I.@.I@I@. . . . . . . ... ...1@ ........-'.@I,@... : 4 .I:@:I,.1II.;., I"::,... ::.:.:. :.1:IE;:,'!i@Ii;I;!1I11EElEI:. @!;:i I@@ f, ;iIiiI@@: !"!I1;i iIi ;! @Ii t; @:; @!,@i@@, I@III : I%III..;,@:1:: i:l!,1!i:@!j:1I.1I!@z:.;fii;i!!i itIil!@ i:!;@ !@ ;l!@:IIIt.,.I-:,I ,@ .!,I:T.!11ir :, @ ,i.I:, t. @,_@,II,.:.@@@::I,:@!I!!@ IYI@i:@l@@@@!:@:i! !@!:! !!!@!ii !!i;@,i;:.1:@,I::4: :i Ill.5-.1-,I I.@.III:1.I:....1@@!.I:@I;@II!: 1,1IIII1.I-.. @@,@.. I I I..I..@@., ,-:,::;:::t.:@"I"I@!Tyriil@ -I-II11 ... .. .. 1..,11.@:! ijf....;;i@i! !11 !@i @! l@ !; T! @! YJ;!@:Ii:@i 16@: :@:@,@i:i@!!I.1 i:li::@: !i;i ;@i t.i:. !I ::I II.1.I iv; ;@ ;: @-:@::,@ :i1N!J! i;:!: :Vi@ tj@:;;@!.j@,1:A@iE4 i@;::II@t: @.-,@;:Tip1!j!Ii:It:-.III@.@.,.lk@ !,@,@II;!I.III:.@, i@:,!::@:3!. - @::Itt.I.I,I@,:;.1,II.: :7 .:I!@;1,,@;!J11 i, :@@Iiii i@@@!,@ ..,..@..@I,.!I i.:1:@--,,-@II 1..j,"i: @iI@!: 1, 1:1 i:1J,iI;i: @.i:! :: ;@:! @I !@ ,!!1:@i:;,@!::: ::::!!i ;!1 @@1:,@_t.:::@..III-,: ,!I:::: @ -1.I . I... ...@I5.!l:@.2@@.1i:: I@ !I;:,;.I-.@;@.@-@,. I 1:IT;,,IIII;I:-.@il @jj:; i: @jjjt; ii i:@:iI :: :"l:-,::@1:-I,.1I....@.@,@iI-@....I I.I:..Idig:.,,@,-,:,@II I I.I....-.@;@:%:-:: I ,,::I:! .!i,i; @,I,, ,;I@-Ai::1.,I @.@,-;@,EI:,@:tE:.:@,,II%I1I@II..... ..,I'@-.. .1I@I,;,lII...., 1!, :: :@j FIN:@nI@@,:@,,.,,...I..,, 11 ,@@@@@, @@l@i, T!fjj !@;;I@ .1.@,@....@I.I .I,",, =@T:@: ,@ - ,- @. .@- I ,; -i.,i.:-- H - -.V: d;@ ilii4@1@!Tl@!'Tll,::-.: .. . ,kI.!@;@@ltl,. I@@! @ : I I @.I M tltiI@. 11 .1-.@I,-..--...@I.@:..::,,. . ., .. --- . . %@, @: i@ !rl@i;;ii ;@,@,@,!@!!I@iTIJANI , . , lF." I I;%%I, I ,...i. -1- I . I I@.@.... ,@ @,@1: ;,:@;:i;ILI!: E5 @: 1 !,I@I,2,;%:I:..,I.1,@@,t,!::1..,I.I@1@ @@] @l@@:@1@@Pill 1:Iii@ :i.!;iI!, :;T...AI.@.. .,::@;:,1,.. i:1.i4i,@ Iiiii; i; iii@@iiIi@@@l;!!::.111J@TI@11@i ii i@i4@::@I.; @! :] i: if!; y, qidi:1II, :: . ", ,. 1. .1 ..I..I@. . .:i..-I.I, -..IIII,.,:,@,..,1; ;,1.;ji@ ....@.....-,,.1t1III.I.--1...:@ ::-:@I@@II@.I11 1. 11I........:I:titi@.I:::, @, 't I !@::I@I :,!,:,.;@:.I:i.I@:1;it@;!I1: @i li @iIIvH;I;;!!Iti-.II7:@.:: II-.. I..;:I@!i@::I@@:@@;,,I. ;@@..,..I:I!,-...--,I,.@II11.1,I...I@.1..I.1,-@,.1.I::I..1.,::-- :- @,,@. . .tt-@- -1I11,@,..,,;I f:@!:;;.:1,::@!II4 i: @,I.,I:i,.:I,,,.11. . .@, ...,"I,@;: 1::::,:@it::@::I@; @l @, I!!;1@ !: I @@I @@1!;:I;;: :; !I @:i;:l:@@!!@:. .-, I. .... ...,, ll,@ I T:!: rh I I:::]:1! Fir qij:i ill:! ,:;@] ,14:,@@! i;l . .1. .I...... 1. I - 1"... .:...- .. -.I@-:: E: :. @.IIi,,;:,:@@I. @@ !@!A. i: :@.@...@..I...@.@@.I.I..I@,,- .:1-.I : III'I !. ;U-Eli. :.:@.@:@1::1@@ :1nIiI@II@]..@II,I..--- @...,... : ,...1. ,....,@I1.,.II@I. . .I.-I @.1,@.@,..,,@11-1. ,......I@, 11 I I. .. . . . ...:@,I,I.....@..III@@I;,..".. ..,1...,I@@;:7@:::@] :E :! .;@..:.i. It:.,I,:I; :@,l! ;: @@:!!@, ;,@:@ P@ ;j:; IAt!I@ i;I:@1I:@:I:,!,I@.1@I.I..1. @...@.1,, .I., .1.II,..-@@!:I,,,,,...I,,..,1.II..I.-I,,.@,II1. 11 . . . I.II..III@,,@--,.,III,.@.@.I...I.. .-:.I1..,.1-I-,III.IIIII 1. 1. .1I......-....,...I.,,,@.-.1I1.I.1 ..II.. 11.II., ,. .,...@,,II1. .1.;I Ii@ il@if :@5 @ ;:I::I@ :;!Y1 !ii!::@@ ir :::@I 1..,,.@.,,@.: .:@;. .,,.@,. 1...,.@.II,;I @,1@,;.....@,...I-.. @..II.1. 'I 1"! I!II,:It@'.,,,,,'I ,I,...,l, ;IItI@1,@@l@I-@: :,iIIii III!1@@1..@. .. .. . .,":1I: @@@I@I@@ !.::@14 I!@::,I :.i.,IIII........I-I11-11 ,. 11..1 I..-,@,,,.Ii!IIII-::I@III@I.:;.:%I.,i@:@@@I@ IN:Oi :I!11@@i@T!@!@I@!@@iii.,.....1.II1.1.1I@II11..1.I.. . ..1@II......I..Ii,,z:@@@@7f:@;@] illilililuli@l v1i,@' @@: :!q.l::li::I@,::: I...I1 .1.-I@,.1. .;I.,..1..@@-::,,,, @@@:,,I1@Nll@@i rl@@l: ,!l@;,@. . . .:t,@1,II.-I...1...1 @.@III11;I:.:%:ti ti@ .. ,,.. -- @ I I:, i ". @ . . -. . .15@ I I,, ,., I. , ,.1.I 11 .1.1 ...... - II ''..''I.-I, ,@II I-. - @ @1.1. ,....1 11:,INnit :@,:. . .II...1I.@@ -.:1.,:!:@@ : :: t: I;: t@I!@4:I Ji!i@iAp @,;,..,I:.,I A,It-l@,,z:i@.,III....@@.I..II..@......I I........ 1.,;.I@@@n::;, ,@,-,, ...:i .1 t:I.II,:IIII-@.-.S@':,:1I..I:1, 1;,:I '!:Eli - . . I @".. @: I . @ . . --.. ,.. I I . 11.1 -Viv 1;I:: 11 :@:@:@@iii@@@!@@!@!@!!!Iiiil:lil!@i:i:i::!@tiii@ @!:@@ !@r!:i --.. ,,,,@I@......I -11.:11 1..1..II--III11I.I I I 1. .@..I:::@....... ,- ...... ... . . . ..I@I. . . ..@ ,i@.,:11,,,,...@.1-@11..I,1. ::i ., I, @ @i :1 r@ z@ i:I , , 1 :@, : , :: @:!:4 .; -., .,!;I i! i: It I t @ @ ':!!i!v!]2vi @ @;@i:@@! @111;!@Yll @i:--.,.1. ., --, .-II: :It,t-,:, .,@:!1 !:, ;::.II1II..I@ I I.... a I@- ,.II..4.@@I-.I.1I@..@.@1....,II,....@, @, - 11I..- @@t,@III.1II.@..,,.11...1..1I@@..I....II'- .... 11.I....@I@;@:@I @:!1 1Pi :@II:t t,, .......I..@..11III11..I....II..I ;:,I.7.I..1; :;@-... .1..,.,...1I.I..I,.. -.@I%..I...1..,@II11 ....... . .,-.: @.I@1--I,,:I,@.iI:I::!. @t@:!I,II4II@@:;@I:t::i;IilE,11 . . .@@II1.....@..1..1@,@I ...@@,,I.@,,. .1 .1.-.I@@,@I1,I.".,. :I Ill;1 ._@@@!:: :i@ jl: :I;i@@i :. !! :@ @@: @@@;@: 1: !@!jjijjj .....I@@,I!;:iiIiFH;i!I:4 t@Ii:@ @3:@:,I@: :!,@ ::;i@i fllwy :@ ,,1..@III.1I.I..@4..... ..-11.I.I..@.;1; :l : i; F! 1, 1: :!II .,. . .I......... . . ..I.@.I.@.@,,S.......... .@-..,..,@.,,1..I.1.I.@1.@I ..,,,,-........I-@.1.. . . .,I , I I ! i@ NIith !:I @... @ :@; @@;:! i,jjt@!t;ii@l i @ :@!@: : I @@! i:: v i:.,,.@ :L!;:;FiJiiihiiif@i@!!:!i@i !@@;I 1,11,14l'on. @.I-. -, .1..,. ....I,@@,,,;I I.I.,.I,"@jI@.....-I,,,i,,",.,:-;I:@i @iI:ll::@:: ",,@, @:,;F1IEi !@I:;@.@.@.. 1.@@I@,.."..@ ,:Ii,:I,jt.j.I.t.l:@@;,lI:1:.@, -@t l,@@v:1,I.,@".@.:'.:.: .::.:I:,,@! N@!;,LF..,I ,@-::.::.@@!: ;, @ ,.:11.1..::,t.:I@.. -i 1@tII.@,@1..1.@.@::II'I IIt:..@.@@-11IillI.@..I..1@I.,%1,@; lP;ltI:I@@I!,ll;ljvfinI%1:1@il.in: I;@ I I . . I1. - . I-- it,11 @ @IjI.. ,-. 1". '11-1..., @I:I:,;;::@I::I ::7%.,1@@!TKMK@..-I..1;:... 1...Ir.1 11 ...- @,@,,.. ....I.,,... ,:II@I@,II:,@ ,I,:, ::11,1:11I!I EI@:,i@.:.II:1 .. ....... @. @,,......@.@i:@.,!,I.... @. -.,,@@@,1::%,@,I1:J!::.,..:I... @. ....@.III11I --- @::.@ 5@: , I: : 1.!@:@:@@;@:@@@@@@1:1:11@lill:l@@;!!@@;f --,: :-.::. i: :,:: ;:-::@ t. - @ I"" .; il :1 -,.,I@:::.:I19I.I@.I@,,III.I. ..,,.I...@11 1. 1, 11 . .... ....I.1I@.,,,,.1. I......@i.:t:,I.1!I,i%:I:L@h,:,..I.I.:@@:@,I:. :: @ @III.@@ ..11.@,I:I,. .1..1.-I1@;ii:!i !i ;:;:;ili!!;I!!: Ifl ti 1. 01 @! .@- I.,..1I...I,tI@@I@,,,,I@ .1... -II...,.7 11-iI'.,,,I:@I;!ij :@,I,..1,,IM.I.I111 I.,.:%::@:1: !!;J!;:: l;:, :l!!:, !!; :I v! id @@ iliil@I.,:,,!: ,I :oJ ::AL1..I@:1 ,; 11:..,.1I,I. I@.,;!!t! :,.@: :@ :.::@II,I r,::; :::: %,@- : :E,:,@:@,:.:@.-@@,. 1. ...@@,- -.@III;@. :: ;,.:-@! 1: :,II:j::I,-.I..IS@II-.I@,,"III1.,.1. .1 .1.@@ @ .I@,@iII..,I:;.::.I@.,.,III:@ i:!S,II@11III-I.,.-II,.I@@I -,..1.II,III...@-I...II.@.....I....-I.,, III.I..@ -..I@,..4llI:::II.1, @.@I@@.@@:@!: @:@ii;i@f:;i@ :zii @@i@:@@!!@@!:!@I.,...1,. ..I@.@1, 1,i1ii @1 l1l: ii i:i.!:@! :@, @@I@@!lH!! :;iI..I;,:@ ...@.I. -...1..,I,,..I:@@II,. .. .I-I..1 . . . ..I@@, @,I1...@1@, .@ .1I,..11 . . .1...II11.1. 1...1..1.11II.1 1. 11..@II. zi" %. .;,@,@..,@,.%...I@.@II.II@@ @%@iiLllg;l.,@II.11,.,,.. .I.I.@,II II1@ :i :::I,:.,;@: :@,:I:I@ii@ !:;::@@;@:@ @@@ awww.-@, I :. 1 ,@:I@I.I,...;-@I @.1-:-1.@.,I!.1;j !!.I:,:@i:@a,:.... @. ...@, 11-II,.:I...I..,I II..,:F-. ..:: @%,I..:,: :@ ::.@1 ::tI.I t @ I @@;:I:f :;r: 1 @11ili1JJ : i ii : i I@ @ @ @ @! ! ! ! I @ !@ .I ..". ......I:,,:,@@,,I.I...,. .... I,.@, ,I@"I," III. I...IIII. : I.;,''.I.I .. I-@IsI,I @I . , .1.@@.,@@ II,I.,@I@@.@ II. . ....II@I .,I III.I... I . . .I@ ..@@ I@II,, .II. I.@..I...I.@III t:..I@:I.!I . .t I:ItI:. ;i@@@I ,, ,,I.I,, ,....,I, .@.. I.., ,@ II., ,. I.I.. ....: rI.@I ,.I..It,,., . ...@. - .11 1. ...II. ..I I., ,@ ,,,.@,k:Y@I. I Ii., ,,I. .. . ..II I%@ :- I @.@ .@ I.4!I!I@: ::@ @i: 11,1@@I... .1.:i.@II:1 ": :;:,:::.t:: .1...1.@. -11.....,.I:@I:,, ,,i,@.1..1@,.,III:111"... . . .@.1....,.@III-..@I@.1 11.I ..,.-...@...1.I.@. ,:,.,,, I.;L!I.I.1,!,.11......@II,@,,;;, "YI11I,.. .1T!@ @;@i@: @i@i @@@i@@:@@@: II @@ ii: @t:: :@@.@%: :@@ '! 1:.II.vIA:.@@@@1II1.II...... Ii,; .;:@@:@:I%I!; ri!l iil@i !Ii :l:i @:,;I @: I!,I.1 .. ...... @.-.1I,,IA:IIII,:i@@@:I@. !:i ::I:!,B.I......@@@,@I, - -,. ..1..,.,IIIII1.I..I@@i, 11.,.. 1,...1@.....I-11.III.I. @II.::!:!:i !; HE;t@;@ :@,I@,@,;,.i.... .. L: I: ,,.. t@,..@,IIII.........I@I!,I ,,I ,@, t@,.,I ,:1! ];;:!:I I1j: ::LIII..I I..I-I .II.. ,@ , @ .@ ,II..I ...,IIi:@ :@,t:;@: :I:@i :@@ @,,.,@. . ... .... !!I @ :I@ ,1i; I@@;!YII @i I: iI Iri : 1Ili @ :i; ; : ,@ @! ;..I..:: ::: @I II:::., ,,, ,IPI : I , I 1 I 1 I ,1 I1I 1. ,II I: :t::@: :;@il!pli! k! ii@@!i : @@ii!l! .. I.. -,@i:: :,,.I@ :;,,,...I ,."@@II :i @1,II : @ :I@i :I71..,II ...-.......I@ ,@IIE., ..I .-@@I @ I@ .@@ .@ ,,.@@.;:@@ I !!:: :!I,,. @- .@,,@@".,....,@.@I.@. .1II:,I,@:!I'I 11 DI: iii !@I !i !!:.... !;:: @@iI1!! !I 1 , I I ,II. .. --:@J,,..-. @:@.-@... ,;,,,,,.,".1...1..I@ilI,.@I,. 1. .. .....I.,. ..... . ... @, @@ @@ .1 @'-,,I11 I -.I1 .1@.1 . . .I1",@II.. 1...I@,II.I. .....I@11.. ,::,1.:I....:-I:@:-....III.I.II . I..II.1I..I.@.1@.I@11 11,.. .. .1. ..@-I I @-.....1,. ..I@.... .. V I i@it Ji 1 I@I @ @. @!,I!llfilf,.@11 11 fiiil;i !@ l:@:i@ @ I iimljl@iviit]@1:1! !@@f I I'll, ...:,-'-::. - ..@ @ 4, - - 11 . .@@@: :@I.., !o@ ;: :;@ @@:ii@i@@;@@@ i@;@@;@@I@@ @t@@i111. .1..1... .,:: iT ,@. . - 1, @ -, !@@` !!@I!IrTlli,Tlllil @!ttti@@ :!!@f !lf@]J , :. .,%!@ I .t..1..-.. -I- .. .11 ,.,I.@:,.... 11 @!@i:JNX I:@,@: ! I , .! ,:1 Ij@..:i:]@ @1@;II.@5 k@ i; f,, !:J@lhid 1iP!::,]t@!! 1 @:@i 5; -,....11:1:@: v:v-. It it-E, ; ,@@%:,. I :.E.@ , : :I:.:I@"i ij tIIII ,I::: :;t@EIY'OI. I 1. .,:Ii!; :HH: Jrl;;ii@,:@;:@@:!@! :INI.I1@., 1. lividilill j:I -I... ....,@1. . 11 III I Lt:7 1 :if i: I .....-I@ - I...I..-.",@. -.- .@ "',I...t--...@@,@@@:@ ii:i i@@:@i::..;! : a:j i!@:I,..- .. .... 1..-,; ,,I;! :; _@: :,,,:@: ,;:!:.. I !::;1::: :@.,;: @; @;@y T! 1 i1i!i;lNht @@-.1. ,, @I.@.I ,,.. , - , , -:- ... . @ I@., I III.,:.I @I I111.1 I . @.-II . ,!i:i:N;!@ ; -11 ... .-,@,@.v-.@-: !@ @ :I ![@II@-.---.! i;:i;@@ Nuv@ HL:! ;,::! j: I- . . .1 11.:II.I-, i, :,.Ii@z ;@ !l !J,Eid J.:i-i:-:@@ i!@@;@: @Ii@PT1J, li ; i : :i@@ ;!@@Ii@ .@ ::.. ,. I.. ...@. ;;;@i.: I:@ @@I@!!;f!-@!! @@t@ I 1,:,IIi; P:ii 1 .". ... 1, ..I..11 : @ :: :@l . I...,I -.11 .1.I , 7.I;.,@.1I'E:k:@@ !:I:! : @::;i. r:: ,@t... 1,I,@:@l:!:!ivI li!F i!@ : @. " @. @, I.I. .11., -.,@...I:!@ll i T! @t: :;,:, @@ :: @@ .:. -, - @itI11 I I!-.. 't ,:: :::: @ Ii r, :@! @:: :. t - @ I:@: I !; t.IIIIll, -I.I.,1 5@@,@,,.11I,I11...@ .,, @:,:, j@! 1I @Ill lj;j T,:@5.,,__ @ , ,:, : IN- @@ :@@ : @@ @,.- I @ . ...-II @ .-I ..: ': :.I:@. 4Iz::;@,.:@:. ,,:, @.-@.I.... "--1 !@ !t .;. @!': , .i: -I:::!j: !!I :::,@I,, .: I I @... .@i@!i!I:@@;i@@!!,@Ill@l% @,@!!: 11 11I".. @.,.;@,,-.1-1-1 .-1, 1. .I-- ... -1@@ . -@ .11.1.1 ....!!\t:!!:i:,@@ : @@@: :@:;@!!@!!!!! :11!I..@,I, -11. . 1. -I@,I.. ..... 1. @ @.: 1. -- -.., ;.". I @@ @ ,. 1,1 .",;i:!l W::@@-: 1,!Ib:I:I!,J @@@:@7ii@ 1,I..,I I-- .1 .. ".1I@.I . @.1 @::I I .1.Ioh:@,!l , @ ;@!illd.@:;! iiij@ii:!!!!1@......-@ ,@,1@,!;7!F 11 .1 ...... - %.1 - .-I.. --. @ @ , , I - I .1 ... I @.11 -@ I.. . .1. ,I.. .... .. 1. - I I ,.I ,.I..@!-.,@:! I, ,f l.!@ !:l: 11 1. , I I@-:@ 1, @ ;,@,;,@,I..,,-...- 1. .@. I I . - -, -III..,.I, - ...- :..;,.@,.",@ III11 1.4 1-1. % .1:I:: 1 I:vl %:Ik :I : 4 lj!:@:@47jl :!:@I @.@@I:.1 ,, @I,I !, @% :@: i::! I.:,.:-- @-I,.-.@.I@:I- i!!i;; P@IiIi;fl A0;,;@:i:@@:@,! :P! !;!!;l TriA hih ;ill @ i@;@J!T!Jioiii E,@, ::1, I @: i!1 @:V-P.-I-Iiiq-:@ :,@@;i;! llflh;@@:!@IJIII@ti@i@@:@ lii@Oii! --.. .... . @.. . . - - ,:I..1... .... I. II @. ..@@III.:1II I I 1. , . ..-@t:,--,:-i. -:::@-@, ::-, . - @ . @ ..-. .I ,.1 .... ..1.: ..... ..I ":%:.. @ ,@ .I I 1. !. g:. ..1,..I11@@i@I::@::::@! @!@IIJ @i i@ii@@ i@!:@:@!f@!:i kii ;@! ir@;@:i @@:@i!@@:!@ I!@!.irikiii @@k,@@i: li:;;O@ 1:11 If! i @! i ii@lti@: . 1 ::.I. wt.I @III I@:@:: -.1@....... - . .1 .- . @@Z!:@ @ @, %jln@ li@!@I.-II.:@I ,:@@i !@@!:@i 1:@::@:!lI::! 1:11:;j @i@i;;:,@!; 11I.@.. .. . @. .I I11 11..@:@ @@i@.@.Ii. I" ., W, :!!! J:!4:llI.::, :@t;-,@.. ,:1,111, i,::@! , ,: ! I@ IYf::Jr!hj I, ;@::: :: 1 :I @ .11-@",.I1. ,.-.@: ,;@:@@: ;)I.- @.@I I11 . ......... - ,:!:,!@, @@: ! :H i: Pri. .@, l:.:11:,@t: ,@II.;.",."... ----iII -..I@11I ,.,:@:I:.:@...-@. -I-. ... ....@@@II1. . ..-I , @.:--,@.I...III11 .1. . - -.,,.@. .1.:@, I I 1,-@. I I .1. 1. I ,I1, - I 1"..-I 111 ,: :11 . ." ,. @ 1". I ..11.-.@,, ., ,- ,: ,".... -.... I.- .@ 1.1- .. ,@@ -I I .1. I . 1.. I.,.,;1 ..-., .E :i:: :t:: : -I @P:!ii@I. ., @.,. IIIt.:-I .11-- ;,..I.1I.. I---,I "i-11, ... -.- . @. . .@ @. .... .... --- ,.:,;::@ 11,.;.,;:::tI.: .1.), ,, , @: 1. -1-1-1 I . ;1;@.1111, . @. .1 : @:., - 1. , , ..@ @!!!Ti@jijo!;i@iii @i;@Y: @:@;@ ll@:!:@J@iii! . .@:::,. ,.- . . .I . I --1.@IIII:I.. .il::.. .:.t-x1ril: i:l: :! ;:@. :@ ;Tl!!@;! Iv1:P1li@i:::!l1,!:;!:!1I.I..",III:::::: -, i, .. . . ..... ..I.... . . ... "... .. . -- .. , ..1. .It@-:@1. 1,,-.. ...... .-.I... I I, :1.1 ..... . .@.. .-I ... 1.II@,II.I.....--@@,I II1...II. .-.1 II.. . 1. -,:t 1. .1 -..I. . .I- .I@III.11.-- .,. .@@.@ 1,@-,. II .1 111. I.. @.I ... I @",. -..,,1.@1,...I-I.1..I .1.-- .I ,, @I- .111- - .. .1I.11.@@I -....... 1.,@ @. . @ - -I.- .: 11I:-.@I11 .1,- :4I1. @ .---@-:,::, .. .,I.. I'll" .1 I :.: @ :t. :@ ::I;@ Ir - ,l!;!%!E.@:I! @!@@Ii@ ;, ,:, ::@.I. .@; o@t@; :, %@: ,;I :.:@ I:@;\@@i@@;i!@ i@, , ,2... 11 ..1. 11.@ ..,.1-:.@@@ .-4.@;--::-:::,., -.1 1, ",.1 ,-,;I,, j:ih:i E:, @@ 11:1 . . .II- I@@:z , j:ih:i E: @. @. , .," ,, !.!,;!!;,:II -".-1, ,... .@ @,1....,@. . . . ... .. .111@ii: .2.-@ @,M. !:. @@.1. @. , 1. @ I: :,:,- .I11 1..1-1.1I,I,11 -,,@- .I.1. , @I......I:.. -.': 1:I: @ -.. - .,I.,I-@, I. ...@@III....". I .::I@III I1@,I .:-:1.t-II- II@ ..:I 1:I@ @ 1. , .,.,.. .. ..IIII.II.. ......1.,..... @@@I .1-1. .1 - I ...-,I -. . . ....,,I .11.1. .. ..@.11.11 ". -...@ .@.@,. I11.I-.. @ @@",I ... -.1-.!f!@,,,..I..4. ..PT.,: ,: ... ......... .. -.1III 11 I.1. , i:;, i:: : @, @: II I; I 1; 1, 1 i: 1 @ 1 i i 1, 11 @ i i; @:i 1I. : I-@ -.1. .1, @14!:Jli@!!!:! @!l in @; l: ,,,. ..... ". .1-1" -.. ....@@,I. ...AIt9H.,-., 1.I-,1. 1-,,.1 .. .... -.1-1 I. IIII-- I.-, :@@ IIY::-.@II-. . . . .I.. ..,, -.1, '.I", %@,II@. 1-,,,, : . ..,,@, I @-..:1. ,. .1. .1 I.. ', 1:1I..1 .1@III,@,. . ..........1,,,:!:. @:..@.I I@I.II III.::," , .@@ I.,,I . . . ,.. I.I1. i@t!:@%@.,.,II,..13!;lJFJ !:, I:,:,@ @: @ ;::: j :jtj ILE: - @II11 1. -.: -- : . @@'@I,I -...@,.: ..iI,,-1-1.I-..11 ...-I11 .11'... .. .@ @:I I:1 I", @ .I III .1..I1. . . .1. @IIII,. .i.,@,@@ i ii jj)-,1.-'. .@ I I-, '. ., I.-I. -. I:, . ,.: It :@ I -.I ,I. ,I 1. I "... .. I.. @. I .I :, I,@. . . .I:- . I I,@,11.1 1. -. I @ @'. @. I @@ .1,. . . :: ... ...I.. . -I--., .....1. . .. ......I.... .. .:; - .. -.1-11. ---i,1@: :11@@li!,:; ;" :': I!: 1;I@., -. @ . :t:: i:t, .I..... @. -1. jjl@@::@ !!,@@!: !iii@@:;iri@@@@@:@:,@ @I:; !: . :@2:. ,,::.-,.I: - @. . @I.-11-.- I.-I- . 1. 1-@ @- @,.,::t . I.. , :@: ;@% @,; 1ii ]IIIHII . . ..... - @. @ @:,@..: ,@ .@:;.;II.. ....I.I .,-,.. .1. @.,@.. I. .I .:t : i . : : @ , I- ::;: . :@ .1. --@II...-. . ..- .@@,I.@ I11 I11- ,.I.11 .1...I@E I .1. :,:,:-,:-:,,11I@ '@ ... @. , 1. ..11 .... .. ,,", -.@. .1- I,-;..,.1.- . .1. II. I@@-1- I-...-,, ,. ,. .., . @ ,.. . 1-.I-.@.-I.,.... . ,..., --.... 1,I.I1. .@I,-- -.. . -- ..I..,@-II: , .. @. .. ,11 I.I..,,,..., -., J.-,Ii ,: ,'- .:t @:.,... ....IC. ,.-.1.1..1. H,:, -I...,I,11 .11,11..I-, ': : :- ... --I, ,11.1I.@@, ". .. , ,,.1 ... 1.@-1. . @.. . -I,I..I..I.1 - @. @.. -.1- -I..... -1 ..@iI.1,-,. I , I... .. - I,, ..... I I-11:11,II... .@@III. . .......... - .1.I I I."... .1. @11I. .-"@J @:., %: t: @.II...11 11 I.I@ -1 .@ .II,@.I.1.1 . . . ...-. I!,.., @I1.,. .... ....... tk@r@ :"......ii!PII -I.. .1@@I.1... . .... . -.1- I1-,:,.:.:.,. I i:jjjjyj@ii:-,.,@III. 1.I@.II.I I.. I... . ...I @ 1.I@@.II , %!:!Ivi -@@ @ fI !;@ I :'Pid@- ,. o: ". .., 1.@ .@ I -@@I.I.. I ,,.I..I@-,-..@-I@;,:::.: .. , @@:@I; :t,ivi&Im! I I@.7-,,ii,, @ 1--",.11 .1 ......I1; ., :.: :.i:i ,-@.@ . .@@,I[ :7 %:%:;: ::i:::@ -, lP:IiD:@i!:.::, -.. ,-. . I.:: 7@,::.,.@:i @:.@,....,@.-,@, . 11I ... -,,,@ioi@i@@@i@;@t::I @y!pjijl&p! I Il:, .1 :t:,:1i ,.: @.,,. II I, I. .@I@:: ::... I I ..@II. . .. . . . -.1,,@. .. . . . .@.:1-1.@@, -I@.. .1.@': : ,.:.:@-I -,.1I..,@I@ .I:I I.. @, ..I1. '..@@I. 11.1 . .... I:ti I .,@,3- :::: - ....@.@@@ . -1-1.1.- @.III.11 I.-@.I -,I. I. .. .%:,;i .:@I,.,. .I:3.....1.1.II@i I II@..-.@@@,-. ., ... ,. -@.,. .@. :, ,:.-:--ti:i.-.@II.. .1..:1I@@.:,@-@ -:;::: -:1..,,I @. - ..;., ,AT1Ti!Tiii:ii:t :, I II I. I@, @:@ 1, ".". -.- .II.@I...-I... .I- ,,.I .. ..... ...II,,. 11 .1..II-I...-. . ... . S11-1....@-I..1,II . . . . . .,;.@ ....I.. ..I..I@@-. . . @ @.. @II.1 . . .. .1. I 1.11,@-I@.E1tt z, , ,--. . . ..............@Is,I1. .!Ij.. t-,@- . . . @..::@:@@ : ::. ,:-1- ...... .@ -..11,II i--II@,..11.@. I I @@!@-11.1'.. @i:!@Dli;!Til 'r I @i@.I,I1,.I.II.,.1. .1 .... -fi:-I.i, ...@..-I .,.,.@ @ I,,.1I.." . . .-I2 A: 1:i!!:@ I !,.@.......@@ @ !Ill ii; !NPiiit,.I @@,.. . . .1 .. . .1 .;I !i:!J@i:@ii!- ; E!@P:!:1JHl:Efl:hi i; @! t;t ;! ;j!:;:l:F ]Eiit7@-:f@f.:: @fI.iI@ I:II.@@ -@@,II I,i I1.:@: "'.,"@Ir,II..I I .H:zH:..@.I-.1 ...I. I. @. - .. I:Eti:!@:: :",:.,@I..I.." 1II@II1, .1 . ., 1,.tIII. . .I .. . . . ...:7I II1I. .1-.1-1@,I...@ . @.- . !!I-.....I-...@: I:; f:i;!! ;,T!j!1;Tj1;1!ijIl.t@;:; ,:`;Ijj1-- ... .Ilk; J!@:iiE!!l :!PY111HI11iHi:ii:I:- 1,I1.. ....1.11 .@ 11..@. ,....... . ,@.......::.... ..@...@,". 11 -1-1 ..... - .... . .. . .. .--,-,;I I .. .1 .@- W:, ... ..... @. wl@;w,VTKl:1o1lIK1f t;x%:,-@I - I.. . -..1 . .. . .I... .@IIi@I,.., .1 I.- .... 1.II,: ,.111 .... ...-111-I.-i... .1@I'I,,I ., - I... @.. . @ @ ,II I1".. .. .:@ :!@ ,..II. ... ...@'11, 11 ...... I I@....- @ 1@ @i:,,T; ,@I ., 1-1-I Tn:@@t.::::I!@!! tii:b@tY ;!:ii, 11 . . . . . .t.::@!;@ .,II1.I"Tn:1 ..@ I- ,"I .. ,,@.,..I i-,.@ nt .t@ .I,II I@,,..I.II -. . ....... : I -: I@ -I@I -..: ::II-@@,,, ,,. i:1..... 3@.11 ......: ,II.III...@, @ @..@I I@:@@II...@, @,;Ill!@flN:1;:o!id:4:i1! i!!:@@I!jlll Hill! ll;iii@;:@@:!:;:i@@!!i!!:Ill@iiI il hlij:, :@ 1: 11 I.1I@. .@I @.,I; ,, ;iil@ ;@!!;!@@::;@@i!iilililill:l@@i@:j E;t@@;;!I1I..-- @ @:it:tt@.1.. -...,@II..... ..1I.1 .1I1.@I:;@-.1 . -1- . w.... -........@..... t:t,,: ...@I! :@ : im vj.Yj:i@ij .: !: :;@.."II. ...-@@ -,l;!Aii;:j @:I;11 : I;, I.:,:;-:.I11.1.,IIII .- ,,@ ,.I.ii:i:i,;i@::!: :T@Flfli@!!Yili;Iii@!@l Io:,iiI - .-,.. ..;i@.,. @ .. ....@...@.. ... ..... I.,-, ,-@. .. . - . . .. ... .....,...,....@---". ::: : %L4%.I;...,.I@@ .I.. .. .,.-II@ ,,.....-I. .... "..., @.,,I.@I .- I I " -. .@@@ @I.,.. I,,..-, I 11 . .. .......-I@@ I-., , ::. .; -@;:; .1.I..-.I.-1.. ,-.1 .I.. .@@.;@ill!I!jlil: @,:,III :.... ".,'. ,...*I...... ,... ..t@I.. 1..:::t:t:t:;:: ,,-: ., : II@: I @II II; :,:. ..I.1 tE, @":.., .. :...I::::; r ;:- I :....... -, IlHi f@I :;:,;l:?:i: F: 11:1 .1 ,"'.-',-, @,. ; ;"v I ,@., --..:.::1 ---,:::I: : :,@;J!j: 11 Hill ii iil::@! J!I @iiO llj@I I!;!I,i ,I,I:.::IE,:iI :,i; @:!l ;:I,.t i,E . -;: :::,:@;! TV jtiilij.itilii :If @:; Y@!!i;iJIC.. , %l@:::!:.,.@ :II: : ,@ :.,,i @, tI @ @ ,i ,- I .. -I":@::-I.t@ II@1W: @@ :, :,:@:. :: ! I . : , II:@, : I:1, :1 :::,-j : :.@:: :: . 1. I @ I . .@@..@.II,;.. I11I1,II Figure 12. Display of multiple hydrographs generated by FFSM A Hydrologic Modeling System was successfully developed and implemented on a PC. The HMS consists of a series of modules linked via a system of menus that provide navigation through the functionality of the package. A major effort was expended to overcome problems associated with creating the extensive databases usually required by distributed parameter hydrologic models. The principal issues involved automating the selection of topographic and soiLlanduse re- lated characteristics, keyboard entry of program control instructions and designing a linkage to provide access to all components of the system within the same computing environment. A procedure was developed to discretize the stream segments to a sub-watershed level (as required by FESHM) based on tributaries and confluences determined from center-line vectors of a stream-network map. A raster scanning scheme was used with Digital Elevation Model (DEM) type data to determine cell gradient, direction and relief from which the contributing area for a given reach was defined. The procedure also provided a rapid method for determining element flow length, slope and area. A map editor was designed and developed to provide a simple procedure for up- dating and/or modifying map or attribute files. Navigation through the system is ac- complishcd with a rich set of menus and prompts. Tasks not fully implemented and planned for the next update include the fol- lowing: Automated estimation of landuse and soil type related parameters; Design storm option for describing the rainfall distribution; Entry of user defined watershed delineation in lieu of automated sub-division and followed by automated selection of topographic parameters as currently supported; and Direct linkage between OSU-MAP, digitizer workstation and HMS package; 39 5.0 SELECTED LITERATURE ON FESHM 1. Contractor, D.N., B.B. Ross and V.0. Shanholtz. 1980. A finite element watershed model to predict storm hydrographs, sediment erosion and transport. In: Proc. of the Third International Conference on Finite Elements in Water Resources. Uni- versity of Mississippi, MS. p 6.24-6.34. 2. Heatwole, C.D. 1979. A finite element model to describe transmission losses from overland flow. M.S. Thesis, Department of Agricultural Engineering, Virginia Polytechnic Institute and State University, blacksburg, VA. 3. Heatwole, C.D., V.0. Shanholtz and B.B. Ross. 1982. Finite element model to de- scribe overland flow on an infiltrating watershed. Transactions of the ASAE 25(3): 630-637. 4. Judah, O.M. 1973. Simulation of runoff hydrographs from natural watersheds by finite element method. Ph.D. Dissertation, Department of Agricultural Engineering, Virginia Polytechnic Institute and State University, Blacksburg, VA. 5. Judah, O.M., V.0. Shanholtz and D.N. Contractor. 1975. Finite element simulation of flood hydrographs. Transactions of the ASAE 18(3): 518-522. 6. Kenimer, A.L. 1987. A computer simulation model for predicting pesticide losses from agricultural lands. ASAE Paper No. 87-2067. American Society of Agricultural Engineers, St. Joseph, MI. 7. Li, E. A. 1975. A Model to Define Hydrologic Response Units Based on Charac- teristics of the Soil-vcgetative Complex within a Drainage Basin. Master of Science Thesis in Environmental Sciences and Engineering, Department of Agricultural En- gineering, Virginia Polytechnic Institute and State University, Blacksburg, Virginia. 8. Li, E. A., V. 0. Shanholtz, D. N. Contractor and J. C. Carr. 1977. Generating precipitation excess based on readily determinable soil and landuse characteristics. Transaction of ASAE. 9. Ross, B.B. 1975. A finite element model to determine the effect of landuse changes on flood hydrographs. M.S. Thesis, Department of Civil Engineering, Virginia Polytechnic Institute and State University, Blacksburg, VA. 10. Ross, B.B. 1978. A spatially responsive catchment model for prediction of stromwater runoff from ungaged watersheds. Ph.D. Dissertation, Thesis, Depart- ment of Civil Engineering, Virginia Polytechnic Institute and State University, Blacksburg, VA. 11. Ross, B.B., D.N. contractor and V.0. Shanholtz. 1979. A finite element model of overland and channel flow for assessing the hydrologic impact of landuse change. Journal of Hydrology 41: 11-30. 12. Ross, B.B., V.0. Shanholtz and T.M. Younos. 1984. Using FESHM for landuse and water resources planning. Agricultural Research Digest No. 1, Virginia Agricultural Experiment Station, Virginia Polytechnic Institute and State University, Blacksburg, VA. 13. Ross, B. B., D. N. Contractor, E. A. Li, V. 0. Shanholtz and J. C. Carr. 1976. A Model for Predicting Flood Hazards due to Specific Landuse Practices. VWRRC Bulletin 99, Blacksburg, Virginia. 40 14. Ross, B. B., V. 0. Shanholtz, D. N. Contractor and J. C. Carr. 1978. Computer Model to Describe the Effect of Landuses on Floods. VWRRC Bulletin 85, Blacksburg, Virginia. 15. Shanholtz, V.O., B.B. Ross and J.C. Carr. 1981. Effect of spatial variability on the simulation of overland and channel flow. Transactions of the ASAE 24(l): 124-138. 16. Smolen, M.D. and T.M. Younos. 1980. Simulation of surface. mine hydrology with the finite element storm hydrograph model. In: Proc. of the 1980 Symposium on Surface Mining Hydrology, Sedimentology and Reclamation. University of Kentucky, Lexington, KY. p 41-46. 17. Smolen, M.D. (ed). 1983. Hydrologic and water quality models for agriculture and forestry. Southern Cooperative Series Bulletin No. 291. Virginia Polytechnic Insti- tute and State University, Blacksburg, VA. p 1-5, 18. Smolen, M.D., B.B. Ross, T.M. Younos and W.J. Sydor. 1984. The finite element storm hydrograph model users guide. Virginia Agricultural Experiment Station Bul- letin 84-87. Blackaburg, VA. 19. Smolcn, M. D., V. 0. Shanholtz and B. B. Ross. 1977. Application of finite element hydrologic model to evaluation of nonpoint source of pollution. Transaction American Geophysics Union, Vol. 58:385. 20. Wolfe, M.L. 1982. Sediment detachment and transport functions to simulate soil loss from reclaimed mine spoils. M.S. Thesis, Virginia Polytechnic Institute and State University, Blacksburg, VA. 21. Wolfe, M.L., V.0. Shanholtz, L.L. Rice and B.B. Ross. 1983. Sediment detachment and transport functions to simulate soil loss from reclaimed mine spoils. Virginia Agricultural Experiment Station Bulletin 83-5, Virginia Polytechnic Institute and State University, Blacksburg, VA. 41 DATE DUE GAYLORDINo.2333 PRINTEDINWS A 3 6668 14107 6747