Porphyry copper deposits of the world

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

Frequently anticipated questions:


What does this data set describe?

Title: Porphyry copper deposits of the world
Abstract:
Information on porphyry copper deposits from around the world with grade and tonnage models, a general classification based on geologic setting, mineralogy, with data allowing locations of these deposits to be plotted using GIS.
  1. How might this data set be cited?
    Singer, Donald A., Berger, Vladimir I., and Moring, Barry C., 2008, Porphyry copper deposits of the world: Open-File Report 2008-1155, Geological Survey (U.S.), Menlo Park, California.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -160.666944
    East_Bounding_Coordinate: 178.178333
    North_Bounding_Coordinate: 67.866667
    South_Bounding_Coordinate: -48.075
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2008
    Currentness_Reference:
    publication date
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Entity point (690)
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.0001. Longitudes are given to the nearest 0.0001. Latitude and longitude values are specified in decimal degrees. The horizontal datum used is World Geodetic System 1984.
      The ellipsoid used is WGS 84.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.
  7. How does the data set describe geographic features?
    main
    General descriptive information about the deposit (Source: this dataset)
    rec_id
    Record ID.

    A distinct numerical identifier for the database record without further scientific significance, assigned by the data manager of mrdata.usgs.gov. Integer values. Int of width 4. (Source: this dataset)
    Range of values
    Minimum:1
    Maximum:690
    Resolution:1
    depname
    Deposit name.

    The most recent deposit name. Textual values of no more than 36 characters. (Source: this dataset) Textual values of no more than 36 characters.
    includes
    Includes.

    The names of deposits that have been combined with the primary deposit as a result of the two-kilometer minimum separation rule. Textual values of no more than 58 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 614 records have no value for includes.
    altname
    Other names.

    Alternative names that have been used for the deposit. Textual values of no more than 154 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 525 records have no value for altname.
    country
    Country.

    Name of the country where the deposit occurs. Textual values of no more than 18 characters. (Source: this dataset) Textual values of no more than 18 characters.
    cntrycd
    Country code.

    Coded abbreviation combining the country and state or province. Textual values of no more than 4 characters. (Source: this dataset)
    Formal codeset
    Codeset Name:Country codes for USGS OFR-2008-1155
    Codeset Source:https://pubs.usgs.gov/of/2008/1155/data/country_codes.xls
    stprov
    State or province.

    State or province, if known, where the deposit occurs. Textual values of no more than 40 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 233 records have no value for stprov.
    latitude
    Latitude.

    Geographic latitude in decimal degrees, datum WGS84. South is negative, north positive. Real numbers stored in double precision. (Source: this dataset)
    Range of values
    Minimum:-48.075
    Maximum:67.8666666666667
    Units:decimal degrees
    longitude
    Longitude.

    Geographic longitude in decimal degrees, datum WGS84. West is negative, east positive. Real numbers stored in double precision. (Source: this dataset)
    Range of values
    Minimum:-160.666944444444
    Maximum:178.178333333333
    Units:decimal degrees
    agemy
    Age.

    Age of the deposit in millions of years before the present based on reported absolute (typically thermal dates) ages or midpoints of geologic time scale units. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 60 records have no value for agemy.
    Range of values
    Minimum:0
    Maximum:3234
    Units:million years
    depage
    Deposit age.

    Textual values of no more than 67 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 97 records have no value for depage.
    oreton
    Ore tonnage.

    Total tons of ore based on total production, reserves, and resources at the lowest possible cutoff grade, in millions of metric tons. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 267 records have no value for oreton.
    Range of values
    Minimum:0
    Maximum:21277
    Units:million metric tons
    cugrd
    Copper grade.

    Average grade of copper for the deposit, as percent of metal in ore. Zero value means the grade (always for byproducts) was unavailable. Real numbers stored in double precision. (Source: this dataset)
    Range of values
    Minimum:0
    Maximum:1.8
    Units:percent
    mogrd
    Molybdenum grade.

    Average grade of molybdenum for the deposit, as percent of metal in ore. Zero value means the grade (always for byproducts) was unavailable. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 1 records have no value for mogrd.
    Range of values
    Minimum:0
    Maximum:0.1
    Units:percent
    augrd
    Gold grade.

    Average grade of gold for the deposit, as grams per metric ton of ore. Zero value means the grade (always for byproducts) was unavailable. Real numbers stored in double precision. (Source: this dataset)
    Range of values
    Minimum:0
    Maximum:1.3
    Units:grams per metric ton
    aggrd
    Silver grade.

    Average grade of silver for the deposit, as grams per metric ton of ore. Zero value means the grade (always for byproducts) was unavailable. Real numbers stored in double precision. (Source: this dataset)
    Range of values
    Minimum:0
    Maximum:21
    Units:grams per metric ton
    deptype
    Type of deposit.

    Classification of the deposit using a system new to this report using the observed rocks reported in maps rather than characteristics that are frequently unobservable in yet-to-be discovered deposits. Textual values of no more than 3 characters. (Source: this dataset)
    Formal codeset
    Codeset Name:Cox and Singer (1986)
    Codeset Source:https://doi.org/10.3133/b1693
    empldepth
    Emplacement depth.

    Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for empldepth.
    Range of values
    Minimum:0
    Maximum:7.5
    Units:km
    dep5km10km
    Other deposits between 5km and 10km.

    Listing of other deposits by type that are between 5 and 10 km of the subject deposit. Each deposit type is coded as the deposit-type number and deposit type as listed in USGS Bulletins 1693 (Cox and Singer, 1986) and 2004 (Bliss, 1992). Textual values of no more than 37 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 460 records have no value for dep5km10km.
    dep5km
    Other deposits within 5km.

    Listing of other deposits by type that are within 5 km of the subject deposit. Each deposit type is coded as the deposit-type number and deposit type as listed in USGS Bulletins 1693 (Cox and Singer, 1986) and 2004 (Bliss, 1992). Textual values of no more than 59 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 352 records have no value for dep5km.
    dep_id
    Deposit ID.

    Integer values. Int of width 8. (Source: this dataset)
    Range of values
    Minimum:1
    Maximum:710
    Resolution:1
    latdeg
    Latitude degrees.

    Degrees of latitude. Integer values. Int of width 3. (Source: this dataset)
    Range of values
    Minimum:-48
    Maximum:67
    Units:degrees
    Resolution:1
    latmin
    Latitude minutes.

    Minutes of latitude. Integer values. Int of width 2. (Source: this dataset)
    Range of values
    Minimum:-59
    Maximum:59
    Units:minutes
    Resolution:1
    latsec
    Latitude seconds.

    Seconds of latitude. Integer values. Int of width 2. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 355 records have no value for latsec.
    Range of values
    Minimum:-58
    Maximum:59
    Units:seconds
    Resolution:1
    londeg
    Longitude degrees.

    Degrees of lontitude. Integer values. Int of width 4. (Source: this dataset)
    Range of values
    Minimum:-160
    Maximum:178
    Units:degrees
    Resolution:1
    lonmin
    Longitude minutes.

    Minutes of longitude. Integer values. Int of width 2. (Source: this dataset)
    Range of values
    Minimum:-59
    Maximum:59
    Units:minutes
    Resolution:1
    lonsec
    Longitude seconds.

    Seconds of longitude. Integer values. Int of width 2. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 365 records have no value for lonsec.
    Range of values
    Minimum:-59
    Maximum:59
    Units:seconds
    Resolution:1
    rockdep
    Rocks in deposit.

    Textual values of no more than 204 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 45 records have no value for rockdep.
    rockmap
    Rocks on map.

    Textual values of no more than 184 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 408 records have no value for rockmap.
    rockmapdep
    Rocks on map in deposit.

    Textual values of no more than 213 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 19 records have no value for rockmapdep.
    discdate
    Discovery date.

    Date the deposit was discovered, where this is known. Textual values of no more than 35 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 306 records have no value for discdate.
    startdate
    Startup date.

    Date mining of the deposit began, if this is know. Textual values of no more than 19 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 553 records have no value for startdate.
    ore_a
    Ore A-axis.

    Length in km of the major axis of the ellipse that best fits the shape of the ore body projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 17 records have no value for ore_a.
    Range of values
    Minimum:0
    Maximum:303
    Units:km
    ore_b
    Ore BA-axis.

    Length in km of the minor axis of the ellipse that best fits the shape of the ore body projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 11 records have no value for ore_b.
    Range of values
    Minimum:0
    Maximum:3
    Units:km
    ore_area
    Ore Area.

    Area in sq km of the ellipse that best fits the shape of the ore body projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 11 records have no value for ore_area.
    Range of values
    Minimum:0
    Maximum:28
    Units:sq km
    alter_a
    Alteration A-axis.

    Length in km of the major axis of the ellipse that best fits the shape of the alteration zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for alter_a.
    Range of values
    Minimum:0
    Maximum:25
    Units:km
    alter_b
    Alteration B-axis.

    Length in km of the minor axis of the ellipse that best fits the shape of the alteration zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for alter_b.
    Range of values
    Minimum:0
    Maximum:9
    Units:km
    alter_area
    Alteration area.

    Area in sq km of the ellipse that best fits the shape of the alteration zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for alter_area.
    Range of values
    Minimum:0
    Maximum:82
    Units:sq km
    sulf_a
    Sulfide A-axis.

    Length in km of the major axis of the ellipse that best fits the shape of the sulfide occurrence zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for sulf_a.
    Range of values
    Minimum:0
    Maximum:13
    Units:km
    sulf_b
    Sulfide B-axis.

    Length in km of the minor axis of the ellipse that best fits the shape of the sulfide occurrence zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for sulf_b.
    Range of values
    Minimum:0
    Maximum:7
    Units:km
    sulf_area
    Sulfide area.

    Area in sq km of the ellipse that best fits the shape of the sulfide occurrence zone projected in two dimensions to the surface. Real numbers stored in double precision. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 10 records have no value for sulf_area.
    Range of values
    Minimum:0
    Maximum:89
    Units:sq km
    comments
    Comments.

    Supplementary information. Textual values of no more than 255 characters. (Source: this dataset)
    ValueDefinition
    (no value)Information not available for this record. 203 records have no value for comments.
    minerals
    Mineralogy of the deposit as reported in scientific literature (Source: this dataset)
    rec_id
    Record ID.

    Numerical identifier for the deposit, matches a value in main:rec_id. Integer values. Int of width 4. (Source: this dataset)
    Range of values
    Minimum:1
    Maximum:690
    Resolution:1
    value
    Mineralogy.

    Name of minerals reported as present in the deposit, without regard for their abundance. Most rock-forming minerals, such as feldspar, calcite, and quartz, are not included. Some variants of rock forming minerals that may be related to mineralization or alteration, such as Ag calcite, are included. Textual values of no more than 44 characters. (Source: this dataset) Textual values of no more than 44 characters.
    ref
    Scientific literature consulted by the authors to characterize the deposit (Source: this dataset)
    rec_id
    Record ID.

    Numerical identifier for the deposit, matches a value in main:rec_id. Integer values. Int of width 4. (Source: this dataset)
    Range of values
    Minimum:1
    Maximum:690
    Resolution:1
    value
    References.

    Papers and web sites that were used to describe the deposit. In a few cases unpublished sources were used. Textual values of no more than 255 characters. (Source: this dataset) Textual values of no more than 255 characters.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Singer, Donald A.
    • Berger, Vladimir I.
    • Moring, Barry C.
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Donald A Singer
    U.S. Geological Survey
    345 Middlefield Road Mail Stop 901
    Menlo Park, CA
    USA

    650-329-5370 (voice)
    dsinger@usgs.gov

Why was the data set created?

Support regional to national scale mineral resource assessment

How was the data set created?

  1. From what previous works were the data drawn?
    USGS OFR-2002-268 (source 1 of 2)
    Singer, Donald A., Berger, Vladimir I., and Moring, Barry C., 2002, Porphyry copper deposits of the world: database, maps, and preliminary analysis: Open-File Report 2002-268, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details: DOI: 10.3133/ofr02268
    Type_of_Source_Media: Digital data
    Source_Contribution: This is a previous major version of the present database.
    USGS OFR-2005-1060 (source 2 of 2)
    Singer, Donald A., Berger, Vladimir Iosifovich, and Moring, Barry C., 2005, Porphyry copper deposits of the world: database, map, and grade and tonnage models: Open-File Report 2005-1060, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details: DOI: 10.3133/ofr20051060
    Type_of_Source_Media: Digital data
    Source_Contribution: This is a previous major version of the present database.
  2. How were the data generated, processed, and modified?
    Date: 2008 (process 1 of 2)
    This report is an update of earlier publications about porphyry copper deposits (Singer, Berger, and Moring, 2002; Singer, D.A., Berger, V.I., and Moring, B.C., 2005). The update was necessary because of new information about substantial increases in resources in some deposits and because we revised locations of some deposits so that they are consistent with images in GoogleEarth. In this report we have added new porphyry copper deposits and removed a few incorrectly classed deposits. In addition, some errors have been corrected and a number of deposits have had some information, such as grades, tonnages, locations, or ages revised. Colleagues have helped identify places where improvements were needed. Data sources used in this process:
    • USGS OFR-2002-268
    • USGS OFR-2005-1060
    Date: 12-Dec-2011 (process 2 of 2)
    Modified location given in record 260 (El Cobre, Cuba) to the inundated pit where mining occurred in the past. Thanks to Mr. Mario J. Faz, P.G., of Miami Florida for finding and alerting us to this problem.
  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?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This collection includes only well explored deposits for which there is sufficient information to contribute to constructing deposit models for this type of deposit and for distinguishing subtypes. This collection excludes, therefore, known occurrences that might be of this type, but for which important information is not available. With its focus on deposits, formally defined, this compilation excludes occurrences that cannot be expected to have economic potential.
  5. How consistent are the relationships among the observations, including topology?
    An important consideration at the data gathering stage is the question of what the sampling unit should be. Grade and tonnage data are available to varying degrees for districts, deposits, mines, and shafts. For the deposits in this file, the following rule was used to determine which ore bodies were combined. All mineralized rock or alteration within two (2) kilometers was combined into one deposit. Thus if the alteration zones of two deposits are within two kilometers of each other, they were combined. Such an operational spatial rule is necessary for defining deposits because we must be able to classify deposits in regions with highly variable geologic information and to avoid bias in estimating undiscovered deposits in resource assessments in areas where detailed information is lacking such as under cover. The two-kilometer rule was developed to try to insure that deposits in grade and tonnage and spatial density models correspond to deposits as geologic entities. Rules such as the two-kilometer rule applied here are essential in order to have an internally consistent assessment system where the estimate of number of undiscovered deposits is consistent with the grade and tonnage model. For example, El Pachon in Argentina and Los Pelambres in Chile are here reported as one record (deposit) because of the two-kilometer rule.

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: none
  1. Who distributes the data set? (Distributor 1 of 1)
    Peter N Schweitzer
    USGS Geology, Energy, and Minerals Science Center
    Geologist
    12201 Sunrise Valley Drive
    Reston, VA
    USA

    703-648-6533 (voice)
    703-648-6252 (FAX)
    pschweitzer@usgs.gov
  2. What's the catalog number I need to order this data set? USGS Open File Report 2008-1155
  3. What legal disclaimers am I supposed to read?
    This report is preliminary and has not been reviewed for conformity with U.S. Geological Survey editorial standards (or with the North American Stratigraphic Code). Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 12-Feb-2021
Metadata author:
Peter N Schweitzer
USGS Geology, Energy, and Minerals Science Center
Geologist
12201 Sunrise Valley Drive
Reston, VA
USA

703-648-6533 (voice)
703-648-6252 (FAX)
pschweitzer@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://mrdata.usgs.gov/metadata/ofr-2008-1155.faq.html>
Generated by mp version 2.9.50 on Fri Feb 12 10:13:26 2021