Mineral Resources On-Line Spatial Data
Mineral Resources > Online Spatial Data
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.
The most recent deposit name. Textual values of no more than 36 characters.
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.
Alternative names that have been used for the deposit. Textual values of no more than 154 characters.
Name of the country where the deposit occurs. Textual values of no more than 18 characters.
Coded abbreviation combining the country and state or province. Textual values of no more than 4 characters.
State or province, if known, where the deposit occurs. Textual values of no more than 40 characters.
Geographic latitude in decimal degrees, datum WGS84. South is negative, north positive. Real numbers stored in double precision.
Geographic longitude in decimal degrees, datum WGS84. West is negative, east positive. Real numbers stored in double precision.
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.
Textual values of no more than 67 characters.
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.
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.
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.
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.
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.
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.
Real numbers stored in double precision.
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.
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.
Integer values. Int of width 8.
Degrees of latitude. Integer values. Int of width 3.
Minutes of latitude. Integer values. Int of width 2.
Seconds of latitude. Integer values. Int of width 2.
Degrees of lontitude. Integer values. Int of width 4.
Minutes of longitude. Integer values. Int of width 2.
Seconds of longitude. Integer values. Int of width 2.
Textual values of no more than 204 characters.
Textual values of no more than 184 characters.
Textual values of no more than 213 characters.
Date the deposit was discovered, where this is known. Textual values of no more than 35 characters.
Date mining of the deposit began, if this is know. Textual values of no more than 19 characters.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Supplementary information. Textual values of no more than 255 characters.
Numerical identifier for the deposit, matches a value in main:rec_id. Integer values. Int of width 4.
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.
Numerical identifier for the deposit, matches a value in main:rec_id. Integer values. Int of width 4.
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.