Licensing A project of Ecotrust
STATE OF OREGON DEPARTMENT OF GEOLOGY AND MINERAL INDUSTRIES SUITE 965 800 NE OREGON ST. #28 PORTLAND, OREGON 97232
OPEN-FILE REPORT O-93-8
Documentation for the Mineral Information Layer for Oregon by County (MILOC93)
Database By Jerry J. Gray, Economic Geologist Oregon Department of Geology and Mineral Industries
----------------------------------------------------------------------
Overview: This report provides a statewide mineral database in dBASE III+ format that can be imported to computerized geographic information systems (GIS), such as those being used by the U.S. Bureau of Land Management (BLM), U.S. Bureau of Mines (USBM), U.S. Forest Service (USFS), U.S. Geological Survey (USGS), agencies of the State of Oregon, Oregon counties, and the private sector. This computer data base gives location, commodity, and other data for an estimated 7,899 mineral occurrences, prospects, and mines in Oregon. Because each site has latitude, longitude, and Universal Transverse Mercator (UTM) coordinates, this layer can be used with many geographic information systems. The data base has utility for local, county, state, and federal planning; for exploration and mining firms; and for other private interest groups.
Sources: Data sources include the USGS CRIB/MRDS and USBM MILS main frame data bases of mineral occurrences, prospects, and mines. For Oregon, these data are complete, up-to-date, and acceptably uniform in geographic coverage. However, these data bases have not been added to since 1981 data were downloaded into dBASE III+. Of the 429 USGS CRIB/MRDS fields, 89 were selected by a committee of federal, state, and county agencies as those that were needed for each agency's planning efforts. After two years of use, recommendations were received from agencies and private parties on which fields should be eliminated, combined, and/or added. Changes were made so that the database now has 84 fields. The records in the federal data bases were edited by the Oregon Department of Geology and Mineral Industries (DOGAMI) professional staff. Duplicate records were eliminated. An additional 2,755 records from the DOGAMI Mined Land Reclamation program are included in the data base as of December 1992. There are now a total of 7,899 mineral occurrences, prospects, exploration targets, and mines in the data base. Data Description As in all data bases, the field name given to a data field may not explain adequately what is in that field.
Field Names and Explanations:
1. SITE_NAME - Self explanatory
2. SYNONYM - Other names that the site has had over time, or in the case of placers, names of other gravel bars along a river segment for which one location was chosen for the site name
3. OWNER - Self explanatory
4. COUNTY - Self explanatory
5. MINING_DIS - Mining district
6. USBLM_DIST - USBLM districts (in which the site is located) Field Codes are as follows: BURN Burns COOS Coos EUGE Eugene LAKE Lake MEDF Medford PRIN Prineville ROSE Roseburg SALE Salem VALE Vale
7. USFS_DIST USFS forest (in which the site is located) Field Codes are as follow: Blank Sites not on any federal forest CRG Columbia River Gorge National Scenic Area DES Deschutes FRE Fremont MAL Malheur MTH Mt. Hood OCH Ochoco ROG Rogue River SIS Siskiyou SIU Siuslaw UMA Umatilla UMP Umpqua WAW Wallowa-Whitman WIL Willamette WIN Winema
8. DRAIN River basin Field Codes (taken from the Oregon Drainage Basin Map-scale 1:1,000,000 as defined by Oregon Water Resources Dept.) are as follows: 01 North Coast 02 Willamette 03 Sandy 04 Hood 05 Deschutes 06 John Day 07 Umatilla 08 Grande Ronde 09 Powder 10 Malheur 11 Owyhee 12 Malheur Lake 13 Goose & Summer Lakes 14 Klamath 15 Rogue 16 Umpqua 17 South Coast 18 Mid Coast
9. HYDR_UNT USGS hydrologic units taken from Hydrologic Unit Map-1974 State Of Oregon-scale 1:500,000
10. PHYSIOG Physiographic/geomorphologic provinces Field Codes are as follows: 10 Columbia Plateau (Federal Code) 12 Basin & Range (Federal Code) 13 Pacific Ranges (Federal Code) The NAMES in this field are taken from the Oregon Physiographic Map
11. LAND_ST Land status/ownership Field Codes are as follows: 00 Undetermined 01 Private 20 County 30 State 31 State Forest 32 State Park 33 State Offshore 40 Federal 41 National Forest 42 National Recreation Area 43 National Wilderness Area 44 National Primitive Area 45 National Park 46 National Monument 47 Indian Reservation 48 National Offshore 49 BLM 50 Military Reservation
12. USGS_NUM The site number from the USGS CRIB/MRDS data base or if the number starts with "OR" from DOGAMI THIS IS THE UNIQUE RECORD NUMBER
13. USBM_NUM The site number from the USBM MILS data base
14. USBLM_NUM Site numbers fron BLM records
15. DOGAMI_MLR The site number given by the DOGAMI Mined Land Reclamation program
16. PRMT - Type of Mined Land Reclamation Permit Field Codes are as follows: CO County exempt APA Application received-aggregate APG Application received-government APM Application received-metals APP Application received-placer APX Application received-exploration OPA Operating permit-aggregate OPG Operating permit-government OPM Operating permit-metals OPP Operating permit-placer XPA Operating permit-exploration-aggregate XPG Operating permit-exploration-government XPM Operating permit-exploration-metals XPP Operating permit-exploration-placer VP Vegetation permit TE Total exemption LEP Limited exemption-prior mined LEV Limited exemption-valid contract PPA Provisional operating permit-aggregate PPG Provisional operating permit-government PPM Provisional operating permit-metals PPP Provisional operating permit-placer PPX Provisional operating permit-exploration
17. PRMTSTATUS The status of the permit Field Codes are as follows: C Closed N New A Amendment R Bond pulled
18. UPDATE_BY The name of the person updating the site record
19. UP_DATE The date the site record was updated
20. LOCATION The direction and distance from some feature, such as a town
21. TOWNSHIP Self explanatory
22. T_CODE The T_CODE is formed by subtracting north township from 10 and adding 10 to those south townships NOTE - Use of T_CODE permits sorting by township without the ambiguity of receiving both north and south townships of the same number.
23. RANGE Self explanatory
24. R_CODE The R_CODE is formed by subtracting west ranges from 20 and adding 20 to those east ranges. NOTE - Use of R_CODE permits sorting by range without the ambiguity of receiving both east and west ranges of the same number.
25. SECTION Self explanatory
26. SECT_FRACT Section fraction. For example NW NW NW indicates the northwest quarter of the northwest quarter of the northwest quarter of the section; a single letter such as N indicates the north half of the section
27. LAT Latitude
28. LONG Longitude
29. UTM_N Universal Transverse Mercator coordinate number, getting larger to the north
30. UTM_E Universal Transverse Mercator coordinate number, getting larger to the east
31. UTM_Z Universal Transverse Mercator grid zone NOTE - Zone 10 for longitude 120 degrees and west, and Zone 11 for 119 degrees-59 minutes-59 seconds and east
32. Q1_SCALE Map scale 1:100,000 for topographic quadrangle map one
33. QUAD1 Name of the 1:100,000-scale topographic quadrangle map in which the site is located
34. Q2_SCALE Map scale of 1:24,000 or 1:62,500 for topographic quadrangle map two
35. QUAD2 Name of the 7-1/2-minute (1:24,000-scale) or 15-minute (1:62,500-scale) topographic quadrangle map
36. ALTITUDE Elevation in feet or meters above sea level
37. STATUS Site type: mineral occurrence, raw prospect, developed prospect, or mine Field Code are as follows: 1 Mineral occurrence (no workings and/or production) 2 Raw prospect (minor workings no production) 3 Developed prospect (workings but no production) 4 Mine (present or past producer)
38. COMOD_PRES All commodities listed in the literature for this site Field Codes are element symbols for all metallic and spelled-out names for all others. NOTE - Use "STONE" for all materal from quarries. The commodity "STONE" can be modified by adding a rock name such as STONE(BASALT). Use "SAND & GRAVEL" for all sand or gravel pits. This commodity can be modified such as "SAND & GRAVEL(SAND)" or "SAND & GRAVEL(FILL)". Use "CLAY" for all clay commodities and modify such as "CLAY(BENTONITE)". Use GEMSTONES for all gemstones and modify such as GEMSTONES(AGATE).
39. COMOD_PROD Commodities produced and sold or used Field Codes are the same as the COMOD_PRES field
40. ORE_MAT Ore material (valuable minerals or mineral material)
41. GANGUE Gangue material (waste minerals or mineral material)
42. PRODUCTION Self explanatory Field Code are "YES"or "NO" (for either current or past)
43. PROD_SIZE Production size Field Code are "SMALL", "MEDIUM", or "LARGE"
44. DEPOS_TYP Deposit type
45. MIN_AGE Mineralization age Field Codes are as follows: QUAT Quaternary HOLO Holocene PLEIS Pleistocene TERT Tertiary PLIO Pliocene MIO Miocene OLIGO Oligocene EO Eocene PALEO Paleocene CRET Cretaceous JUR Jurassic TRI Triassic PERM Permian PENN Pennsylvanian CARB Carboniferous MISS Mississippian DEV Devonian SIL Silurian ORD Ordovician CAMB Cambrian PREC Precambrian ARCH Archean HUR Huronian CEN Cenozoic MES Mesozoic PAL Paleozoic
46. HOST_ROCK Rock type hosting the mineralization
47. HOST_R_AGE Host rock age Field Codes same as those for MIN_AGE
48. IGNEOUS_R Igneous rock associated with the mineralization
49. IG_R_AGE Igneous rock age Field Codes same as those for MIN_AGE
50. ALTERATION Self explanatory
51. ORE_CNTRL Geologic controls for the ore body
52. DEP_DESCOM Deposit description comments
53. GEOL_COM Comments concerning geology of site
54. DESC_WORK Type of mine workings Field Choices are "SURFACE", "UNDERGROUND", or "BOTH"
55. YR_DISC Year the mineral discovery was made
56. YR_1ST_PRO Year that mineral production started
57. YR_LASTPRO Year that production stopped
58. WRKDES_COM Description of exploration and/or mine workings
59. CP_ITEM1 First commodity with recorded production
60. CP_AMT1 Cumulative-production amount for first commodity
61. CP_UNIT1 Units (ounces, pounds, tons) for first commodity
62. CP_YEAR1 Year to calculate cumulative-production for first commodity
63. CP_ITEM2 Second commodity with recorded production
64. CP_AMT2 Cumulative-production amount for second commodity
65. CP_UNIT2 Units (ounces, pounds, tons) for second commodity
66. CP_YEAR2 Year to calculate cumulative-production for second commodity
67. CP_ITEM3 Third commodity with recorded production
68. CP_AMT3 Cumulative-production amount for third commodity
69. CP_UNIT3 Units (ounces, pounds, tons) for third commodity
70. CP_YEAR3 Year to calculate cumulative-production for third commodity
71. CP_ITEM4 Fourth commodity with recorded production
72. CP_AMT4 Cumulative-production amount for fourth commodity
73. CP_UNIT4 Units (ounces, pounds, tons) for fourth commodity
74. CP_YEAR4 Year to calculate cumulative-production for fourth commodity
75. CP_ITEM5 Fifth commodity with recorded production
76. CP_AMT5 Cumulative-production amount for fifth commodity
77. CP_UNIT5 Units (ounces, pounds, tons) for fifth commodity
78. CP_YEAR5 Year to calculate cumulative-production for fifth commodity
79. CP_ITEM6 Sixth commodity with recorded production
80. CP_AMT6 Cumulative-production amount for sixth commodity
81. CP_UNIT6 Units (ounces, pounds, tons) for sixth commodity
82. CP_YEAR6 Year to calculate cumulative-production for sixth commodity
83. GEN_COM General comments concerning site
84. RF1 Published or unpublished reference #1
85. RF2 Published or unpublished reference #2
86. RF3 Published or unpublished reference #3
87. RF4 Published or unpublished reference #4
88. RF5 Published or unpublished reference #5
89. RF6 Published or unpublished reference #6
Record Location Accuracy: Records in the MILOC data base were obtained from the USBM MILS data base, the USGS CRIB/MRDS data base, and the DOGAMI Mined Land Reclamation files. The records in the two federal data bases were obtained mainly from published sources, such as state, private, USGS, USBM, and from the USFS and BLM.
For the first two federal data bases, the locations of mines, prospects, and mineral deposits taken from older publications are often reported in narrative format, while those in newer publications are often reported by subdivisions of a section of land or by latitude and longitude. Most locations reported in these two data bases have not been field checked. Therefore, they are reference-specific data bases that also contain some site-specific records. Although the data bases require latitude, longitude, and UTM coordinates for entry of each record, the quality of the locational description varies widely among the information source documents. The locations generally are accurate within a mile and most to within a quarter mile.
All the records with a DOGAMI_MLR were taken from DOGAMI's Mined Land Reclamation file and are accurate within a quarter of a mile, and most within an eighth of a mile. Most latitude, longitude, and UTM coordinates for the two federal data bases were derived manually from topographic maps (1:62,500 or 1:24,000). For those records from the DOGAMI Mined Land Reclamation files, the latitude, longitude, and UTM coordinates were computer generated by digitizing the mine sites plotted on Oregon State Highway Division county maps, which have an approximate scale of one-half inch equals one mile.
Appendix 1 contains the "Source Graphic Lineage Report" and "Digital Output Format Standards" from the Oregon State Map Advisory Council report, "Digital Spatial Standards and Procedures," which was prepared by the GIS Standards and Procedures Working Group of the State Map Advisory Council, March 22, 1990, sections 2.6 and 4.0.
Uncompressing data from the disks: The complete 30-megabyte MILOC93 data base has been compressed using LHarc 1.13 and is contained in two files called MILOC93A.LZH and MILOC93B.LZH, each on its own high density 5-1/4" disk. The desired file should be copied to your hard disk and MUST be uncompressed before attempting to use the data. Table 1 shows the file names, number of records, and the size of the files for each county data base. Check to see how large each county data base is to ensure that you have room on your hard disk to uncompress it. A suggested procedure for uncompressing a data base might be as follows:
At this point, you have a usable dBASE III+ file for Baker County. If you are using MILOC93B.LZH from Disk 2 and wish to uncompress a data base other than Baker County or use a different sub-directory name, then substitute the appropriate changes in the above instructions. If you already have LHARC in the path on your hard disk, you will not need to copy it from the distribution disks. See LHarc.doc for the complete instructions on using LHarc for compressing data files.
Table 1. County file names, number of contained records, and byte size, both original and packed, for the two floppy disks MILOC93A.LZH and MILOC93B.LZH Floppy File name # Records Bytes Disk Original Packed MILOC93A.LZH
Using the Data Base: After a county file has been uncompressed, it can be used with dBASE III+ or compatible software programs.
Getting Started: The following are some dBASE III+ commands that will get a person started:
Type DBASE and press enter. If the hard drive has a different setup, you may need to get to the dBASE subdirectory by another route.
With the dot prompt showing, type USE (county file name) and press enter. Now that data file is in dBASE.
Type BROWSE and press enter. The data fields and records can be viewed and changed.
Hard Copy: If a hard copy of the data is needed, the program PRMILO93.PRG written by Steven Baker of the Oregon Department of Energy can be used. This is a dBASE III+ compatible program to print out one of the county data bases, one site per page. Your printer must be in compressed mode, 17 characters per inch and should be placed into the compressed mode before starting the program. Type DO PRMILO93 and press enter. The program will ask the name of the data base to print. For example, answering with LANE93 will load and print the LANE93.DBF file. In this case, the command will print all 300 records, which takes a lot of paper. The data base file to print must be in your default directory. (The file, SAMP_PRN.TXT, is an approximation of the hard copy for Black Butte Mine from the LANE93.DBF. To print this file, set your printer to 17 characters per inch and use the DOS PRINT command.)
Data for Part of County: If data are needed for only one part of a county, another file can be generated by typing COPY TO (file name) FOR (field name)="(insert statement that will give you the sort you want)". NOTE ALL DATA IN THE DATA BASE ARE IN CAPITAL LETTERS. An example is: COPY TO (file name) FOR TOWNSHIP="30S" .AND. RANGE="40W". The T_CODE AND R_CODEs could have been used. In that case the command would be COPY TO (file name) FOR T_CODE="40" .AND. R_CODE="60". The new file will now contain all the records that fall within that township and range. If data based on a commodity is needed, the Substring symbol should be used so that all sites that list that commodity can be found. In this case the command would be COPY TO (file name) FOR "MN"$ COMOD_PRES. The new file will have all sites that manganese was listed under the field COMOD_PRES. To get a hard copy of the records, type DO PRMILO93 and press enter. When the question "File Name" appears on the screen, type the name of the new file and press enter. All the records in the new file will be printed out. How To Add Records To The Data Base For federal, state, local agencies and/or private parties that wish to add to the data base, PLEASE send the records on a floppy disk to the Department office in your area. The file should be a ".dbf" file with the same structure as one of MILOC93.LZH county files. NOTE ALL DATA SHOULD BE ENTERED WITH CAPITAL LETTERS.
How To Correct Record Data: If errors are found in this data base, PLEASE make a hard copy of that record using PRMILO93.PRG. Then make the correction on the hard copy with a color pen. The hard copy should be sent to the Department office in your area.
Where To Send Data Base Additions And Corrections:
Data base additions and corrections for counties in northwest Oregon (Benton, Clackamas, Clatsop, Columbia, Hood River, Lincoln, Linn, Marion, Multnomah, Polk, Tillamook, Washington, Yamhill) should be sent to: Ronald P. Geitgey, Oregon Department of Geology and Mineral Industries, Suite 965, 800 N.E. Oregon Street #28, Portland, Oregon 97232, (503) 731-4100 FAX (503) 731-4066.
Data base additions and corrections for counties in southwest Oregon (Coos, Curry, Douglas, Jackson, Josephine, Klamath, Lake, and Lane) should be sent to: Frank R. Hladky, Oregon Department of Geology and Mineral Industries, 5375 Monument Drive, Grants Pass, Oregon 97526 (503) 476-2496.
Data base additions and corrections for eastern Oregon counties (Baker, Crook, Deschutes, Gilliam, Grant, Harney, Jefferson, Malheur, Morrow, Sherman, Umatilla, Union, Wallowa, Wasco, and Wheeler) should be sent to: Mark L. Ferns, Oregon Department of Geology and Mineral Industries, 1831 1st Street, Baker City, Oregon 97814, (503) 532-3133.
Acknowledgments: This data base is the result of interagency and individual cooperation. Agencies involved in this project include: BLM, USBM, USFS, USGS, Oregon Department of Energy, Oregon Department of Forestry, Oregon Department of Geology and Mineral Industries (DOGAMI), Oregon Department of Land Conservation and Development, Department of State Lands, Oregon Department of Transportation - Highway Division, Oregon Department of Water Resources, counties such as Deschutes, Polk, and Yamhill, and private timber firms. Steven Baker, Oregon Department of Energy, was indispensable to this project. Steve downloaded USBM and USGS raw data into dBASE III+ at least twice and wrote many programs (including the PRMILO93.PRG), spending many long hours of his own time on this project. James Ridenour, USBM, provided MILS data. Ray Arndt, USGS, provided CRIB/MRDS data. Eric Hoffman, BLM, and Robert Fujimoto, USFS, arranged partial funding for the project. Daniel Wickwire, BLM, digitized the Department's Mined Land Reclamation sites. DOGAMI staff Mark E. Neuhaus, Paul E. Staub, and John D. Beaulieu provided advice and technical review.
Maintenance: To provide for a usable data base in the future, DOGAMI recognizes the following needs:
1. The data base should be updated at least once a year.
2. The data base should be customized for use by other agencies and/or subunits of agencies.
3. An outreach program to educate local, state, and federal agencies on the use and updating of MILOC93 should be continued.
Appendix 1. Source Graphic Lineage Report and Data Quality Report The MILOC93 data base conforms to the Oregon State Advisory Council Digital Spatial Standards and Procedures, prepared by the GIS Standards and Procedures Working Group of the State Map Advisory Council, March 22, 1990, listed below. Information following colons indicates manner in which DOGAMI met these standards.
2.6 Source Graphic Lineage Report
2.6.1 The lineage of the source graphic must be recorded at the time of data capture. The database lineage will be available to other agencies for evaluation of database compatibility. The combination of the data capture Source Graphic Lineage Report and the output Data Quality Report, described in section 4.2, constitute the "Truth in Labeling" concept which is necessary in digital databases.
2.6.2 The Source Graphic Lineage Report must be available separately from the data transferred.
2.6.3 The Source Graphic Lineage Report must contain the following:
2.6.3.1 Name of source graphic: Mineral Industry Location System (MILS) of U.S. Bureau of Mines, Computerized Resources Information Bank (CRIB) of U.S. Geological Survey renamed to Mineral Resource Data System (MRDS), and DOGAMI Mined Land Reclamation program (MLR).
2.6.3.2 Scale of source graphic: 1:1,000 to 1:62,500.
2.6.3.3 Scale at which data are captured: 1:1,000 to 1:62,500.
2.6.3.4 Source Agency: MILS - U.S. Bureau of Mines; CRIB/MRDS - U.S. Geol. Survey; MLR - Oregon Dept. of Geol. & Mineral Indus. (DOGAMI).
2.6.3.5 Datum, if source graphic is in NAD 83: Not specifically available, but all topographic maps in use at the time of capture of original data entry were NDA-27.
2.6.3.6 Compilation date of source graphic: Ongoing to 1990 for MILS, 1980 for MRDS, and 1990 for DOGAMI-MLR.
2.6.3.7 Revision dates of source graphic: Ongoing within dates specified in 2.6.3.5.
2.6.3.8 Media used: Paper.
2.6.3.9 Quality of the media used: New paper topographic maps meeting national map accuracy standards.
2.6.3.10 Category of the data: Mineral prospects and mines.
2.6.3.11 Projection of the source graphic: Polyconic as used for U.S. Geological Survey topographic maps.
2.6.3.12 Date of automation: Various dates prior to 1990 for MILS, 1980 for USGS and 1990 MLR. May 5, 1991, for this MILOC93 data base.
2.6.3.13 Name of agency collecting the data: MILS - U.S. Bureau of Mines; CRIB/MRDS - U.S. Geological Survey; and MLR - DOGAMI. DOGAMI collected most data for USGS under subcontract.
2.6.3.14 Name of contractor if data are collected by contract: CRIB/MRDS - DOGAMI.
2.6.3.15 Software system, procedure, and version number used for actual data capture: MILS - Contact John Dillon, MAS Data Base Administrator, Minerals Availability Field Office, P.O. Box 25407, Bldg. 53, Denver Federal Center, Denver, CO 80225; CRIB/MRDS - Contact Raymond E. Arndt, Chief MRDS Project, U.S. Geological Survey, 920 National Center, Reston, VA 22092; MLR - Contact Daniel W. Wickwire, U.S. BLM, P.O. Box 2965, Mail Stop 995.6, Portland, OR 97208.
2.6.4 Any database created by merging information obtained from distinct sources must be described at sufficient detail to identify the actual source for each block of data in the file. In these cases, either a lineage code on each block of data or a quality overlay will be required. Original source is provided under "References" for each file.
2.6.5 The Source Graphic Lineage Report will be included in the Data Quality Report described in section 4.2 and the Data Element Dictionary described in section 5. 4 DIGITAL OUTPUT FORMAT STANDARDS These Standards cover the file formats in which data should be delivered. It will also cover the minimum detail which should appear on spatial output graphics.
4.2 Data Quality Report
4.2.1 The Data Quality Report will contain all of the information identified in the Source Graphic Lineage Report described in section 2.6.
4.2.2 The Data Quality Report must contain the following:
4.2.2.1 The mathematical transformations of coordinates used in each step from the source material to the final product. The specific parameters used to make the transformation must be described for each particular database. Reference to the software manufacturers' published information will be acceptable: For MILS contact John Dillon, MAS Data Base Administrator, Minerals Availability Field Office, P.O. Box 25407, Building 53, Denver Federal Center, Denver, CO 80225; for CRIB/MRDS contact Raymond E. Arndt, Chief MRDS Project, U.S. Geological Survey, 920 National Center, Reston, VA 22092; and for MLR contact Daniel W. Wickwire, U.S. Bureau of Land Management, P.O. Box 2965, Mail Stop 955.6, Portland, OR 97208.
4.2.2.2 A deductive estimate of the positional error of each category in the database: For MILS and CRIB/MRDS 0.25 to 1.0 miles and for MLR 0.125 to 0.25 miles.
4.2.2.3 A subjective estimate of error for the attribute portrayal: reference specific.
4.2.2.4 Administrative restrictions to the release or use of the data, e.g., sensitive archeological site data: None.
4.2.2.5 Title of contact person and phone number for further information concerning the database collection: Mark L. Ferns, Oregon Department of Geology and Mineral Industries, 1831 1st Street, Baker City, Oregon 97814, (503) 532-3133.