I JJ3.71 10285 N 1 1 a mm iya7 IVf «/f f lUf J w Rivers Study Data Management System User's Manual st;,7e documents coitr FED 12 1SS8 MO ''J HELENA, MOr ,iQ State of Idaho Siat9 of Montana State ot Oregon State ot V\teshington NW Indian Tribes USDA Forest Service USDI Bureau of Land Management USDI Fish and Wildlife Service USDI fsiational Park Service NW Power Planning Council Bonneville Power Administration March 1987 n? RETURf .tviV ^xtiCjiOR^ "^^^^UfsTO^ State of Montana Natural Resource Information System -•*w^ir/u«.iff ' - MONTANA STATE LIBRARY S 333.71 10285 Nil umm 1987c.1 User's manual, Montana rivers study data USER'S MANUAL MONTANA RIVERS STUDY DATA MANAGEMENT SYSTEM Version 1.0 March 1987 Prepared for Montana Natural Resource Information System Montana State Library 1515 E. Sixth Avenue Helena, Montana 59620 Montana Department of Fish, Wildlife and Parks 1420 E. Sixth Avenue Helena, Montana 59620 by MORRISON-MAIERLE, INC. Consulting Engineers Computer Services Division 1600 Poly Drive - Suite 305 Billings, Montana INTRODUCTION The Montana Rivers Study data base represents the compilation of several complex data bases from throughout the state of Montana into one large data base management system. Information pertaining to Fisheries, Wildlife, Recreation, Natural features, and Cultural features along Montana's waterways is readily available to you through this information management system. The master data base is maintained through the Montana Natural Resource Information System in Helena, Montana. Updates to the information contained in the master data base will be periodically distributed to users on flexible disks as additional information is gathered and collated into the master data base. This information management system is written in dBASE III Plus, a powerful data base management software system developed and marketed by Ashton-Tate. Software query, editing, listing and update programs for the NRIMS system were written by William G. Enright, P.E. of Morrison-Maierle, Inc., Billings, Montana. Users are asked to supply written comments and suggestions on how to improve this system either to Larry Thompson, Program Director, Natural Resource Information System, Montana State Library, 1515 E 6th Avenue, Helena, MT 59620 (406) 444-3115, to Janet Decker-Hess, Montana Department of Fish, Wildlife and Parks, P.O. Box 67, Kalispell, MT 59901 (406) 752- 5501, or to Bob McFarland, Montana Department of Fish, Wildlife and Parks, Wildlife Research Bureau, Montana State University, P.O. Box 5, Bozeman, MT 59717 (406) 994-3285. TABLE OF CONTENTS 1. SUMMARY and PURPOSE 1.1. Summary 1-1 1.2. Purpose 1-2 2. STARTING THE SYSTEM 2.1. System Requirements 2-1 2.2. Installing the Rivers Study Data Base 2-1 2.3. Loading dBASE III Plus 2-1 2.4. Standard Key Conventions 2-1 2.5. The Welcome Screen 2-2 2.6. The Master Menu 2-2 2.7. Master Menu Selections 2-3 3. REPORT/DISPLAY FUNCTIONS 3.1. Selecting Records 3-1 3.1.1. The Resource Selection Menu 3-1 3.2. Setting the Query Conditions 3-2 3.2.1. No Filter (List all Records) - "1" 3-3 3.2.2. Geographical Areas - "2" 3-3 3.2.2.1. All Data for the Entire State - "1" 3-4 3.2.2.2. County or Counties - "2" 3-4 3.2.2.3. Data for Specified EPA Reaches - "3" 3-5 3.2.2.4. Data for Specified DFWP Water Codes - "4" ... 3-5 3.2.2.5. Data for Specified USGS Hydrological Units - "5" 3-6 3.2.2.6. Data for Specified Townships and Ranges - "6". . 3-6 3.2.3. Value Class 3-7 3.2.4. User-Generated AD-HOC Query 3-8 3.2.5. Complex User-Generated Query 3-9 3.3. Report Formats and Report Order 3-11 3.4. Report Control Menus 3-12 4. FILE MANAGEMENT FUNCTIONS 4.1. "A" (EDIT/ADD/DELETE RECORDS) 4-1 4.1.1. Edit 4-2 4.1.2. Add 4-5 4.1.3. Delete 4-5 4.2. "B" Update Record (Batch) 4-6 4.3. "C" Pack File 4-6 4.4. "D" Reindex File 4-7 LIST OF FIGURES 2.1. The Welcome Screen 2-2 2.2. The Master Menu 2-3 3.1. The Resource Menu in REPORT Mode 3-2 3.2. The Query Conditions Menu 3-3 3.3. The Geographical Menu 3-3 3.4. The County Selection Sub Menu 3-4 3.5. The EPA Reach Menu 3-5 3.6. The DFWP Water Code Menu 3-6 3.7. The USGS Hydrological Code Menu 3-6 3.8. The Specified Townships and Ranges Menu 3-7 3.9. The Value Class Menu 3-7 3.10. The AD-HOC Query Introduction Screen 3-9 3.11. A Typical AD-HOC Query Generation Input Screen 3-9 3.12. The Report Order Menu 3-11 3.13. The AD-HOC Index Generator Screen 3-12 3.14. The AD-HOC Index Generation Input Screen 3-12 3.15. A Typical Report Control Menu 3-13 3.16: A Typical Report Control Screen During Print 3-13 4.1 The Resource Menu 4-1 4.2. The Edit Prompt Screen 4-2 4.3. The Record Selection Screen 4-2 4.4. The Edit Overview Screen 4-3 4.5. A Typical Edit Screen 4-4 4.6. The Resource Menu in PACK Mode 4-6 n LIST OF APPENDICES A. FILE STRUCTURES A.l. Data Base Files A-1 A. 1.1. DESCRIP.OBF A-2 A. 1.2. FISH. DBF A-3 A. 1.3. REC.DBF A-4 A. 1.4. GEO. DBF A-7 A. 1.5. NAT. DBF A-8 A. 1.6. FOQR.DBF A-9 A. 1.7. WILDLIFE. DBF A-9 A. 1.8. AREACODE.DBF A-15 A. 1.9. COUNTY. DBF A-15 A.l. 10. EPA. DBF A-15 A. 2. Index Files A-15 A. 3. Query Files A-16 A. 4. Form Files A-16 A. 5. Program Files A-16 B. TABLES USED IN CODING DATA B.l. Codes for National Forests and Forest Districts (FISH. DBF) . B-1 B.2. Codes for Other Land and Water Based Activities (REC.DBF). . B-3 B.3. Codes for Value Class Rating Reasons (REC.DBF) B-4 B.4. Codes for DFWP River Drainages (WILDLIFE. DBF) 8-7 B.5. Codes for Wildlife Seasonal Use (WILDLIFE. DBF) B-9 C. SAMPLES OF REPORT PRINTOUTS C.l. Value Class Summary by Water Code C-1 C.2. Value Class Summary by Reach C-2 C.3. Resource Area Detailed Report C-3 C.3.1. Resource Area Detailed Report-Fisheries C-3 C.3.2. Resource Area Detailed Report-Wildlife C-4 C.3.3. Resource Area Detailed Report-Geological and Other Natural Features C-5 C.3.4. Resource Area Detailed Report-Recreation C-6 C.3.5. Resource Area Detailed Report-Cultural Features . . . C-7 C.4. Straight File Dump C-8 D. LIST OF CONTACT PERSONNEL D-1 LIST OF TABLES A.l. DATA BASE FILES A-1 A. 2. INDEX FILES A-15 A. 3. QUERY FILES A-16 A. 4. FORM FILES A-16 A. 5. PROGRAM FILES A-16 iii CHAPTER 1 SUMMARY AND PURPOSE 1. SUI*4ARY and PURPOSE 1.1. Sunmary: This User's Manual is designed to help you use the Montana Rivers Study data management system. The system is written in dBASE III Plus, an efficient data base management system. You, as a user, need not be concerned about understanding the inner workings of dBASE III Plus. The information management system that you will be using is completely menu driven, allowing you total access to all of the functions and utilities available in the information management system. The Montana Rivers Study Data Base is being managed by the Montana Natural Resource Information System, Montana State Library, 1515 East Sixth, Helena, Montana 59620, phone (406)444-3115. Questions regarding the data base or its use should be referred to: Programmer /Analyst Montana Natural Resource Information System (406)444-3115 or Janet Decker-Hess Montana Department of Fish, Wildlife & Parks (406)752-5501 The Montana Rivers Study data base is a dynamic system and will be continuously updated. However, it is crucial that any updating or changes in data be centrally coordinated. You should never attempt to modify the data in your copy of this data base. Instead, list your suggested changes or mark them on a copy of the printout and send them to the responsible senior resource expert (refer to the Appendix D for names and addresses of senior resource experts). Any comments regarding the data management software itself should be addressed to NRIS. If you encounter a problem with the query programs, first turn your printer on, hit the "escape" key, then hold down the shift key and simultaneously hit the "PrtSc" key. This will produce a printout of the screen and record of the program(s) causing the problem. Next, on this printout write the choices you made from the previous menus to get to this point (for example, "Resource area detailed report; Wildlife; Geographic areas; Townships and Ranges). If this is not done, it is virtually impossible to identify and correct the problem. Throughout this manual examples using actual data from the data base will illustrate the ease of use and the power of the system. By replicating the examples in this manual on your own system, you will learn your way around the system and will become more familiar with its operation and its limitations. Because of the very large size of some of the data files contained in the system, the programs may seem relatively slow when first compared with other software systems that you may be using. However, don't let the apparent lack of speed fool you. The data comprising the Montana Rivers Study is contained in several very large files. Some of the routines use all of these files to gather the information that you request. 1-1 While it may appear that the computer is resting, it is actually perform- ing many calculations, relationships and file management tasks. Be patient and you will De very pleased with the vast amount of informa- tion you can obtain from the system. 1.2. Purpose: The purpose of this manual is to help you gain access to the compo- site data base generated by the Montana Rivers Study. This manual is not intended to be a short course in dBASE III Plus, but is designed to be a tool to help you use the Montana Rivers Study Data Management System. For those users interested in dBASE III Plus, there are numerous ref- erence books available at better bookstores that will provide you with all the information you desire on the dBASE III Plus data base management system. 1-2 CHAPTER 2 STARTING THE SYSTEM 2. STARTING TWE SYSTEM 2.1. System Requirements To operate the Montana Rivers Study data management system, you will need a microcomputer with an MS-DOS or PC-DOS operating system, at least a 10 megabyte hard disk with at least 5 megabytes of free disk space, 512 K RAM, and dBASE III plus. 2.2. Installing the Rivers Study Data Base The Montana Rivers Study files should be copied onto your hard disk into a subdirectory called C:\DBASE\RIVERS>. If necessary, add "PROMPT $P$G" and "PATH C:;C:\DBASE" to your AUTOEXEC.BAT file to show the subdirectory title at the prompt and to allow dBASE III to run from the subdirectory. 2.3. Loading dBASE III Plus If dBASE III Plus is not installed on your system, follow the in- structions supplied with dBASE III Plus and install the system on your hard disk. In order to utilize the data management system, first you must load dBASE III Plus. Type DBASE RIVERS (return). This will load both the dBASE III Plus system and the Rivers Study data management system. After a few seconds, the welcoming screen of the management system will display on the console. 2.4. Standard Key Conventions Standard Conventions used throughout this manual are shown in the following table. Enter or Return Key. Arrow Keys Cursor control keys on the numeric keypad. PgDn The Page Down Key "PgDn" on the numeric keypad. Backspace The Backspace key usually located above the Enter or Return key. The "key" linking all data files together is the Montana Department of Fish, Wildlife and Parks water code, a six-digit number unique to every major river or stream (see Appendix A). 2-1 2.5. The Welcome Screen: The welcome screen displays overall operational capabilities of the NRIS system in very broad terms. The main purpose of this screen is to notify you that the data management system is active and provide general information to the new user. The screen will not appear again until the system is restarted. MONTANA RIVERS STUDY DATA BASE Welcome to the Montana Rivers Study Data Base. This program allows you to access data on :Fisheries :Wildlife iNatural Features :Recreation :Cultural Features :Institutional Constraints of Montana Rivers. You will be presented with a series of menus allowing you to select: (1) The Resource category you're interested in; (2) The specific river, drainage area, or other geographical area you're interested in; (3) The format in whic h you would like the data presented, and; (4) The level of detail you require for the data. Fig. 2-1: The Welcome Screen After reading the welcoming screen, press any key to continue. All menu selections respond as soon as you press a key corresponding to the menu selection you desire. However, there are certain submenus that do require the use of the Enter or Return key during completion of the menu. These situations will be noted in the appropriate sections of the manual . 2.6. The Master Menu: The MASTER menu will display on the console after you press the key. This menu is the "heart" of the Rivers Study management system. All of the functions available within the system are called in part from this menu. Note that the upper left corner of the menu tells you that you are in the MASTER menu. This display of the menu name is typical throughout the data management system. Another standard function built into the system is the "0" (zero) option. By pressing the "0" key at any menu, you will either return to the MASTER menu or the menu immediately preceding the current menu. Therefore, repeated selection of the "0" option will return you to the MASTER menu and ultimately return you to the operating system. 2-2 MASTER MONTANA RIVERS STUDY DATA BASE Release 1.00 EDIT/UPDATE REPORT/DISPLAY A. EDIT/ADD/DELETE RECORD 1. VALUE CLASS SUMMARY BY WATER CODE B. BATCH FILE UPDATE 2. VALUE CLASS SUMMARY BY REACH C. PACK FILE 3. RESOURCE AREA DETAILED REPORT D. REINDEX FILE 4. STRAIGHT FILE DUMP 0. EXIT TO DOS Select: Fig. 2-2: The Master Menu If you inadvertently return to the operating system by PRESSING "0" (zero), you must "restart" the system as described in the previous section of this chapter. 2.7. Master Menu Selections: The MASTER menu lists the 9 choices (A, B,C, 0,1,2,3,4,0) available in the data management system. Selection of some of these menu selections will present submenus. By working your way down through the menus, you will discover the flexibility built into the information management system. If you happen to "over shoot" a menu, pressing "0" at the Select prompt will return you to the previous menu. You can "back up" to the main menu and even completely out of the system by continuing to press "0" at the select prompt. 2-3 CHAPTER 3 REPORT/DISPLAY FUNCTIONS 3. REPORT/ DISPLAY FUNCTIONS Having all the information from the Montana Rivers Study stored in your computer is of little value unless the information can be recovered in a manner usable to the user. The system has a full service reporting function built in to allow you to report the data in numerous ways. Four reports are available under the current release of the system. These reports are: 1. Value Class Summary By Water Code 2. Value Class Summary By Reach 3. Resource Area Detailed Report 4. Straight File Dump An example of each of these reports is contained in Appendix C. 3.1. Selecting Records Obviously, each time that you want to the data management system, you don't want data for the entire state. The system has a system that allows you to "custom tailor" the needs. By selecting choice "1", "2", series of menus and submenus that conditions for your report, the following section. generated a report from to have to list all the built in query and index reports to your specific or "3" you will be presented with a will allow you to set specific These conditions are shown in detail in 3.1.1. The Resource Selection Menu: The Resource Menu will display only if you have selected the Resource Area Detailed Report or the Straight File Dump. The Resource Menu is the same menu that is used in the File Management Routines. It is reproduced on the following page. 3-1 Master This menu allows you to select one of the RESOURCE CATEGORY MENU listed data bases for further querying or editing. Which of the following Resource Categories do you wish to access? 1. Fisheries 2. Wildlife 3. Natural Features (botanical and specially managed areas) 4. Natural Features (geological) 5. Recreation 6. Cultural Features 7. Description (For Value Class Reports) 0. Exit Select: Fig. 3-1: The Resource Menu in REPORT mode If you selected Report Option "4" - Straight File Dump, no more user input is necessary. The system will print the entire contents of the file. Note that some of these files are quite lengthy and that the time required for the complete report is a function of the speed of your printer. BE SURE YOUR PRINTER IS ON AND READY TO PRINT The system will prompt you to be sure your printer is on line. However, if you forget to select your printer, the system will fail. At this point you must restart the data management system before continuing. Most of the report functions have a "bail-out" feature built in. The display will inform you to press the "0"' (zero) key to stop the printing. In a few cases, you will be prompted to use the "ESCAPE" key to terminate the print. This is one of the few times the escape key is active. In all other instances, the Escape key will not terminate the current function. 3.2. Setting the Query Conditions: A Query Condition is a set of filters that will allow only records meeting the conditions of the filter to be reported. You can think of a filter as a sieve. By defining the parameters that you want, you are setting the "size of the sieve opening" so that only certain size elements will "fall through". There are numerous choices of predefined query conditions available to you through the data management system. However, the predefined choices may not always meet your needs. If this is the case, the system contains "AD-HOC" query condition options that will allow you to systematically construct a customized query (filter) condition. More discussion of the AD-HOC query generator will follow in a later section. 3-2 Master This menu a Hows you to select a query Report/Display condition to 'filter ' the data so that the SET QUERY CONDITIONS . report will contain only records for specific area{s) of interest. You may also generate your own Ad -Hoc query cone iition. 1. No Fi Iter (List all records) . 2. Geographic Areas. 3. Value Class. 4. User Generated Query (restric ted). 5. User Generated Query (unrestricted] , 0. Exit. Select: Fig. 3-2: The Query Conditions Menu (NOTE: For wildlife, if you choose query conditions 2 or 3, the query condition will be applied to DESCRIP.DBF rather than WILDLIFE. DBF) . 3.2.1. No Filter (List all records) - "1" Query condition "1" sets no query conditions, i.e. all records within the data bases are available for reporting purposes. Selection of this option is much the same as the Straight File Dump with the exception that you will be allowed to select the "Order" of the records in a later menu. 3.2.2. Geographical Areas: - "2" The Geographical Area Selection provides you with numerous sub- menus. These submenus provide you with the choices shown in the figure below. Master Report/Display Set Query Conditions GEOGRAPHICAL This menu allows you to specify method by which you will access state geographically. Select th6 from this menu. the the ; method 1. All data 2. Data for 3. Data for 4. Data for 5. Data for 6. Data for 0. Exit. for the entire state, a specified COUNTY or COUNTIES, specified EPA reaches, specified DFWP water codes, specified USGS hydrological units specified Townships and Ranges. • SELECT : Fig. 3-3: The Geographical Menu 3-3 3.2.2.1. All data for the entire state; '1' The selection of "1" will not generate a query or filter condition. It allows for the listing of all records within the selected data base. 3.2.2.2. County or Counties: - "2" For sake of example, assume that you want a report that only covers two or three counties in the state. You have previously selected the County Query. Now the display lists all of the Counties in the State pre- ceded by the county number. In the bottom center of the display you see the selection box. Master This menu allows you to sel ect the county(s) Report/Display for which you wish to obtain data. Enter 1 Set Query Conditions "0" to exit or to termi nate county input. Geographical - ■> COUNTY 1. Silver Bow 15. Lake 29. Rosebud 43. Broadwater 2. Cascade 16. Dawson 30. Deer Lodge 44. Wheatland 3. Yellowstone 17. Roosevelt 31. Teton 45. Prairie 4. Missoula 18. Beaverhead 32. Stillwater 46. Granite 5. Lewis & Clark 19. Chouteau 33. Treasure 47. Meagher 6. Gallatin 20. Valley 34. Sheridan 48. Liberty 7. Flathead 21. Toole 35. Sanders 49. Park 8. Fergus 22. Big Horn 36. Judith Basin 50. Garfield 9. Powder River 23. Musselshel 1 37. Daniels 51. Jefferson 10. Carbon 24. Blaine 38. Glacier 52. Wibaux 11. Phillips 25. Madison 39. Fallon 53. Golden Valley 12. Hill 26. Pondera 40. Sweet Grass 54. Mineral 13. Ravalli 27. Richland 41. McCone 55. Petroleum 14. Custer 28. Powell 42. Carter 56. 0. Lincoln Exit SELECT Fig. 3-4: The County Selection Sub Menu The procedure to select one or more counties is quite simple, but you must pay attention or else you may generate a "bogus" filter condi- tion. Don't worry, if you do happen to generate an incorrect query con- dition, you can go back to the menu and "reconstruct" your query. Suppose you want the report to include Yellowstone and Stillwater Counties. The procedure that would generate this condition is as follows: 1. Press "3" (without the quotes) This selects Yellowstone County. 2. Press "32" (without the quotes) This selects Stillwater County. 3. Press "0" (zero) (without the quotes) This informs the system that you have completed your selection of counties. 3-4 The result of your selection will be displayed on all of the screen displays that follow your selection until such time that they are cleared by you, or you return to the Main menu. Your query condition will look like: SET FILTER TO 'YELL.' $COUNTY .OR. 'STIL.' $COUNTY This query conditions can be interpreted as follows. Allow only those records in the data base I previously selected that contain the string 'YELL.' or 'STIl.' in the data field called COUNTY to pass through the filter and be reported. If a data record does not contain either of these counties then do not report them. 3.2.2.3. Data for specified EPA reaches: -"3" You may specify the range of data by EPA (Environmental Protection Agency) reaches by selecting option "3" from the geographical menu. Selection of this option displays the EPA Reach Menu. Master Report/Display Set Query Conditions Geographical ->EPA Enter EPA Code : Enter the EPA code: 123 (example: "1701020588000.00") Fig. 3-5: The EPA Reach Menu The EPA reach menu will appear in a slightly different manner than is shown when it is first displayed. You will be asked to input the EPA reach code. If, at this point, you decide to abort this query, enter "0" (zero). You will return to the geographical menu. If you enter an EPA reach code (shown as 123 in the figure above), the program will first "look up" from EPA. DBF the DFWP water code corresponding to the EPA code you've entered. It will then set the filter to that DFWP water code. If several DFWP water codes correspond to the EPA code you've entered, only data for the first one encountered will pass through the filter. The resulting query condition will be displayed on all future displays until it is canceled in a manner described in the County/Counties discussion. 3.2.2.4. Data for specified DFHP water codes - "4" You may specify the range of data by DFWP (Department of Fish, Wildlife and Parks) water codes by selecting option "4" from the geographical menu. Selection of this option displays the DFWP Water Code Menu. 3-5 Master Enter the lower and upper limits for the Report/Display DFWP Water Codes for which you wish to Set Query Conditions obtain data. Geographical ->WTRCODE Lower DFWP Water Code: 010040 Upper DFWP Water Code: 104861 for all after Lower Code. Fig. 3-6: The DFWP Water Code Menu The DFWP menu will not display exactly as shown in the above figure when it is first displayed. Initially, only the first line asking for the Lower DFWP Code will display. At this point, if you wish to abort the DFWP menu, enter "0" (zero). This will return you to the geographical menu. 3.2.2.5. Data for specified USGS hydrological units - "5' You may specify the range of data by USGS (United States Geological Survey) hydrological units by selecting option "5" from the geographical menu. Selection of this option displays the USGS Hydrological Units menu. Master Enter the lower and upper limits for the Report/Display USGS Codes for which you wish to obtain Set Query Conditions data. Geograph 1 ca 1 -> USGSCODE Lower USGS Water Code: 1223 Upper USGS Water Code: 4456 for all after Lower Code. Fig. 3-7: The USGS Hydrological Code Menu The USGS menu will not display exactly as shown in the above figure when it is first displayed. Initially, only the first line asking for the Lower USGS Water Code will display. At this point, if you wish to abort the USGS menu, enter "0" (zero). This will return you to the geographical menu. 3.2.2.6. Data for Specified Townships and Ranges = "6" You may specify the range of data by Township and Range by selecting option "6" from the geographical menu. Selection of this option displays the Township and Range menu shown on the next page. 3-6 Master Report/Display Geographical -> TOWNSHIP This menu will allow you to enter a range of Townships and Ranges for which you wish to obtain information, Southernmost Township Northernmost Township Westernmost Range is Easternmost Range is is TIN is T2N R20E R21E Fig. 3-8: Specified Townships and Ranges Menu The Township and Range menu will not above figure when it is first displayed, asking for the Southernmost Township will you wish to abort the USGS menu, enter you to the geographical menu. display exactly as shown in the Initially, only the first line display. At this point, if "0" (zero). This will return You may enter Townships or Ranges ranging from 1-9 without a lead- ing 0 (zero). That is, the system will translate "TIN" to "TOIN" and Range "R5E" to "ROSE". The query condition resulting from this geograph- ical menu selection will be quite long due to the method the data is stored within the data sets. Do not be alarmed if the displays following this query condition appear to overwite the borders on the display. This query condition will function correctly. 3.2.3. Value Class: Selecting the Value Class query option from the Query Conditions Menu will display the Value Class menu. This menu, shown in the following figure, allows you to limit the output to certain limits of the value class assignment. Note that the query conditiQP is sometimes called. "OVERALL" in the display. Master Report/Display ..ua Set Query Conditions only one value class. Set query conditions-> VALUE CLASS Enter the limits of the VALUE CLASS that you desire. Enter "0" for onlv one value class. Enter Lower VALUE CLASS Boundary 1 Enter Upper VALUE CLASS Boundary 2 Fig. 3-9: The Value Class Menu The Value Class menu will not figure when it is first displayed, for the Lower VALUE CLASS Boundary wish to abort the VALUE CLASS menu, to the geographical menu. display exactly as shown in the above Initially, only the first line asking will display. At this point, if you enter "0" (zero). This will return you 3-7 3.2.4. User Generated Query (restricted). If none of the options available in the menus for query condi- tions fit the needs of the desired report, the system allows for the con- struction of an AD-HOC query condition. You may enter these ad-hoc queries in two different ways. This choice allows you to use menus to construct an ad-hoc query. The next choice allows you to type in your query directly in dBase III code. The second choice, described below, is recommended for most queries; although it requires you to understand some dBase III code, it allows you to construct very powerful boolean search conditions. Because you and not the system are constructing the query, you must obey certain grammatical rules for your AD-HOC query to function. For example, dBASE III allows what is known as a "substring" search". You have seen the construction of a substring search in the County Query. The operator for a substring search is the "$". The use of this search condition requires precise grammatical construction. For example, suppose you wish to search the field "STATUS" in the Natural Features data base for the condition "RNA". The actual query condi- tion command would be: SET FILTER TO 'RNA' $STATUS The data management system will construct the actual command for you, however, it WILL NOT supply the proper punctuation, you must do this your- self. Another example may be that you want to create a query condition such that only records in Missoula county with a value class less than 2 are reported. The query condition would be similar to: SET FILTER TO 'MISS.' $COUNTY .AND. OVERALL <"2" Again, the system AD-HOC query generator will construct tfie correct command IF you supply the proper punctuation. In General, the system will not supply single quotes "'" or paren- theses "0". NOTE: DO NOT USE THE DOUBLE QUOTATION MARK ' " ' The data management system will accept them in the AD-HOC construc- tion, but will abort the system if they are used! Values that are acceptable to the AD-HOC query generator will be displayed in the lower section of the display. These fields are the variables identified as the query condition variables. Be careful in the spelling. An incorrect field name will not function correctly. An example of the figures depicting a typical AD-HOC query input screen is on the following page. 3-8 FILTER COMMAND GENERATOR This portion of the routine allows you to set a filter condition for the particular file you have selected. You may bypass the routine by entering "ALL" for the FIELD input. You may end your input by pressing the return key in the CONNECTION input area. PLEASE WAIT. Fig. 3-10: The AD-HOC Query Introduction Screen • LINE FIELD j OPERATOR EXPRESSION | CONNECTION FIELD 1 = 'ALL' TO EXIT '' IN CONNECTION TO END 1 1 1 1 1 2 1 3 1 4 1 1 5 1 CODE :RIV NAME :REGION :TRS :COUNTY :EPA NO :TRIB TO: HYD UNIT :FNL WILD :FNL FISH :FNL FOOR :FNL NAT :FNL GEO :FNL REC: OVERALL : : : : : : : 1 Fig. 3-11: A Typical AD-HOC Query Generation Input Screen Presently, no error checking is built into the system. Carefully review each input element before confirming the input with . If however, your AD-HOC query appears in error on previous screens, simply return to the AD-HOC menu and reconstruct the query. 3.2.5. User-generated Query (unrestricted). If you select this choice, you will be presented with a screen prompting you to enter a query condition that may be up to 254 characters long. Although you are limited by the grammatical rules of dBASE III, you may perform some very powerful and complex boolean searches. . .for example, you can search for all streams in Gallatin or Madison County that have value class assignments of 1 for both fisheries and recreation, or you can search for all natural features that are designated as either National Natural Landmarks or Research Natural Areas but do not have a value class of 2. as Some of the basic rules of dBASE III grammar you'll need to know follows: are 3-9 Logical Operators. Conditions can be linked together with the following logical operators: (A) .OR. (B) records meeting either condition (A) or (B) (A) .AND. (B) only records meeting both conditions (A) and (B) (A) .AND. .NOT. (B) only records meeting condition (A) and not meeting condition (B) Make sure that periods are placed both in front of and behind the logical operators; they are an essential part of the code. Substring Searches. In dBASE III, the dollar sign {"$") means "is contained in." for example, "YELL" $COUNTIES means "the character string 'YELL' is contained in the field called 'COUNTIES.' Notice that the substring you are searching for must be contained in quotation marks. If these quotation marks are not included, the query won't work. Conversion to upper case. if you're not sure if the substring you're searching for within a field is in upper case, lower case, or mixed, convert the field contents to upper case as follows: "YELL" $UPPER(COUNTIES) This will retrieve the record whether the county name has been entered as "Yell," "yell," or "YELL". Substring operation Sometimes you are only interested in part of a field, e.g., the first two digits of the water code designate the drainage, and you may be interested in these two only. The substring operation is used to select a substring from a field, for example, for the code "021476," SUBSTR(C0DE,1,2) = "02" (displays two characters beginning with the first) SUBSTR(C0DE,4,3) = "476" (displays three characters beginning with the fourth) Conversion from character to numeric. Most fields in the Montana Rivers Study data bases are either "character" (that is, they're treated simply as character strings) or "numeric" (that is, only numbers are allowed and they're treated a special way). Although a character field may contain only numbers, as with the "CODE" field, you cannot treat them as numbers (that is, you cannot perform calculations or comparisons on them) unless they are first converted to numeric. This is done using the "VAL()" function. For example, the following shows an incorrect way and the 3-10 correct way to sparch for all codes falling between the values "020000" and "030000." INCORRECT: C0DE>20000 .AND. C0DE<30000 CORRECT: VAL(C0DE)>20000 .AND. VAL{C0DE)<30000 Conversion from Numeric to Character. To convert a numeric value to a character string, use the "STR" function, e.g., STR(EAGLE). The string returned actually has ten characters to the left of the decimal, so if you wish to search for an exact match, you must select a substring of the string. For example, the following two operations involving the one-digit numeric field "EAGLE" are equivalent. EAGLE=2 SUBSTR(:)TR(EAGLE) ,10,1) = "2" Parentheses. Make sure that all multiple conditions are enclosed in parentheses, and that all pairs of parentheses match. If there are unmatched ■ parentheses, the query will not work. The following is an example of a faulty and a corrected complex query condition: INCORRECT: VAL(SUBSTR(C0DE,1 ,2)<10 .AND. "YELL" $UPPER(COUNTIES) CORRECT: VALISUBSTR(C0DE,1 ,2) ) <10 .AND. "YELL" $UPPER(COUNTIES) 3.3. Report Formats and Report Order After the completion of the query condition input, you are allowed to specify the Report Format and Report Order. Again, the display will allow you an array of choices. Master This menu allows you to specify the format and Report/Display the method the data you select is presented. REPORT ORDER FtNU All selections will report the complete entry | for each river in the selected area in one of the following formats. Select the format now. A. Water Code (or Normal Index). B. River Name. C. EPA Reach. D. USGS Code + River Name. E. Value Class + River Name. F. Value Class + Water Code. G. Value Class + EPA Reach. H. Value Class + USGS Code. I. User Generated (AD_HOC) Index. 0. Previous Menu. SELECT: Fig. 3-12: The Report Order Menu 3-11 Most of the Report Order selections are self explanatory. In some cases, depending on the database selected, not all of the selections shown will be available. Make your selection from the available reports displayed on the screen. Of particular interest is menu selection "I" - User Generated AD-HOC Index. This function operates in a manner similar to the AD-HOC query generator. AU-HOC INDEX GENERATOR This portion of the routine allows you to generate an AD-HOC index for the particular file you have selected. PLEASE WAIT Fig. 3-13: The AD-HOC Index Generator Screen PRIORITY I 2 FIELD : Enter the name of the field (or fields) on which you wish to index. iCODE :HYD UNIT ; OVElTALL :RIV_NAME :FNL WILD ; REGION ;FNL FISH ;TRS :FNL FOOR : COUNTY ;FNL NAT :EPA_NO :FNL GEO :TRIB_TO; :FNL REC: Fig. 3-14: The AD-HOC Index Generation Input Screen 3.4. Report Control Menus Many of the reports that can be generated have a print control screen. The screen may vary in appearance, but the overall function of the screen menu is the same. Unless otherwise directed, in the print mode, pressing "0" (zero) will terminate the printing and return you to the report format menu. The following is an example of the report control menu. 3-12 Master Report/Display No query conditions '■■"•"■ ■ ~ " " ■ ~ ~ ■ -VALUE CLASS ASSIGNMENT SUMMARY INDEX ON WATER CODE (or Nor ■ma Index) TO DESCRIPl REPORT TO (P)RINTER, (S)CREEN (E)xit Fig. 3-15: A typical Report Control Menu Master Report/Display No query condit ions INDEX ON WATER CODE (or Normal Index) TO DESCRIPl REPORT TO (F )RINTER, (S)CREEN (E)xit P Press *** PRINTING *** "0" to terminate print * ** END *** Fig. 3-16: A Typical Report Control Screen during print 3-13 CHAPTER 4 FILE MANAGEMENT FUNCTIONS 4. FILE MANAGEMENT FUNCTIONS 4.1. "A" (EDIT/ ADD/DELETE RECORD) NOTE: This section is Intended only for use by data managers. In order to preserve the integrity of the data files these functions have been disabled on all copies of the system except those at NRIS and DFWP's Helena offices. If you see any records that need changing, please keep a list of them (use "Shift-PrtSc" to print a copy of the record] and provide them to the appropriate senior resource expert (Appendix D) . Your changes will thus be provided to all users of the system. This selection allows numerous file management functions to be performed on the data bases within the system. New records can be ADDed to a data base (and automatically update the associated data files and ranking matrix); EDIT an existing record within the data bases (and automatically update the associated data files and ranking matrix); or mark a record for deletion from a database. The marking for deletion from a data base does not physically remove the record, but merely marks it as deleted. A deleted record will not be utilized in any of the report functions of the data management program. After selecting "A", Edit/ Add/Delete a Record, the RESOURCE menu will display on the screen. Note that the upper left corner of the menu is building you a "map", letting you know where you have been. This "map" will follow you through the entire system and at times will display query selections, filter options and index options that you have selected through the course of the menus. The RESOURCE menu, shown below lists the data bases that are available to you for file management. As you can see, an asterisk appears in line seven. There is a special data base named DESCRIP.dbf that is automatically maintained by the system. Users should not attempt to edit this data base as the reports all utilize this data base as an "internal" road map. Changing this data base destroys this map and the DESCRIP data base will have to be rebuilt, a long and time consuming procedure. Master This menu allows you to select one of the RESOURCE CATEGORY FCNU listed data bases for further querying or editing. Which of the following Resource Categories do you wish to access? 1. Fisheries 2. Wildlife 3. Natural Features (botanical and specially managed areas) 4. Natural Features (geological) 5. Recreation 6. Cultural Features 0. Exit Select: Fig. 4-1: The Resource Menu 4-1 4.1.1. Edit: After you have selected the RESOURCE data base, the console screen will clear and you will be asked for the "KEY" of the record you wish to edit. All of the data bases within the system are keyed on the record field "CODE". Because some of the data bases may have more than one record with the same "CODE" you will be presented with a full screen list of records beginning with the code you selected and listing records below (increasing code number). Master Resource EDITOR-> FISH.dbf Please enter six-digit water code for the stream you wish to access. Do not include hyphens. Example "013280" Enter "0" (zero) to exit. Fig. 4-2: The Edit Prompt Screen After you have selected the "water code" for the record that you want, the record selection screen will be displayed. The record number matching the first occurrence of the water code will automatically be displayed in the WHICH RECORD query on the lower left of the screen. If this is the record that you want to edit, press return. If, however, the record number does not indicate the record you wish to edit, enter the correct record number and press return. Record* CODE RIV NAME FINAL VAL 228 014860 MEDICINE LODGE CREEK 3 299 014940 M FK BLACKTAIL DEER CREEK 4 385 015020 MILL CREEK 4 386 015020 MILL CREEK 4 1657 015160 MUDDY CREEK 1 488 015210 NARROWS CREEK 2 325 015220 NICHOLIA CREEK 4 1658 015400 N FK DIVIDE CREEK 2 WHICH RECORD 228 N- NEXT PAGE P- PREVIOUS PAGE "0" - EXIT Fig. 4-3: The Record Selection Screen If the record you seek is not among those displayed on the screen, you can either page forward or backward by pressing either the "N" or "P" (Next or Previous page) followed by . If you are at or near the end of the file, and select the "N" option, the screen will display all of the remaining records it can on the screen. In addition, the message "END OF FILE" will be displayed in place of the N- NEXT PAGE prompt. If you again press "n", don't be surprised if you get a blank screen. Pressing "N" again will restore it. 4-2 After the record number is entered, the console screen will again clear and the particular record that you selected will be displayed in a format that is conducive to editing. The next screen displays a portion of the record, you to take one of three actions: 1. Edit the record. 2. Recall a deleted record. 3. Delete the current record. This is to allow Make your choice from one of the three options, Record No. 228 EDIT THE FISH DATA BASE OVERVIEW CODE 014860 RESOURCE F REACH AH9 RIV NAME MEDICINE LODGE CREEK SECTION 002 LOWER IRRIGATION DIVERSION UPPER AYERS CANYON TRS T10SR11W08BBAD REGION 3 (E)dit (R)ecall, (D)elete this record Fig. 4-4: The Edit Overview Screen A typical edit screen is shown below. The cursor indicates the field that is currently being edited. You may use all of the cursor keys and the key to move through the record. Note the instruction at the bottom of the page. It is how you can page through a multi page edit, Save the changes you have made to certain fields within the record, or abort the edit . To edit a record, edit. Move the cursor (Control + Y). This Enter the new data. position the cursor in the field you wish to to the beginning of the field and press *Y will erase the data contained in the field. 4-3 Record No. 228 EDIT THE FISH DATA BASE Page 1 of 1 CODE 014860 RESOURCE F REACH AH9 RIV NAME MEDICINE LODGE CREEK SECTION 002 LOWER IRRIGATION DIVERSION UPPER AYERS CANYON TRS T10SR11W08BBAD REGION 3 COUNTYl BEAV C0UNTY2 C0UNTY3 C0UNTY4 C0UNTY5 LENGTH 28.2 VALUE A 3 VALUE B 3 VALUE C 4 VALUE_D Press "PgDr " to move thru or save record. Fig. 4-5: A Typical Edit Screen WARNING: On many computer keyboards, the numeric keypad provides two functions. The first function, as the name implies, is to allow for the rapid entry of numerical (0-9) data. The other func- tion, and the function you will be using most of the time, is for cursor position control. The function or mode of the keypad is controlled by the "Num Lock" key which is located above the keypad. On some keyboards, there is a small LED which wi]] illuminate if the keypad is in the numeric mode. Other key- boards, like the IBM PC give you no indication whatsoever as to the current mode of the keypad. dBASE III has recognized this shortfall and it will tell you not only the status of the numeric keypad, but also if the "Caps Lock" is engaged, if the "Scroll Lock" is engaged or if you are in the "Ins" (Insert) mode. In order for the edit function to work correctly, the keypad must be in the "cursor control mode". Additionally, the "Scroll Lock" should not be engaged. The data you have just entered is not recorded in the data base until you specifically instruct the program to "S"ave the changes. You accomplish this by the following actions. 1. Pressing the "PgDn" key. 2. Pressing "S" for save. 4-4 When you save a record, there will be a brief pause. This is normal. A lot is happening with the information you just entered. The five county names are regrouped and stored into a field called COUNTY (you cannot edit this field). The Final Value for the record is re- computed with the result being saved in the field called FINAL_VAL (another field that you cannot edit). Finally, the DESCRIP.dbf data base is updated to reflect any changes that are appropriate from the data base you are editing. If you use the editor to make changes to the data and later discover the changes you made were in error, you must re-edit the record to correct the data that is in error. To exit from the edit routine, simply enter "0" at the KEY prompt. You will return back through the menus. 4.1.2. Add: New records are added to the data base by entering a unique key. If the editor does not find the record you are requesting, you will be asked whether or not you wish to add a new record. If you have mistakenly entered an incorrect key, press "N". You will return to the KEY entry screen. If you answer "Y" a blank record similar in format to the edit screen will display. Using a prepared data entry sheet, enter the data in the precise order in which the cursor prompts. You can move about on a particular screen, but you cannot page back and forth. If you do make a mistake simply edit the record after it is saved by the add routine. 4.1.3. Delete: As you have seen, the delete function is actually contained within the Edit function. By selecting (D)elete from the edit overview routine, the record is automatically deleted. You can tell if a record has been marked for deletion by observing the upper right center of the screen. If the word "Deleted" is visible, and flashing, the record has been marked for deletion. If you have mistakenly marked a record for deletion, you can "reca" any time prior to "Packing" the data base. (More on Packing later ill" if any time prior to "Packing" the data base. (More on Packing later). To "undelete" a record, select the (R)estore option from the edit overview screen. The record will be undeleted. The routine goes directly into the edit mode to allow any changes that you may want to make. After making any changes press "PgDn" and (S)ave the record. You can also determine which records are marked for deletion whenever you select a KEY and the 20 line record display is on the screen. Any record that is marked for deletion will have an "*" displayed near the record number. 4-5 4.2. "B" Update Record (Batch): NOTE: At the time of this release, the Batch Update routine has not been written or incorporateed into this system. This selection will allow you to do a "batch" update of the selected data base. "Batch Update" simply means that all of the additions or corrections to be made to the data base have been compiled into a separate data base file with the same file structure and that we will let dBASE III find the correct record and replace existing data with new data or add new records to the data base. Batch updating has some particular advantages. First, you can review and edit the "update" file to insure that all data is correct. Second, you can do the batch update at a time when computer usage is slow, thereby allowing more users time on the computer. At the time of this release, the Batch Update routine has not been written or incorporated into this system. 4.3. "C" Pack File: This selection allows you to "Pack" a selected data base file. The selected data base file is selected from the RESOURCE menu in a manner similar to that explained under the Add/Edit/Delete function. Note that an additional option is now available to you. You can "Pack" all of the data bases with one operation, the "ALL option". Master This menu allows you to select one of RESOURCE CATEGORY MENU the listed data bases for further querying or editing. Which of the following Resource Categories do you wish- to access? 1. Fisheries 2. Wildlife 3. Natural Features (botanical and specially managed areas) 4. Natural Features (geological) 5. Recreation 6. Cultural Features 7. Description (For Value Class Reports) 8. All data bases 0. Exit Select: Fig. 4-6: The Resource Menu in PACK mode "Packing" a data base permanently removes the record from the data base, i.e. it is gone forever. Only those records marked for deletion are removed from the data base. Therefore, it is in your best interest to review the data base file prior to running the pack operation, as it is much easier to "undelete" a record than it is to re enter the entire record. The "Pack" routine will ask you if you want a list of records 4-6 marked for deletion prior to packing the file. In some cases, depending on the size of the data base file, not all of the information contained in the data base will be reported. However, sufficient data win be displayed to allow you to determine whether or not the record should be deleted and removed from the data base file. If you discover that a record is marked for deletion that you do not want to delete, abort the pack operation and select the "Add/Edit/Delete" operation from the MASTER MENU. Again select the data base from the RESOURCE Menu, edit the particular record and undelete it with the "R" keystroke. You can repeat the undelete operation as many times as necessary until only the records you want deleted remain marked for deletion. You can now select the "Pack" option from the MASTER menu and complete the "Pack" operation. During the pack operation, the console will report the progress of the operation. You will also see a message line reporting the status of the index file(s). These index files are part of the system that allow you rapid access to any record within the system. The index must be rebuilt after a "Pack" operation to maintain the integrity of the index and to allow you to be able to find records in the future. When the packing operation is complete, program control will return to the MASTER menu. 4.4. "D" Reindex File: All of the data base files have standard index files associated with them These index files are "maintained indexes", that is the are automatically updated when records are added to the data base. There are some cases, however, when a data base index will become "confused". The system allows you to easily reconstruct the index if you suspect this misalignment has occurred. By selecting the "Reindex File" option, and selecting the appropriate data base, the system will reconstruct the data base index. Again, like the "Pack" routine you have the option of re indexing "ALL" of the data bases. No further user intervention is required. When the reindexing operation is complete, program control will return to the MASTER menu. 4-7 APPENDIX A DATA BASE FILE STRUCTURES APPENDIX A FILE STRUCTURES A.l. Data Base Files: Table A-1 lists and briefly describes the database files contained in the Montana Rivers Study data base. Table A-1: DATA BASE FILES 1. DESCRIP.DBF This is the MASTER data base containing a summary of all information contained in the other data bases. Every water code for which there is infor- mation is represented by a record in this data base, with the name of the stream, various geo- graphical descriptors, and the value class assign- ments for each resource category. This file is the authority for names associated with water codes and for the geographical descriptors of the streams. 2. FISH. DBF This is the fisheries data base. It is a subset of the much larger DFWP interagency stream data base. Each water code may have more than one reach code assigned to it, so the number of records in this data base is larger than the number of water codes. 3. REC.DBF This is the recreation data base. Each river may have more than one reach code assigned to it, so the number of records contained in this data base is larger than the number of water codes rated. 4. GEO. DBF This is the geological features data base. Many individual sites may correspond to a single water code; each site is given a unique "reach" number although the sites are not really "reaches". 5. NAT. DBF This is the natural features data base (including botanical and specially managed biological sites). Its structure is identical to that of GEO. DBF. 6. FOOR.DBF This is the cultural features data base. Each river may have more than one reach code assigned to it, so the number of records contained in this database is larger than the number of water codes rated. 7. WILDLIFE. DBF This is the wildlife data base. It is a subset of a much larger data base managed by DFWP. This file contains information for each of the 354(??) wildlife areas into which the state has been divided by DFWP. Each of these areas contains many streams corresponding to many water codes. The wildlife areas and the water codes are related by the following file, AREACODE.DBF. A-1 8. AREACODE.DBF 9. COUNTY. DBF Records in this file contain only two fields: a water code, and the wildlife area code cor- responding to that water code. This file is a lookup table relating county names to the 3-digit county codes used in the fisheries data base. 10. EPA. DBF This file is a lookup table relating DFWP water codes to EPA codes. The following tables list the Field Names, Field Types, Field Width, Decimal allocation, and field definitions for the Montana Rivers Study data case files. A. 1.1. DESCRIP.DBF DESCRIP.dbf Alias: DESCRIP Master index file: DESCRIP. ndx Key: CODE + RIV NAME Structure for database: DESCRIP.dbf Field Field Name Type Width Description 1 CODE C 6 2 RIV_NAME C 30 3 REGION C 1 4 TRS C 14 5 LOWER C 30 6 UP TRS C 14 7 UPPER C 30 8 COUNTY C 25 9 TRIB TO C 25 10 HYD UNIT C 8 11 LENGTH N 5(1) 12 USES FOR C 15 13 USES DIS C 15 14 FNL WILD C 1 15 FNL FISH C 1 16 FNL FOOR C 1 17 FNL_NAT C 1 18 FNL_GEO C 1 19 FNL REC C 1 20 FINAL VAL C 1 ** Total ** 226 DFWP water code River name {as contained in DFWP water code catalog) DFWP administrative region Legal description of lower boundary Verbal description of lower boundary Legal description of upper boundary Verbal description of upper bouadary Counties crossed by the river or stream Name of stream into which this one flows USGS hydrologic unit code Length in kilometers USES National Forest USES Forest District Final wildlife value class assignment Final fisheries value class assignment Final cultural value class assignment Final natural features (botanical, spe- cially managed) value class assignment Final geological features value class assignment Final recreation value class assignment Final overall value class assignment (this is equal to the highest value class assignment received for any one of the individual resource categories) A-2 A. 1.2. FISH.dbf FISH.dbf Alias: FISH Master index file: FISH.ndx Key: CODE + FINALVAL Structure for database: FISH.dbf Field Field Name Type Width Description 1 CODE 2 RESOURCE 3 REACH 4 RIV_NAME 5 SECTION 6 7 8 9 10 11 13 14 15 HYD_UNIT LOWER UPPER TRS UP_TRS USPS FOR 12 USPS DIST TRIB_TO REGION COUNTY C c c c c c c c c c 6 1 30 3 11 30 30 14 14 2 30 1 25 16 COUNTYl C 4 17 C0UNTY2 C 4 18 C0UNTY3 C 4 19 C0UNTY4 C 4 20 C0UNTY5 C 4 21 LENGTH N 5(1) 22 VALUE A C 1 23 VALUE B c 1 24 VALUE C c 1 25 VALUE D c 1 26 FINAL VAL c 1 DFWP water code "F" for all records (to indicate fisheries) A unique 3-character identifier (called the "serial" in the interagency fish- eries data base) for the segment rated Name of river or stream Describes which section of the water code is being rated in this record USGS hydrologic unit code Description of lower reach boundary Description of upper reach boundary Legal description of lower boundary Legal description of upper boundary Code for USPS National Forest (see Appendix B.l) Code for USPS Forest District (see Appendix B.l) Tributary to DFWP administrative region Counties crossed by the river or stream (this field is a concatenation of the following five which counties crossed) list individual ** Total ** 233 Length of reach (kilometers) Resource value Sport Fishery value Habitat and Species value (blank) Pinal fisheries value class (equals highest value class assigned for resource value, sport fishery value, or habitat and species value) (l=Unique or Outstanding; 2=Substantial ; 3=Moderate; 4=Limited; U=Unknown or unclassified) A-3 A. 1.3. REC.dbf REC.dbf Alias: REC Master index file: REC.ndx Key: CODE + FINAL VAL Structure for database: REC.dbf Field Field Name Type Width 1 CODE C 2 RESOURCE C 3 REACH 4 AGENCY C C 6 1 4 1 5 RIV NAME C 30 6 SEG NAME C 15 7 UP BOUND C 15 8 LO BOUND C 15 9 LENGTH C 2 0 DFWP REGN C 1 1 WATER CHAR C 1 12 MNTH_BTBL C 1 13 MOTOR_BOAT C 1 14 CANOE C 1 15 KAYAK C 1 16 RAFT C 1 17 TUBING C 1 18 SWIMMING C 1 19 BOAT FISH C 1 Description DFWP water code "R" for all records (to indicate recreation) Segment or reach rated Agency rating the reach (1 = DFWP only; 2 = BLM only; 3 = USES only; 4 = DFWP and USES; 5 = DFWP and BLM; 6 = BLM and USFS; 7 = all 3 agencies) River name Segment name Description of upper boundary Description of lower boundary Length (in — ?) DFWP administrative region Water character (1 2 3 4 5 6 7 8 No. of months per year boatable 9 = flat; = flat/minor rapids; = minor rapids; = minor/moderate rapids; = moderate rapids; = moderate/major rapids; = major rapids; = not boated) of months per year = 9 or more months) Use for motor boating (1 = primary activity; 2 = secondary activity) Use for canoeing (1 = primary activity; 2 = secondary activity) Use for kayaking (1 = primary activity; 2 = secondary activity) Use for rafting (1 = primary activity; 2 = secondary activity) Use for innertubing (1 = primary activity; 2 = secondary activity) Use for swimming (1 = primary activity; 2 = secondary activity) Use for boat fishing (1 = primary activity; 2 = secondary activity) A-4 REC.dbf Alias REC. (continued) 20 SHORE FISH C 1 21 EXTRA_1 C 2 22 EXTRA_2 C 2 23 TENT_CAMP C 1 24 CAR CAMP C 1 25 TRAIL USE C 26 MOTOR TRAI C 27 DRIVING C 1 28 VIEWING C 1 29 PICNIC C 1 30 EXTRA_3 C 2 31 EXTRA_4 C 2 32 USE_LEVEL C 5 33 UNITS c 1 34 USE ESTIMA C 35 ACCESS Use for shore fishing (1 = primary activity; 2 = secondary activity) Other land and water based activities (see Appendix B,2) Other land and water based activities (see Appendix B,2) Use for tent camping (1 = primary activity; 2 = secondary activity) Use for car camping (1 = primary activity; 2 = secondary activity) Use by trailers (1 = primary activity; 2 = secondary activity) Use for motor trailers (I = primary activity; 2 = secondary activity) Use for driving (1 = primary activity; 2 = secondary activity) Use for viewing (1 = primary activity; 2 = secondary activity) Use for picnicing (1 = primary activity; 2 = secondary activity) Other land and water based activities (see Appendix B.2) Other land and water based activities (see Appendix B.2) Approximate use level, available Units for use level (1 = visits; 2 = visotor days; 3 = other unit) Use estimate (1 = heavy; 2 = heavy/moderate; 3 = moderate; 4 = moderate/ low; 5 = low) Access rating (1 = abundant access; 2 = abundant/moderate; 3 = moderate; 4 = moderate/limited; 5 = limited; 6 = limited/restricted; 7 = restricted; 8 = other) if data are A- 5 REC.dbf Alias REC. (continued) 36 ROS CLASS 37 SCENIC QUA C 38 NO_SITES C 1 39 VALUE A C 1 ** 40 VALUE B C 1 41 VALUE C C 1 42 FINAL_VAL C 1 43 REASONl C 2 44 REAS0N2 C 2 45 REAS0N3 C 2 46 REAS0N4 c 2 47 REAS0N5 c 2 48 REAS0N6 c 2 49 REAS0N7 c 2 50 REAS0N8 c 2 51 REAS0N9 c 2 52 REASONIO c 2 Total ** 150 2 3 4 5 6 7 2 3 4 5 7 Recreation opportunity spectrum class (1 - primitive; primitive/ semi primitive; semiprimitive; semiprimitive/transitional ; transition; transitional/rural ; rural; 8 = rural/urban; 0 = urban) Scenic quality (1 = outstanding; outstanding/substantial ; substantial ; = substantial/moderate; = moderate; 6 = moderate/limited; limited) Number of developed recreation sites along this reach DFWP value class (l=outstanding; 2=substantial ; 3=moderate; 4=limited; U=unknown or unclassified) BLM value class (as above) USPS value class (as above) Final value class (as above; equals the highest value class assignment in any of the above three categories) Additional reasons given for value class assignment (Appendix B.3) (as above) (as above) (as above) (as above) (as above) (as above) (as above) (as above) (as above) A-6 A. 1.4. GEO.dbf GEO.dbf Alias: GEO Master index file: GEO.ndx Key: CODE + FINAL_VAL Structure for database: GEO.dbf Field Field Name Type Width Description 1 CODE C 6 2 RESOURCE C 1 3 REACH C 4 4 SITENAME C 40 5 TYPEl C 20 6 TYPE 2 C 20 7 TYPE 3 c 20 8 STATUS c 40 9 COUNTY 26 BLM 25 10 COUNTYl C 4 11 C0UNTY2 C 4 12 C0UNTY3 C 4 13 C0UNTY4 C 4 14 C0UNTY5 C 4 15 USGSNO C 8 16 RIV NAME C 30 17 MIMIN C 6 18 MIMAX C 6 19 QUADNAMEl C 35 20 Yl c 2 21 SCI c 3 22 QUADNAME2 c 35 23 Y2 c 2 24 SC2 c 3 25 0 c 1 27 TN C 2 28 G C 1 29 TX c 2 30 T c 1 31 RN c 2 32 Y c 1 33 RX c 2 34 R c 1 35 LEGAL c 55 36 LATMIN c 6 DFWP water code "G" for geological , "N" for other natural (Dotanical, specially managed) Site number Site name Type of feature Type of feature Type of feature Special designation, management status or institutional constraint Counties in which the site is located (concatenation of the following five fields) USGS Hydro logic Unit Code River name River mile at lower boundary River mile at upper boundary Name of USGS quad on which -site is located Year of above quad map Scale of above quad map Name of second USGS quad (if more than one) Year of above quad map Scale of above quad map Number of additional quad maps on which site occurs Map number of BLM 1:100,000 map on which site occurs Number of northernmost township N or S? Number of southernmost township N or S? Number of easternmost range E or W? Number of westernmost range E or W? Sections (or additional legal descr.) Southernmost latitude (degrees, minutes, seconds) A-7 GEO.dbf Alias GEO (continued) 37 LATMAX C 6 38 LONGMIN C 7 39 LONGMAX C 7 40 LATILONG C 2 41 DESCRIPTl C 254 42 DESCRIPT2 C 100 43 SOURCES C 200 44 ACCURACY C 1 45 46 VALUE A VALUE_B C C 47 VALUE_C C 48 VALUE_D C 49 FINAL_VAL C ** Total ** 985 Northernmost latitude (degrees, minutes, seconds) Easternmost longitude (degrees, minutes, seconds) Westernmost longitude (degrees, minutes, seconds) Latilong containing site Narrative description Description (continued) Sources of information on site How accurately is site located? (A = to nearest 1/4 section; B = to nearest section; C = to nearest township; D = to nearest county) Value class assignment for uniqueness Value class assignment for previous designation or listing Value class assignment recreational use Value class assignment reference value Final value class assignment (equals highest value class received in any of the above four ratling categories) for public and for scientific A. 1.5. NAT.dbf NAT.dbf Alias: NAT Master index file: NAT.ndx Key: CODE + FINALVAL Structure for database: NAT.dbf (The structure of this file is identical to that of GEO.DBF) A-8 A. 1.6. FOOR.dbf (Cultural data base) FOOR.dbf Alias: POOR Master index file: FOOR.ndx Key: CODE Structure for database: FOOR.dbf Field Field Name Type Width Description 1 CODE C 6 z RESOURCE C 1 3 REACH C 4 4 MAP_NAME C 20 5 RIV NAME C 35 6 VALUE A C 7 VALUE B C 8 VALUE C C 9 VALUE D C 10 FINAL VAL C 11 UP TWP C 3 12 UP RAN C 4 13 UP SEC C 3 14 LO TWP C 3 15 LO RAN C 4 16 LO SEC C 3 ** Total ** 91 DFWP water code "C" for an records (to indicate cultural) Segment rated Name of BLM 1:100,000 map on which segment is shown Name of river or stream Value class assignment (blank) (blank) (blank) Final cultural value class assignment Township of upper segment boundary Range of upper segmant boundary Section of upper segment boundary Township of lower segment boundary Range of lower segment boundary Section of lower segment boundary A. 1.7. WILDLIFE. DBF WILDLIFE. DBF Alias: WILDLIFE Master index file: AREA.NDX Key: AREA Structure for database: WILDLIFE. DBF Field Field Name Type Width Description 1 HYDRUN C 8 2 REG C 1 3 DRA C 4 4 AREA C 3 5 I^IAME C 37 6 LOWBOUN c 27 7 UPBOUND c 27 8 TYPE c 1 9 TRIBTO 20 10 TRIBDR C 4 11 CONFL RM C 6 12 CONFLLEG C 10 USGS Hydrological unit DFWP administrative region DFWP drainage code (see Appendix B.4) Unique wildlife area identification code (all start with J) Wildlife area name Lower boundary of wildlife area Upper boundary of wildlife area Wildlife area river/land type (M = mainstem; B = basin; T = tributaries of mainstem) River to which the streams within the wildlife area are tributaries Drainage code for above River mile of wildlife area confluence Legal description of wildlife area confluence A-9 WILDLIFE. dbf Alias: 13 LOWRM C 14 UPRM C 15 LOWLEG C 16 LOWUTMX C 17 LOWUTMY C 18 CNTYl C 19 CNTY2 C 20 CNTY3 C 21 PW N 22 WS N 23 NWR N 24 NFH N 25 WMA N 26 WPA N 27 NCA N 28 CE N 29 RNA N 30 OTHER N 31 OTRATE N 32 HABCOND N 33 HABFOR N 34 HABWET N 35 HABISL N 36 HABDIV N 37 HABOG N 38 GRIZ N WILDLIFE (continued) 6 6 10 6 7 3 3 3 area lower area upper River mile of wildlife boundary River mile of wildlife boundary Legal description of wildlife area lower boundary UTMX coordinate of wildlife area lower boundary UTMY coordinate of wildlife area lower boundary 1st county overlapping wildlife area 2nd county overlapping wildlife area 3rd county overlapping wildlife area Proposed wilderness in area? (1 = Y, 0 = N) Wild and scenic river in area? (1 = Y. 0 = N) National Wildlife Refuge in area? ( 1 = Y. 0 = N) National Fish Hatchery in area? (1 = Y, 0 = N) Wildlife Management Area in area? (1 = Y, 0 = N) Waterfowl Protection Area in area? (1 = Y, 0 = NJ Nature Conservancy Preserve in area? (1 = Y, 0 = N) Conservation Easement in area? (1 = Y, 0 = N) USFS or BLM- Research or Natural Area in area? (1 = Y, 0 = N) Any other Formal Land Designation Within area? (1 = Y, 0 = N) Rating for other Land Designation, if any (1 = Y, 0 = N) Habitat Condition of Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Amount of Forested Land in Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Amount of Wetland Habitat in Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Amount of Islands in Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Habitat Structure and Diversity in Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Amount of Old Growth Habitat in Wildlife Area (1 = Low, 2 = Moderate, 3 = High) Grizzly Bear Habitat (0 = Absent, 1 = Fringe areas, 2 = Critical Habitat) A-10 WILDLIFE. dbf Alias 39 WOLF N 40 EAGLE N 41 WHCR N 42 PEREG N 43 CARIB N 44 WT_RNG N 45 WT IV N WILD 46 MU_RNG 47 MD IV N N 48 EK_RNG N 49 EK_IV N 50 AN_RNG N 51 AN_IV N 52 BH_RNG N 53 BH IV N 54 MO_RNG N 55 MO_IV N 56 BB RNG N IFE (continued) Gray (0 = Bald (0 = 2 = Deer to Whitetail Wolf Habitat Absent, 1 = Present) Eagle Habitat Absent, 1 = Low Density Use, Nesting or Critical Whooping Crane Habitat (0 = Absent, 1 = Present) Peregrine Falcon Habitat (0 = Absent, 1 = Present) Caribou Habitat (0 = Absent, 1 = Present) Seasonal Use by Whitetail (see Appendix B.5) Importance Value of Area Deer (1 = Low Populations; 2 = Moderate Populations; 3 = High Populations) Seasonal Use by Mule Deer (see Appendix B.5) Importance Value of Area to Mule Deer (1 = Low Populations; 2 = Moderate Populations; 3 = High Populations) Seasonal Use in Area by Elk (see Appendix B.5) Importance Value of Area to (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Antelope (see Appendix B.5) Importance Value of Area to Antelope (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by (see Appendix B.5) Importance Value of Sheep (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Moose (see Appendix B.5) Importance Value of Unit to Moose (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Black Bear (see Appendix B.5) Elk Bighorn Sheep Area to Bighorn A-11 WILDLIFE. dbf Alias: WILD 57 BB IV 58 ML_RNG 59 ML IV N N 60 ST_RNG 61 ST IV N N 62 SG_RNG N 63 SG_IV N 64 MG_RNG N 65 MG IV N 66 RO HS 67 BV HS 68 BC HS 69 LX HS 70 MT HS IFE (continued) Lion to Mountain Sharp-Tail Sharp-Tail Importance Value of Area to Black Bear (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Mountain (see Appendix B.5) Importance Value of Area Lion (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Grouse (see Appendix B.5.) Importance Value of Area to Grouse (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Sage Grouse (see Appendix B.5) Importance Value of Area to Sage Grouse (1 = Low Populations, 2 = Moderate Populations, 3 = High Populations) Seasonal Use in Area by Mountain Goat (see Appendix B.5) Importance Value of Area to Mountain Goat (1 = Low Populations, 2 = Moderate Pop-ulations, 3 = High Populations) Habitat Suitability for River Otter (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High Densi-ty/Suitability Habitat Suitability for Beaver (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High Density/Suitability) Habitat Suitability for Bobcat (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High Density/Suitability) Habitat Suitability for Lynx (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High Density/Suitability) Habitat Suitability for Marten (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High Density/Suitability) A-12 WILDLIFE. dbf Alias 71 TU_HS N 72 RG_HS N 73 PH_HS N 74 CG_HS N 75 WO HS N 76 WV_HS N 77 OTH HS N WILD 78 WTFWLSTG N 79 SPGS N 80 HIGHGRAD N 81 REPTSCON N 82 COLNEST N 83 OSPREY N 84 GDEAGLE N 85 RAPTNEST N 86 SSCOTH C 20 87 SSCRATE N 4 IFE (continued) Habitat Suitability for Turkey (1 = Low Density /Suitability, 2 = Moderate Density/Suitabil ity, 3 = High Density/Suita-Dility) Habitat Suitability for Ruffed Grouse (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High DensityZ-Suitability) Habitat Suitability for Pheasant (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High DensityZ-Suitability) Habitat Suitability for Canada Geese (1 = Low Density/Suitability, 2 = Moderate Density/Suitability, 3 = High DensityZ-Suitability) (Not used) Habitat Suitability for Wolverine (1 = Low DensityZSuitability, 2 = Moderate DensityZSuitability, 3 = High DensityZ-Suitability) Habitat Suitability for Any Other Species (1 = Low DensityZSuitability, 2 = Moderate DensityZSuitability, 3 = High DensityZSuitability) Waterfowl Staging Areas or "Prime Wetlands" in area? (1 = Y, 0 = N) WarmZHot Springs Open in Winter and Used by Waterfowl? (1 = Y, 0 = N) Harlequin Duck or Amphibian of Special Concern in Stream? (1 = Y, 0 = N) Reptiles of Special Concern in Sloughs, Backwaters? (1 = Y, 0 = N) Areas with Colonies? (1 = Y, 0 = N) Large Nesting Osprey Population? (1 = Y, 0 = N) Nesting Golden Eagle Cliffs? (1 = Y, 0 = N) High Density Raptor Populations? (1 = Y, 0 = N) Other Specialized Wildlife Use Areas (verbal description] Rating for Other Specialized Wildlife Use Area (1 = Y, 0 = N) Cormorant, Heron, Pelican A-13 WILDLIFE. dbf Al ias : WILDL 88 COUNTY C 25 89 TOTHABPTS N 3 90 TOTSPPTS N 3 91 TOTHUNPTS N 3 92 TOTNONPTS N 3 93 TOTRECPTS N 3 94 HABRATE N 1 95 SPECRATE N 1 96 RECRATE N 1 97 FINAL VAL C 1 Each County in 4 letter county from Habitat from from Quality Species Quality Hunting Recreation from Nonconsumptive ** Total ** 328 First Four Letters of area ("." between each abbreviation) Total Points Criteria Total Points Criteria Total Points Criteria Total Points Recreation Criteria Total Recreation Points Habitat Value Class (1 = Outstanding, 2 = Substantial, 3 = Moderate, 4 = Low, 5 = Unknown) Species Value Class (1 = Outstanding, 2 = Substantial, 3 = Moderate, 4 = Low, 5 = Unknown) 1 = Outstanding, 2 = Substantial, 3 = Moderate, 4 = Low, 5 = Unknown) Final Wildlife Resource Value Class (1 = Outstanding, 2 = Substantial, 3 = Moderate, 4 = Low, 5 = Unknown) A-14 A. 1.8. AREACODE.dbf AREACOOE.DBF Master index file: AREACODE.ndx Key: CODE + AREA Structure for database: AREACODE.dbf Field Field Name Type Width Description 1 CODE C 6 DFWP water code 2 AREA C 3 DFWP wildlife area code ** Total ** 9 A. 1.9. COUNTY. dbf COUNTY. dbf Alias: COUNTY Master index file: COUNTY. ndx Key: CNTY Structure for database: COUNTY. dbf Field Field Name Type Width Description 1 CNTY C 2 COUNTY C ** Total ** 15 18 DFWP 3-digit county code (See Appendix B.4) Name of county A. 1.10. EPA. dbf EPA. DBF Alias: EPA Master index file: EPA. ndx Key: CODE Structure for database: EPA. dbf Field Field Name Type Width 1 CODE 2 RRN ** Total ** C C 6 16 22 Description DFWP water code EPA code A. 2. INDEX FILES As noted in the preceeding file structures, each of the data base files has a maintained index file. The following table lists the names of those files. Table A-2: INDEX FILES AREACODE.NDX FISH. NDX REG. NDX CNTY. NDX FOOR.NDX AREA. NDX COUNTY. NDX GEO. NDX EPA. NDX DESCRIP.NDX NAT. NDX A-15 A. 3. QUERY FILES The routines that allow the construction of query files and index files utilize special database files to allow these queries or indexes on selected variables. The data base files are denoted with the file extention name ".STR". The following table lists these files. Table A-3: QUERY FILES DESCRIP.STR NAT. STR FISH. STR REC.STR FOOR.STR WLRANK.STR GEO. STR A. 4. FORM FILES Many of the file dump routines use the dBASE III report format generated by dBASE III. The following table lists the report files utilized in this system. Table A-4: REPORT FILES AREACODE.FRM HARVEST. FRM DESCRIP.FRM REC.FRM FISH. FRM WLRANK.FRM FOOR.FRM A. 5. PROGRAM FILES The following table lists the programs comprising the Montana Rivers Study data management system. Table A-5: PROGRAM FILES VCAR.PRG MASTERl.PRG EPA.PRG FOORAPND.PRG 6E0EDIT.PRG NATl . PRG NRIMS.PRG RECSAVE.PRG VALUCLAS.PRG V_STOP . PRG RPTFMT.PRG FISHAPND.PRG FOOREDIT.PRG GE06RAPH.PRG NATAPND.PRG RECAPND.PRG TOWNSHIP. PRG VCAS.PRG FILDUMP.PRG COUNTY. PRG FISHEDIT.PRG GENPROCS.PRG GEONAT.PRG NATEDIT.PRG RECEDIT.PRG WILDMENU.PRG WTRCODE.PRG RESOURCE. PRG EDITOR. PRG FLTROUPT.PRG GEOAPND.PRG GEOSAVE.PRG NATSAVE.PRG RECFRM.PRG USGSCODE.PRG A-16 APPENDIX B TABLES USED IN CODING DATA APPENDIX B.l CODES USED FOR NATIONAL FORESTS AND FOREST DISTRICTS (FISH. DBF) FOREST AND DISTRICT CODES, FOREST SERVICE REGION 1 Forest Code District Cod( Dillon 01 Wise River 02 Wisdom 03 Sheridan 06 Madison 07 Stevensville 01 Darby 02 Sula 03 West Fork 04 Sheyenne 01 Beartooth 02 Sioux 03 Ashland 04 Ft. Howes 05 Grand River 06 Medora 07 McKenzie 08 Deerlodge 01 Jefferson 02 Philipsburg 03 Butte 04 Swan Lake 01 Spotted Bear 04 Hungry Horse 06 Glacier View 07 Tally Lake 08 Big Timber 01 Livingston 02 Gardiner 03 Bozeman 05 Gallatin 06 Hebgen Lake 07 BEAVERHEAD 02 BITTERROOT 03 CUSTER 08 DEERLODGE 09 FLATHEAD 10 GALLATIN 11 B-1 FOREST AND DISTRICT CODES, FOREST SERVICE REGION 1 (continued) Forest Code District Code HELENA 12 Townsend 01 Helena 02 Lincoln 04 KOOTENAI 14 Rexford 01 Yaak 02 Fortine 03 Troy 04 Libby 05 Fisher River 06 Cabinet 07 LEWIS & CLARK 15 Teton 01 Sun River 02 Belt Creek 03 Judith 04 Musselshell 06 White Sulphur 07 LOLO 16 Missoula 03 Ninemile 04 Plains 05 See ley Lake 06 Superior 07 Thompson Falls 08 B-2 APPENDIX B.2 COOES FOR OTHER LANO AND WATER BASED ACTIVITIES (REC.DBF) (1 = Primary Use, 2 = Secondary Use) 01 Waterfowl hunting 1 02 Big game hunting 1 03 Upland bird hunting 1 04 Upland bird hunting 2 05 Big game hunting 2 06 Waterfowl hunting 2 07 Hunting 1 08 Hunting 2 09 Summer homes 1 10 Woodcutting 1 11 Rock collecting 1 12 Rock collecting 2 13 Trapping 1 14 Woodcutting 2 15 Bird hunting I 16 Bird hunting 2 17 Pleasure driving {gravel roads) 1 18 Trapping 2 19 Pleasure driving (gravel roads) 2 24 Cross-country skiing 1 25 Cross-country skiing 2 26 Horseback riding 2 27 Wildlife viewing 2 28 Birdwatching 2 29 Mountain climbing 1 30 Snowmobiling 1 31 Backpacking 1 32 Crayfishing 1 33 Outfitting 1 34 Bow hunting 1 35 Horseback riding 1 36 Ice fall climbing 2 37 Ghost town visiting 2 38 Gold panning 1 39 Ghost town 1 40 Float boating 1 41 Mountain biking 2 42 Four-wheel driving 2 43 Water play 2 44 Scenic viewing 1 45 Waterskiing 1 47 Waterskiing 2 48 Scenic viewing 2 49 Photography 2 50 Taking minnows 1 B-3 APPENDIX B.3 EXPLANATIONS FOR VALUE CLASS ASSIGNMENTS RECREATION (REC.DBF) Stream Characteristics 05 Short segment 16 Bank erosion/disturbed shoreline 33 Meandering/braided 34 Major waterfall 37 No Whitewater or falls 47 Small creek/low flows/ intermittent 50 Long free-flowing segment 84 Mountain stream/ falls Recreational Opportunities 07 Limited recreational values/opportunities/potential 25 No camping areas 32 Recreation opportunities/potential good/high/excellent 48 Camping opportunities good/abundant 59 Diverse recreational opportunities 66 Woodcutting 67 Developed recreation sites 70 Agates 74 Picnicking 92 Horseback riding 97 Hiking 98 Cross-country skiing 99 Snowmobiling Recreational Use Boating 06 Low recreational use 20 Moderate recreational use 39 Low/secondary water-based use 43 Low population base nearby/mainly local use 49 High recreational use 76 Close to large urban area 10 Useable by jetboats 19 Floating difficult 30 Good boating 36 Boating opportunities limited 58 Few people float/minor use 60 Commercial floating 71 Challenging rapids 88 Heavy floating use B-4 Fishing Hunting EXPLANATIONS FOR VALUE CLASS ASSIGNMENTS (REC.DBF) (continued) 08 Fishery good/excellent/popular 24 Fishing is poor/limited 72 Paddlefish 78 Fishing use light 83 Fishing fair/moderate 09 Waterfowl hunting 21 Hunting popular/good potential 26 Hunting limited 35 Big game hunting good/excellent 51 Upland bird hunting 89 Wildlife abundant (hunting & non-consumptive use) Wildlife Habitat 09 Wildlife/birds abundant 15 Poor riparian habitat 42 Grizzly habitat 45 Excellent riparian habitat 79 Wildlife habitat/range/habitat 87 Spawning ground 90 Special wildlife species (grayling/mtn goat/cutthroat, etc) Scenic Attributes Access 01 Scenic quality good/substantial/outstanding 18 Unusual topography/environment (rugged /canyons /bad lands /gorges) 27 Scenic quality low/limited/typical/uniform 52 Scenic quality moderate/nice 13 Access restricted/limited/poor 17 Access good/abundant 22 Private property/mostly private lands 23 Good trail system/access 31 Access moderate 41 Mostly public land 82 Fences across stream/beaver dams 85 Mixed public and private B-5 EXPLANATIONS FOR VALUE CLASS ASSIGNMENTS (REC.DBF) (continued) Level of Development 02 Primitive country/natural/pristine 11 Diversion dams/irrigation structures 14 Logging/clear cuts 40 Major fire impact 53 Much traffic/congested 55 Highway/road parallels stream 57 Flows through town/city 62 Solitude 63 Riprap 64 Agricultural lands 68 HomeSite development 69 Development present (golf course/ski area) 73 Remote 77 Considerable evidence of man 81 Railroad parallels stream Water Quality 03 Clean water/good quality 28 Muddy water 65 Municipal water supply 80 Poor water quality Other Attributes 04 Historical significance 38 Special management area 44 Potential unknown 46 Indian religious area/prehistoric sites/pictographs 56 Unique resource 75 Possible recreational river candidate 86 Flows into/provides access to wilderness area 91 Historical site/mining activity B-6 APPENDIX B.4 CODES FOR FISH, WILDLIFE & PARKS RIVER DRAINAGES (NOTE: THESE ARE THE FIRST TWO DIGITS OF THE DFWP WATER CODE) 01 Beaverhead 02 Big Hole 03 Bitterroot 04 Blackfoot 05 Clark Fork (below Bitterroot River) 06 Clark Fork (above Bitterroot River) 07 Flathead (below South Fork) 08 Flathead (above & including South Fork) 09 Gallatin 10 Jefferson 11 Kootenai 12 Little Missouri 13 Madison 14 Marias 15 Milk 16 Missouri (below Marias River) 17 Missouri (above Marias River) 18 Musselshell 19 St. Mary 20 Sun 21 Yellowstone (below Bighorn River) 22 Yellowstone (above & including Bighorn River) B-7 1- z CO < z (0 m 3 < O ffi cr lU z o o -1 IVER RtV (0 < m o oc c a. ir o >- z UJ -D UJ z o > O OT a. to LLOWS TLE Ml > o tc (0 1 < 2 UJ f- \- o o o >- -I « h- o o CO < a oc UJ > APPENDIX B.5 CODES FOR WILDLIFE SEASONAL USE (WILDLIFE. DBF) Mildlife Seasonal Use Codes 1 Year-round 2 Spring 3 Summer 4 Fall 5 Winter 6 Spring and Summer 7 Spring and Fall 8 Spring and Winter 9 Surmier and Fall 10 Summer and Winter B-9 APPENDIX C SAMPLES OF REPORT PRINTOUTS APPENDIX C.2 EXAMPLE OF VALUE CLASS SUMMARY BY REACH MONTANA RIVERS STUDY •3UW«ARy OF VALUE CLASS ASSIGfWENTS BY REAO' 01/05/67 - lS:il SET FILTER TO CODEO "10999S" .Ml. CODE \) 'ITWAi" INDEX ON RIV mUE TO DESCRIPl Page 1 RIVER NAME ABBOT CREEK ADA CREEK ADAIR CREEK ADAMS CREEK MATER CODE .RESOURCE REACH ADAMS CREEK ADDITION CREEK ADOLPH CI«EK ADVENT CREEK (eCAS CREEK AFTERBAY CREEK (KIRN CREEK AKINKaD ND : 6 01/05/S7 19:30:14 IINDEX ON WftTER CODE (or rgcrrnal Index) TO 6E01 BITE NUMBER: b-6 DFWP RIVER CODE: SITE NPME: Gardiner i_andslides TYPE: landslide. . STftTUS: Proposed NNL.Driority 1 -D, Ye 1 1 owst one NP COUNTIES: PftRK ; ; RIVER NOME: Gardiner River RIVER MILES O - £. 0 QUODS: Gardiner (1955 . 15 » (19 . ) BLM 1:100000 MAP NUMBER: 52 LEGftL: T- 95 -T R- a E - R SECTIONS: SWl/4, Sc:5, S26, Sd.7 , N3/A, S34, N3/4, S35, Wl/2, NW1/h, S36 LATITUDE: - LONGITUDE: DESCRIPTION: See Hyndrnar. and ftlt (198£), pp. 109-110 (#10). Fields and Melton (19S5) suggest that landslide extends to NW as far as Yankee Jim Canyon. SOURCES: : See description ACCURACY : 1 UNIQUENESS: 3 DESI8NATION: 1 USE: SCIENTIFIC VALUE: FINAL VALUE CLASS: 1 FILE: GEO. dbf RECORD NO: 17 01/05/87 19:30:S0 IINDEX ON WATER CODE (or Normal Index) TO GEOl SITE NUMBER: G-17 DFWP RIVER CODE: SITE NAME: Lower Shonkin Sag TYPE: underfit stream, , STATUS: Proposed NNL, priority 1-D COUNTIES: CHOU ; ; RIVER NAME: Closed basin RIVER MILES QUADS: Shonkin (197c: , 7. 5 ) Montague (197d , 7. 5 ) BLM 1:100000 MAP NUMBER: £9 LEGAL: T- ££ N -T R- 9 E - R 10 E SECTIONS: Sl£, Sl/4, 31, S7, 8, 9-1 1 , SI /4, 5, 6, Wl/£, Sl£, W3/4, SI 3, E3/4 LATITUDE: - LONGITUDE: DESCRIPTION: See Hyndman and ftlt (198£), pp. 1&4-169 (#£4) SOURCES: : Bee description ACCURACY: 1 UNIQUENESS: i. DESIGNATION: 1 USE: SCIENTIFIC VALUE: FINAL VALUE CLASS: i C-5 APPENDIX C.3.4 EXAMPLE OF RESOURCE AREA DETAILED REPORT _ RECREATION MONTANA RIVERS STUDY RECREOTION fiSSESSMENT DETAILS 01/05/87 - 19:33 Page INDEX ON WATER CODE (or Normal Index) TO RECl CODE: 010040 SEGMENT NO. : LOWER BOUNDARY: DFWP REGION: 3 WATER CHARACTER: ACTIVITY RATINGS MOTOR BOATING TUBING: TENT CAMPING: DRIVING: HUNGRY HOLLOW RIVER NAME: ALDER GULCH CR 1 LENGTH: 14 km RUBY R UPPER BOUNDARY; RATING AGENCIES: USPS ONLY Not boated MONTHS/ YR BOATABLE: O (1 = Primary activity, £ = Secondary activity) O CANOEING: O 0 SWIMMING: O £ CAR CAMPING: 2 1 VIEWING: 1 KAYAKING: O BOAT FISHING: O TRAIL USE: O PICNICING: 2 USE LEVEL: Unknown Heavy ACCESS : Rural USE ESTIMATE: SCENIC QUALITY: Outstanding ROS CLASS NO. DEVELOPED RECREATION SITES: 2 VALUE CLASS ASSIGNMENTS (1 = outstanding, 2 = substantial, 3 = moderate, 4 = limited, 5 = unclassified, O = not DFWP: O BLM: O USFS: 2 FINAL VALUE: £ RAFTING: SHORE FISH: MTR TRAILER: Moderate rated) O 1 O CODE: 01048O RIVER NAME: BEAVER CREEK SEGMENT NO, : 1 LENGTH: 6 km LOWER BOUNDARY: W FK RUBY R UPPER BOUNDARY: DFWP REGION: 3 RATING AGENCIES: DFWP only HEADWATERS Not boated MONTHS/ YR BOATABLE: O (1 = Primary activity, 2 = Secondary activity) WATER CHARACTER: ACTIVITY RATINGS: MOTOR BOATING: TUBING: TENT Cffl«1PING: DRIVING: USE LEVEL: Unknown SCENIC QUALITY: ROS CLASS: NO. DEVELOPED RECREATION SITES: O VALUE CLASS ASSIGNMENTS (1 = outstanding, 2 = substantial, 3 = moderate, 4 = limited, 5 = unclassified, O = not DFWP: 5 BLM: O USFS: O FINAL VALUE: 5 o CANOEING: 0 KAYAKING: O RAFTING: O o SWIMMING: 0 BOAT FISHING: 0 SHORE FISH: 0 o CAR CAMPING: 0 TRAIL USE: 0 MTR TRAILER: 0 o n VIEWING: O USE ESTIMATE: PICNICING": ACCESS: 0 » ■■ rated) 21 km CLARK CYN DAM RIVER NAME: BEAVERHEAD R 2 NAME: UPPER BEAVERHD LENGTH: DILLON UPPER BOUNDARY: RATING AGENCIES: All agencies Mi nor /Moderate rapids MONTHS/YR BOATABLE: 7 (1 = Primary activity, £ = Secondary activity) CODE: 010500 SEGMENT NO. : LOWER BOUNDARY: DFWP REGION: 3 WATER CHARACTER: ACTIVITY RATINGS MOTOR BOATING TUBING: TENT CAMPING: DRIVING: USE LEVEL: Unknown USE ESTIMATE: SCENIC QUALITY: Subst /Moderate ROS NO. DEVELOPED RECREATION SITES: 3 VALUE CLASS ASSIGNMENTS (1 = outstanding, 2 = substantial, 3 = moderate, 4 = limited, 5 = unclassified, O = not DFWP: 1 BLM: 1 USFS: 1 FINAL VALUE: 1 2 2 £ 1 CANOEING: SWIMMING: CAR CAMPING: VIEWING: USE 1 0 £ £ KAYAKING: BOAT FISHING: TRAIL USE: PICNICING: 1 1 O 1 RAFTING: SHORE FISH: MTR TRAILER: 1 1 £ Heavy /Moderate ACCESS: Moderate CLASS: Transition rated) C-6 APPENDIX C.3.5. EXAMPLE OF RESOURCE AREA DETAILED REPORT - CULTURAL FEATURES MONTftNft RIVERS STUDY CULTURftL FILE RESOURCE / DUMP 01/05/87 - 19:36 Pagt INDEX ON RIV NAME TO FOORl 050016 FINAL_VAL 1 REACH 1125 RESOURCE C MAP_NAME PLAINS RIV_NAME ADAMS CREEK VALUE_A VALUE_B VALUE_C VALUE. _D UP_TWP 15N UP_RAN 23W UP_SEC 22 LO_TWP 15N LO_RAN 23W LO_SEC 27 170032 FINAL_VAL 1 REACH 426 RESOURCE C MAP_NAME TOWNSEND RIV_NAME ADOLPH CREEK VALUE_0 VALUE_B VALUE_C VALUE. _D UP_TWP 04N UP_RAN 05E UP_SEC 27 LO_TWP 04N LO_RAN 05E LO_SEC 08 080100 FINAL_VAL 1 REACH 169 RESOURCE C MAP_NAME WHITEFISH RIV_NAME AKINKOKA CREEK VftLUE_A VALUE_B VALUE_C VALUE .D UP_TWP 36N UP_RAN 23W UP_SEC 34 LO_TWP 36N LO_RAN 23W LO_SEC 26 019110 FINAL_VAL 1 REACH 710 RESOURCE C MAP_NAME DILLON RIV_NAME ALBERS SLOUGH VfiLUE_A VALUE_B VALUE_C VALUE. .D UP_TWP 05S UP_RAN 07W UP_SEC 30 LO_TWP OSS LO_RAN 07W LO_SEC 20 060057 FINAL_VAL 1 REACH 778 RESOURCE C MAP_NAME ENNIS RIV NAME ALDER GULCH VALUE_A VALUE_B VALUE_C VALUE. .D UP_TWP 07S UP_RAN 03W UP_SEC 12 LO_TWP 06S LO_RAN 03W LO_SEC 08 010040 FINAL_VAL 1 REACH 734 RESOURCE C MAP_NAME DILLON RIV_NAME ALDER GULCH CREEK VALUE_A VALUE_B VALUE_C VALUE. .D UP_TWP 05S UP_RAN 04W UP_SEC 32 LO TWP 053 LO RAN 04W LO SEC 32 C-7 APPENDIX C.4 EXAMPLE OF STRAIGm: FILE DUMP OF DESCRIP.DBF MONTANA RIVERS STUDY DESCRIPTION FILE RESOURCE / DUMP 01/05/87 - 19:39 Page INDEX ON RIV NAME TO DESCRIPl Code 109999 River Name: Rec 3080 Region TRS County EPA # Tr-ib To Hyd. Unit Length 0.0 Final Values: (wild) (fish) (cult) " Name: Region TRS County EPA # T>~ib To Hyd. Unit Length O. O Final Values: (wild) (fish) (cult) (nat) Overall Final Value : Rec 3814 (geo) U (rec) Code OaOOaO River Name: ABBOT CREEK Rec 1127 Region 1 TRS T30NR19W05ADC County FLAT. EPA # Trib To FLATHEAD RIVER Hyd. Unit 17010208 Length 9.7 Final Values: (wild) 5 (fish) 4 (cult) (nat) (geo) irec} Overall Final Value : 4 Code 080040 River Name: ADA CREEK Region 1 TRS T£gNR18WOO County EPA # Trib To Hyd. Unit 17010209 Length O. O Final Values: (wild) £ (fish) (cult) Overall Final Value : 2 (nat) Rec 3006 (geo) (rec) Code 220014 River Name: ADAIR CREEK Rec 2245 Region 3 TRS T01SR10E09 County PARK. EPA # Trib To SHIELDS RIVER Hyd. Unit 10070003 Length 6.0 Final Values: (wild) 2 (fish) 3 (cult) (nat) (geo) (rec) Overall Final Value : 2 Code 170016 River Name: ADAMS CREEK Rec 1855 Region 4 TRS T12NR07E26CDBC County MEA6. EPA « Trib To SHEEP CREEK Hyd. Unit 10030103 Length 11.6 Final Values: (wild) (fish) 4 (cult) (nat) (geo) (rec) Overall Final Value : 4 Code 050016 River Name: ADAMS CREEK Region 2 TRS T15NR23W33 County EPA # Trib To Hyd. Unit 17010204 Length O. O Final Values: (wild) 2 (fish) (cult) 1 Overall Final Value : 1 (nat) Rec 2857 (geo) (rec) C-8 APPENDIX D LIST OF CONTACT PERSONNEL ^k}^thMest River Study Contact Personnel Pat Graham Larry Peterman MDFWP MDFWP 1^20 E. Sixth Avenue 1^20 E. Sixth Avenue Helena, MT 59620 Helena, MT 59620 Larry Thompson Natural Resource Information System Montana State Library 1515 E. Sixth Avenue Helena, MT 59620 ^^'^-3115 Sandy Fiance MDFWP 1^20 E. Sixth Avenue Helena, MT 59620 ^A^-3795 Janet Decker-Hess MDFWP P.O. Box 67 Kalispell, MT 59903 752-5501 ext. 220 B?9I?^ii9I'' Stewart Allen University of Idaho Department of Wi Id lands/Recreation Management it2a Veatch Moscow, ID 838^3 Home: (208) 885-7911 Office: (208) 885-7^28 Fi^sheri^es: Bob McFar land /Randy Merry MDFWP P.O. Box 5 Bozeman, MT 59717 99^-6355 Larry Thompson (see address above) D-1 DOFJBP-a30 May 1987 IC