USGS Home
Contact USGS
Search USGS

Mineral Resources > Online Spatial Data

An index to PGE-Ni-Cr deposits and occurrences in selected mineral-occurrence databases

Frequently anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  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?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How should this data set be cited?

   Causey, J. Douglas, Galloway, John P., and Zientek, Michael L., 2009, An index to PGE-Ni-Cr deposits and occurrences in selected mineral-occurrence databases: Open File Report 2009-1045, U.S. Geological Survey, Menlo Park, California.

   Online Links:

   • <http://pubs.usgs.gov/of/2009/1045/>

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -172.755600

   East_Bounding_Coordinate: 178.850000

   North_Bounding_Coordinate: 83.080332

   South_Bounding_Coordinate: -53.147950

3. What does it look like?

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

   Calendar_Date: 2009

   Currentness_Reference: publication date

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

   Geospatial_Data_Presentation_Form: 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):

      • Entity point (17969)

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

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
      

7. How does the data set describe geographic features?

   main

   General descriptive information about the site

   site_id

   Site ID.

   Unique identifier for a site. Integer values. Int of width 10.

   Range of values
   Minimum:	7684
   Maximum:	12164329
   Resolution:	1

   name

   Site Name.

   Name of the site as used in the literature. Textual values of no more than 76 characters.

   Value	Definition
   (no value)	Information not available for this record. 933 records have no value for name.

   latitude

   Latitude.

   Geographic latitude of the site, WGS84. Real numbers stored in double precision.

   Range of values
   Minimum:	-53.14
   Maximum:	83.08
   Units:	decimal degrees

   longitude

   Longitude.

   Geographic longitude of the site, WGS84. Real numbers stored in double precision.

   Range of values
   Minimum:	-172.75
   Maximum:	178.85
   Units:	decimal degrees

   src_rec_no

   Source record.

   Record number in the source database. Textual values of no more than 15 characters.

   record_tp

   Description.

   Description of the site from the source database. Textual values of no more than 100 characters.

   Value	Definition
   (no value)	Information not available for this record. 2223 records have no value for record_tp.

   country

   Country.

   Country in which the site occurs. Textual values of no more than 43 characters.

   state

   State or Province.

   State or province in which the site occurs. Textual values of no more than 29 characters.

   Value	Definition
   (no value)	Information not available for this record. 6770 records have no value for state.

   ref_no

   Reference ID.

   Unique identifier for the bibliographic reference, a value in reference:ref_no. Integer values. Int of width 4.

   Range of values
   Minimum:	4
   Maximum:	70
   Resolution:	1

   class

   Classification.

   Generalized classification of the site based on the record_tp value. Textual values of no more than 32 characters.

   commodity

   Commodities found at the site

   site_id

   Site ID.

   Unique identifier for a site, a value in main:site_id. Integer values. Int of width 10.

   Range of values
   Minimum:	7684
   Maximum:	12164329
   Resolution:	1

   value

   Commodity.

   Commodity, an element symbol or material type. Textual values of no more than 36 characters.

   reference

   Bibliographic references for data sources

   ref_no

   Reference ID.

   Unique identifier for the bibliographic reference. Integer values. Int of width 4.

   Range of values
   Minimum:	4
   Maximum:	70
   Resolution:	1

   ref

   Reference.

   Bibliographic reference text, possibly including a URL. Textual values of no more than 768 characters.

   ref_short

   Citation.

   Short citation of the reference, suitable for in-text notes. Textual values of no more than 64 characters.

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Causey, J. Douglas
   • Galloway, John P.
   • Zientek, Michael L.

2. Who also contributed to the data set?

3. To whom should users address questions about the data?
   J. Douglas Causey
   U.S. Geological Survey
   Geologist
   904 W. Riverside Ave, Rm 202
   Spokane, WA 99201-1087
   USA
   

   509-368-3116 (voice)
   509-363-3199 (FAX)
   dcausey@usgs.gov
   

Why was the data set created?

The dataset was created to provide an index to other sources of information on mineral sites containing nickel, chromium and platinum group elements.

How was the data set created?

1. From what previous works were the data drawn?

   Causey and others (2009) (source 1 of 3)

   Causey, J. D., Galloway, J.P., and Zientek, M.L., 2009, An index to PGE-Ni-Cr deposits and occurrences in selected mineral-occurrence databases: Open File Report 2009-1045, U.S. Geological Survey, World Wide Web.

   Online Links:

   • <http://pubs.usgs.gov/of/2009/1045>

   Type_of_Source_Media: Access v. 2000 database

   Source_Scale_Denominator: 1000000

   Source_Contribution: Data used to make a point shapefile.

   Banerjee and others, 2001 (source 2 of 3)

   Banerjee, J., Gosh, S., and Mukherjee, A., 2001, Mineral atlas of India: None None, Geological Society of India, Hydesbad, India.

   Type_of_Source_Media: paper

   Source_Scale_Denominator: 2,000,000

   Source_Contribution:

   Data extracted to tabular form and used to make a point feature class and shapefile.

   Besaire, 1964 (source 3 of 3)

   Besaire, Henri, 1964, Madagascar, carte géologique: None None, Service géologique, Madagascar.

   Type_of_Source_Media: paper

   Source_Scale_Denominator: 1000000

   Source_Contribution:

   Data extracted to tabular form and used to make a point feature class and shapefile.

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

   Date: 2009 (process 1 of 1)

   Data from table in Access database added as a theme to ArcMap. The latitude and longitude fields used to make a XY Event theme. The event theme was then exported to a shapefile.

   Person who carried out this activity:
   

   J. Douglas Causey
   U.S. Geological Survey
   Geologist
   904 W. Riverside Ave, Rm 202
   Spokane, WA 99201-1087
   USA
   

   509-368-3116 (voice)
   509-363-3199 (FAX)
   dcausey@usgs.gov
   

   Data sources used in this process:

   • Causey and others (2009)

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?

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

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:

This spatial database is not meant to be used or displayed at any scale larger than 1:1,000,000 (for example, 1:100,000). Any hardcopies utilizing these datasets 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 these data sets, nor imply that changes they made were approved by the U.S. Geological Survey.

1. Who distributes the data set? (Distributor 1 of 1)
   U.S. Geological Survey Information Services
   P.O. Box 25046
   Denver, CO 80225-0046
   USA
   

   1-888-ASK-USGS (voice)
   infoservices@usgs.gov
   

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

   USGS Open-File Report 2009-1045

3. What legal disclaimers am I supposed to read?

   The U.S. Geological Survey (USGS) provides these geographic 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 these data have been processed successfully on computers of the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of these data on any other system, nor does the fact of distribution constitute or imply such warranty.

   In no event shall the USGS have 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.

   This spatial database is not meant to be used or displayed at any scale larger than 1:1,000,000 (for example, 1:100,000).

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	Site locations and characteristics with bibliographic reference in format Shapefile (version 1.0)
     Network links:

   • Cost to order the data: none

Who wrote the metadata?

Dates:

Last modified: 14-Jul-2010

Metadata author:

J. Douglas Causey
U.S. Geological Survey
Geologist
904 W. Riverside Ave., Rm 202
Spokane, WA 99201
USA

509-368-3116 (voice)
509-368-3199 (FAX)
dcausey@usgs.gov

Metadata standard:

Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)