USGS - science for a changing world

USGS Geoscience Data Catalog

Additional USGS Geoscience data can be found by geographic location or by publication series.

Digital mining claim density map for Federal lands in Arizona: 1996

Metadata also available as - [Outline] - [Parseable text] - [DIF]

Frequently-anticipated questions:


What does this data set describe?

Title:
Digital mining claim density map for Federal lands in Arizona: 1996
Abstract:
The mining claim density data of federal lands in Arizona are combined with the digital Arizona Public Land Survey (PLS) to create a digital map of the density of mine claims in Open-File Report 99-406.
The mining claim density data of federal lands in Arizona was one of 13 western states released in Open-File Report 99-325. The database for Arizona was converted to an Arc/Info file and connected with the PLS by an Arc/Info relate.
As stated in OF 99-325, "These mining claim density databases were created from data obtained in March 1997, from the Mining Claim Recordation System (MCRS) of the Bureau of Land Management. These databases provide mining claim density information in a tabular form. They quantify the status of mining claim activity for 1996 and include information on mining claim activity since 1976. The databases contain information identifying 1) the general location of mining claims within the Public Land Survey System (PLS), 2) the number and type of claims (lode, placer, mill site, tunnel site), and 3) the status of the claims (open is held, closed is no longer held by a claimant)".
Combining the database with a digital PLS coverage of Arizona enables a User to spatially display the mine claim data as a digital map and compare it with other spatial themes.
Supplemental_Information: This data is in Arc/Info 7.1 format
  1. How should this data set be cited?

    Hyndman, Paul C. , and Campbell, Harry W. , 19990826, Digital mining claim density map for Federal lands in Arizona: 1996: U.S. Geological Survey Open-File Report 99-406.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -115
    East_Bounding_Coordinate: -109
    North_Bounding_Coordinate: 37
    South_Bounding_Coordinate: 31

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 1976
    Ending_Date: 1997
    Currentness_Reference:
    Release date of data by the Bureau of Land Management in March, 1997

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: map and database

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • Point (31283)
      • String (48304)
      • GT-polygon composed of chains (18066)

    2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -111.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000
      False_Northing: 0

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest .1
      Ordinates (y-coordinates) are specified to the nearest .1
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.4.
      The flattening of the ellipsoid used is 1/294.98.

  7. How does the data set describe geographic features?

    az_clms.clms
    Summary of values for number and type of mining claims in each section from OF99-325. The data is tied to an MTRS code which represents the Meridian + Township + Range + Section. This code provides a unique identifier for each Section of the PLS. (Source: The Bureau of Land Management is the official source for PLS designations and surveys and for the mining claim data.)

    MTRS
    A concatenation of Meridian, Township, Range, and Section of the PLS (Source: Bureau of Land Management)

    ValueDefinition
    MMTTT.TDRRR.RESS__MTRS is an 18-character field which is a concatenation of meridian (M), Township (T), township direction (D), range (R), range direction (E), and section (S). The form of the field is MMTTT.TDRRR.RESS__. The last two spaces were included in the beginning of the study but were not utilized.
    MM = the FIPS code for meridian. FIPS stands for the Federal Information Processing Standard. The codes for the meridians are:
    14 - Gila-Salt River 22 - Navajo
    TTT.T = BLM Township designation as 'TTT.T' may include a fraction of a Township. For example, Township 1 would be '__1.0'. Township 27.5 would be '_27.2'. The '.2' is a 1/2 township.
    D = BLM Township direction may be North (N) or South (S).
    RRR.R = BLM Range designation as 'RRR.R' which may include a fraction of a Range See Township (T) for example.
    E = BLM Range direction may be East (E) or West (W).
    SS = BLM Section number. For example, section 1 is '_1' and section 35 is '35'. Generally the highest section number is 36, but there are exceptions in several States.

    NOLC
    Number of Open (or recorded) Lode Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:67

    NOPC
    Number of Open (or recorded) Placer Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:38

    NOMC
    Number of Open (or recorded) Mill site Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:117

    NOTC
    Number of Open (or recorded) Tunnel site Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:1

    TOC
    Total number of Open (or recorded) Claims of all types within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:129

    NCLC
    Number of Closed (or terminated and closed) Lode Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:172

    NCPC
    Number of Closed (or terminated and closed) Placer Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:104

    NCMC
    Number of Closed (or terminated and closed) Mill site Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:144

    NCTC
    Number of Closed (or terminated and closed) Tunnel site Claims within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:12

    TCC
    Total number of Closed (or terminated and closed) Claims of all types within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:0
    Maximum:235

    TC
    Total number of all Claims of all types within a section (Source: Hyndman and Campbell, 1999)

    Range of values
    Minimum:1
    Maximum:254

    az_clms.pat
    Summary of values for number and type of mining claims in each section from OF99-325. The data is tied to an MTRS code which represents the Meridian + Township + Range + Section. This code provides a unique identifier for each Section of the PLS. (Source: The Bureau of Land Management is the official source for PLS designations and surveys and for the mining claim data. The coverage, az_clms,)

    TOWNSHIP
    The first three digits are the Township number and the last digit is the direction. 1=North; 2=East; 3=South; 4=West (Source: None)

    RANGE
    The first three digits are the Range number and the last digit is the direction. 1=North; 2=East; 3=South; 4=West (Source: None)

    SECTION
    Section number (Source: None)

    MTRS
    A concatenation of Meridian, Township, Range, and Section of the PLS (Source: Bureau of Land Management)

    ValueDefinition
    MMTTT.TDRRR.RESS__MTRS is an 18-character field which is a concatenation of meridian (M), Township (T), township direction (D), range (R), range direction (E), and section (S). The form of the field is MMTTT.TDRRR.RESS__. The last two spaces were included in the beginning of the study but were not utilized.
    MM = the FIPS code for meridian. FIPS stands for the Federal Information Processing Standard. The codes for the meridians are:
    14 - Gila-Salt River 22 - Navajo
    TTT.T = BLM Township designation as 'TTT.T' may include a fraction of a Township. For example, Township 1 would be '__1.0'. Township 27.5 would be '_27.2'. The '.2' is a 1/2 township.
    D = BLM Township direction may be North (N) or South (S).
    RRR.R = BLM Range designation as 'RRR.R' which may include a fraction of a Range See Township (T) for example.
    E = BLM Range direction may be East (E) or West (W).
    SS = BLM Section number. For example, section 1 is '_1' and section 35 is '35'. Generally the highest section number is 36, but there are exceptions in several States.

  8. What are the components of this data set?

    az_clms.e00 (Arc/Info export file)
    This Arc/Info export file contains the coverage az_clms, the database az_clms.clms, and the relate az_clms.rel. This digital map contains only those parts of the Arizona PLS which contain mine claim density data. The original PLS of Arizona was acquired from the U.S. Bureau of Mines when it was closed by Congress in 1996. The Bureau of Mines purchased the PLS of Arizona from a private company. The data is proprietary and cannot be released in its complete form.
    az_clms.clms (Arc/Info database)
    This database contains mine claim density information for federal lands in the state, from 1976 through 1996. It is one of several state databases from OF 99-325.
    az_clms.rel (Arc/Info relate)
    This file contains the parameters needed to relate the database, az_clms.clms to the digital map database, az_clms.pat. The structure of the relate is:
      RELATION                   = AZ_CLMS
      TABLE-ID                   = az_clms.clms
      DATABASE                   = info
      ITEM                       = MTRS
      COLUMN                     = mtrs
      TYPE                       = ORDERED
      ACCESS                     = RO
    


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Cheryl Laudenbach, Denver Service Center, BLM, provided the original mining claim data from the Mining Claim Recordation Database. The data was used to create the mining claim density databases in OF 99-325.

  3. To whom should users address questions about the data?

    Pamela D Derkey
    U.S. Geological Survey, GEO-WRG-MRS
    W 904 Riverside Avenue
    Spokane, WA 99201
    USA

    509-368-3114 (voice)
    509-368-3199 (FAX)
    pderkey@usgs.gov


Why was the data set created?

The digital map was developed to document mining claim activity on federal lands in Arizona and to investigate interrelationships of mining claim activity with physical and social science concerns.
This digital map is not to be considered as a legal representation of survey lines and corners or of mining claim boundaries.


How was the data set created?

  1. From what previous works were the data drawn?

    OF 99-325 (source 1 of 2)
    U.S. Geological Survey, 1999, Digital databases containing mining claim density information for Arizona, California, Colorado, Idaho, Montana, Nebraska, New Mexico, Nevada, Oregon, South Dakota, Utah, Washington, and Wyoming created from the BLM Mining Claim Recordation System: 1996: U.S. Geological Survey Open-File Report 99-325, U.S. Geological Survey, Denver, Colorado.

    Online Links:

    Other_Citation_Details:
    Original data from the Bureau of Land Management Mine Claim Recordation Database (MCRD)
    Type_of_Source_Media: digital file
    Source_Contribution:
    This database contributed the mine claim density information needed to create a spatial mine claim density map.

    Arizona PLS (source 2 of 2)
    Arizona State Land Department, 1988, Public Land Survey System for Arizona.

    Other_Citation_Details:
    Arizona Land Resources Information System. 1616 W. Adams, Phoenix, AZ, 85007. Contact by phone at (602) 542-4709, or by email at gisdata@lnd.state.az.us. The digital PLS is considered copyrighted and will not be released in a form that would enable someone to reconstruct the PLS. Portions can be released in paper or digital form.
    Type_of_Source_Media: digital file
    Source_Contribution: ALRIS provided the digital PLS of Arizona at a nominal cost.

  2. How were the data generated, processed, and modified?

    Date: 1997 (process 1 of 2)
    The mine claim density database of Arizona was released as part of the U.S. Geological Open-File Report, OF 99-325. It was imported as an Arc/Info table, az_clms.clms, using the command, dbaseinfo. A relate, az_clms.rel, was made to connect the database to the PLS of Arizona. This report can be found at URL: <http://geopubs.wr.usgs.gov/open-file/>

    Data sources used in this process:

    • OF 99-325

    Date: 1997 (process 2 of 2)
    A field, mtrs, was added to the Arizona PLS to which the mine claim density database could be attached. The polygon attribute table, .pat, was converted to a dBase file. The mtrs field was created and populated and the table was converted back to a .pat table. The original .pat was replaced with the new .pat. The data was attached through the use of a relate, az_clms.rel, and a subset of the Arizona PLS which contained only mine claim density data was created. An example of commands for using the relate in ArcEdit for selecting all claims in the Total Claims (tc) field is:
    restore relate az_clms.rel
    editcover az_clms
    sel az_clms//tc
    

    Data sources used in this process:

    • Arizona PLS

  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    OF 99-325 reports that the attributes of the mining claim data from BLM data, claims per section, do not represent the exact number of claims in each section. Some claims overlap into adjoining sections and/or townships. In order to count each claim only once, it was necessary to choose one section for each claim to be identified with. Therefore, the first section listed in the BLM database for a particular claim was chosen as the section the claim was counted in.
    The accuracy was tested by summing each category of claim in the mining claim database and comparing the sum to those from the original BLM database. The sums for each category matched.
    No attempt was made to determine the accuracy of BLM's database.

  2. How accurate are the geographic locations?

    A claim may be within a section or it may straddle two, three, or four sections. In order to count each claim only once, it was necessary to choose one section for each claim to be identified with. Therefore, the first section listed in the BLM database for a particular claim was chosen as the section the claim was counted in.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    None of the data from BLM was omitted. The data is considered complete for the purpose of determining mining claim density in this State.
    The digital PLS of Arizona is assumed to be complete although it does not cover the entire state.

  5. How consistent are the relationships among the observations, including topology?

    The data set is a derived subset of the original BLM data. No modifications to the BLM data were made.
    The PLS in this report is a derived subset of the original PLS. Only those sections containing mine claim density data are included in this report.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
Users should contact the BLM for current data. The U.S. Geological Survey makes no warranties related to the accuracy of the data and users are required to determine suitability of use for any particular purpose. This digital map is not meant to be construed as a legal representation of mining claim boundaries. The PLS digital map is from the Arizona State Land Department, Arizona Land Resources Information System. Users should contact them for a current digital pls map and metadata. The map should not be used at scales larger than 1:100,000.
The user must obtain current information on mining claims from the Arizona State Office of the Bureau of Land Management for the area of interest since the mining claim density data is not current. The information in the database does not provide the legal location or status of individual mining claims.
Any hardcopies utilizing this data set shall clearly indicate their source. If the user has modified the data in any way they are obligated to describe the types of modifications they have performed on the hardcopy map. User specifically agrees not to misrepresent this data set, nor to imply that changes they made were approved by the U.S. Geological Survey.

  1. Who distributes the data set? (Distributor 1 of 3)

    Pamela D Derkey
    U.S. Geological Survey, GEO-WRG-MRS
    W 904 Riverside Avenue
    Spokane, WA 99201
    USA

    509-368-3114 (voice)
    509-368-3199 (FAX)
    pderkey@usgs.gov

  2. What's the catalog number I need to order this data set?

    Open-File Report 99-406

  3. What legal disclaimers am I supposed to read?

    The U.S. Geological Survey (USGS) provides this data "as is." The USGS makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although this data has been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of this data on any other system, nor does the fact of distribution constitute or imply any such warranty.
    In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by the USGS.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    The user should have GIS software capable of reading Arc/Info files


  1. Who distributes the data set? (Distributor 2 of 3)

    U.S. Geological Survey Information Services
    Open-File Reports
    Box 2586
    Denver, CO 80225
    USA

    1-303-202-4200 (voice)
    1-303-202-4693 (FAX)

  2. What's the catalog number I need to order this data set?

    USGS Open-File Report 99-406

  3. What legal disclaimers am I supposed to read?

    The U.S. Geological Survey (USGS) provides this data "as is." The USGS makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although this data has been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of this data on any other system, nor does the fact of distribution constitute or imply any such warranty.
    In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by the USGS.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    The user should have software GIS software capable of reading Arc/Info files.


  1. Who distributes the data set? (Distributor 3 of 3)

    U.S.G.S. Earth Science Information Office
    904 West Riverside Avenue, Rm 135
    Spokane, WA 99201
    USA

    509-368-3130 (voice)
    509-353-2872 (FAX)
    esnfic@mailmcan1.wr.usgs.gov

    Hours_of_Service: 8:00 a.m. - 4:30 p.m. Pacific time zone
  2. What's the catalog number I need to order this data set?

    Open-File Report 99-406

  3. What legal disclaimers am I supposed to read?

    The U.S. Geological Survey (USGS) provides this data "as is." The USGS makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although this data has been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of this data on any other system, nor does the fact of distribution constitute or imply any such warranty.
    In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by the USGS.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    The user should have software GIS software capable of reading Arc/Info files.


Who wrote the metadata?

Dates:
Last modified: 25-Feb-1999
Last Reviewed: 15-Dec-1999
Metadata author:
Pamela D Derkey
U.S. Geological Survey, GEO-WRG-MRS
W 904 Riverside Avenue
Spokane, WA 99201
USA

509-368-3114 (voice)
509-368-3199 (FAX)
pderkey@usgs.gov

Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


This page is <http://geo-nsdi.er.usgs.gov/metadata/open-file/99-406/metadata.faq.html>
How other people discovered this page

Accessibility FOIA Privacy Policies and Notices

Take Pride in America logo USA.gov logo U.S. Department of the Interior | U.S. Geological Survey
URL: http://geo-nsdi.er.usgs.gov/metadata/open-file/99-406/metadata.faq.html
Page Contact Information: Peter Schweitzer
Page Last Modified: Monday, 10-Nov-2008 12:20:10 EST

Generated by mp version 2.9.8 on Mon Nov 10 12:20:10 2008