<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20251216</CreaDate>
<CreaTime>12082800</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Poly_SpatialJoin</itemName>
<nativeExtBox>
<westBL Sync="TRUE">-169.104104</westBL>
<eastBL Sync="TRUE">-78.422442</eastBL>
<southBL Sync="TRUE">31.420997</southBL>
<northBL Sync="TRUE">66.261619</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="TRUE">LocPtToLocPoly</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="TRUE">SiteToLocPoly</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
</relatedItems>
<imsContentType Sync="TRUE">002</imsContentType>
<itemSize Sync="TRUE">0.000</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Geographic</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Angular Unit: Degree (0.017453)</csUnits>
<peXml Sync="TRUE">&lt;GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'&gt;&lt;WKT&gt;GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433],AUTHORITY[&amp;quot;EPSG&amp;quot;,4326]]&lt;/WKT&gt;&lt;XOrigin&gt;-400&lt;/XOrigin&gt;&lt;YOrigin&gt;-400&lt;/YOrigin&gt;&lt;XYScale&gt;1111948722.2222221&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;8.983152841195215e-09&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;LeftLongitude&gt;-180&lt;/LeftLongitude&gt;&lt;WKID&gt;4326&lt;/WKID&gt;&lt;LatestWKID&gt;4326&lt;/LatestWKID&gt;&lt;/GeographicCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20251216</SyncDate>
<SyncTime>11172200</SyncTime>
<ModDate>20251216</ModDate>
<ModTime>11172200</ModTime>
<ArcGISProfile>FGDC</ArcGISProfile>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Carma A. San Juan</rpIndName>
<rpOrgName>U.S. Geological Survey, Rocky Mountain Region</rpOrgName>
<rpPosName>Physical Scientist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>303-236-2450</voiceNum>
<faxNum>303-236-3200</faxNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>PO Box 25046, Mail Stop 973</delPoint>
<city>Lakewood</city>
<adminArea>CO</adminArea>
<postCode>80225</postCode>
<country>US</country>
<eMailAdd>csanjuan@usgs.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt>20200824</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>USGS Information Services</rpIndName>
<rpOrgName>U.S. Geological Survey - ScienceBase</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>1-888-ASK-USGS (1-888-275-8747)</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>Building 810, Mail Stop 302</delPoint>
<city>Denver</city>
<adminArea>CO</adminArea>
<postCode>80225</postCode>
<country>United States of America</country>
<eMailAdd>sciencebase@usgs.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>None. No fees are applicable for obtaining the data set.</resFees>
</distorOrdPrc>
<distorFormat>
<formatName>Digital Data</formatName>
</distorFormat>
<distorTran>
<onLineSrc>
<linkage>https://doi.org/10.5066/P97NJLI4</linkage>
</onLineSrc>
</distorTran>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://doi.org/10.5066/P97NJLI4</linkage>
</onLineSrc>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Tungsten Deposits in the United States</resTitle>
<date>
<pubDate>2020-08-31</pubDate>
</date>
<resEd>2.0</resEd>
<citRespParty>
<rpOrgName>Karl, N.A.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Burger, M.H.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>USGS ScienceBase</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Denver, CO</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Reyes, T.A.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Long, K.R.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Schmeda, G.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Knudsen, L.D.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Carroll, T.R.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>Vector Digital Data Set</fgdcGeoform>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
<datasetSeries>
<seriesName>U.S. Geological Survey data release</seriesName>
<issId>DOI: 10.5066/P97NJLI4</issId>
</datasetSeries>
<otherCitDet>Suggested citation: Karl, N.A., Carroll, T.R., Burger, M.H., Knudsen, L.D., Long, K.R., Reyes, T.A., and Schmeda, G., 2020, Tungsten Deposits in the United States (ver. 2.0, August 2020): U.S. Geological Survey data release, https://doi.org/10.5066/P97NJLI4. Karl, N.A., ORCID 0000-0003-2858-2498; Carroll, T.R., ORCID 0000-0002-0671-2848; Burger, M.H., ORCID 0000-0002-6254-4375; Knudsen, L.D., ORCID 0000-0003-3691-5475; Long, K.R., ORCID 0000-0002-6457-2820; Reyes, T.A., ORCID 0000-0002-0504-2571; Schmeda, G., ORCID 0000-0003-2676-1118</otherCitDet>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;This attribute table contains location polygon data for the database: Karl, N.A., Carroll, T.R., Burger, M.H., Knudsen, L.D., Long, K.R., Reyes, T.A., and Schmeda, G., 2020, Tungsten Deposits in the United States (ver. 2.0, August 2020): U.S. Geological Survey data release, &lt;/SPAN&gt;&lt;A href="https://doi.org/10.5066/P97NJLI4"&gt;&lt;SPAN&gt;https://doi.org/10.5066/P97NJLI4&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>This dataset was developed as part of an ongoing effort by the U.S. Geological Survey to inventory public information on critical mineral deposits within the United States that have record of production and (or) resources above a specified cutoff limit. In the case of tungsten, the cutoff was set at 215 metric tons of tungsten metal. This represents, approximately the largest 10 percent of known U.S. deposits. These geospatial data provide location, geologic description, and production and resource information. In general, USGS uses this information to delineate permissive tracts (geographic areas in which specific types of mineral deposits may occur), develop assessments of potential undiscovered mineral resources, determine where and how the environmental effects of mining may be observed, and understand the natural variability found in mineral deposits of particular types. These data also support the Federal strategic objective to secure reliable supplies of critical minerals by providing information for geoscience research and mineral exploration to State and Federal agencies, private industry, and the general public.</idPurp>
<idCredit>The data sets were developed by the U.S. Geological Survey Geology, Geophysics, and Geochemistry Science Center (GGGSC) with support from the Bureau of Land Management Solid Minerals Program. Database reviews and contributions were made by USGS personnel Stu Giles, David John, Jeff Mauk and Kim Shedd.</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Jeffrey L. Mauk</rpIndName>
<rpOrgName>U.S. Geological Survey, Rocky Mountain Region</rpOrgName>
<rpPosName>Research Geologist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>303-236-5605</voiceNum>
<faxNum>303-236-3200</faxNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>PO Box 25046, Mail Stop 973</delPoint>
<city>Lakewood</city>
<adminArea>CO</adminArea>
<postCode>80225</postCode>
<country>US</country>
<eMailAdd>jmauk@usgs.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="011"/>
</maintFreq>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>Geographic Names Information System (GNIS)</resTitle>
</thesaName>
<keyword>North Carolina</keyword>
<keyword>Nevada</keyword>
<keyword>Texas</keyword>
<keyword>New Mexico</keyword>
<keyword>Washington</keyword>
<keyword>Arizona</keyword>
<keyword>Colorado</keyword>
<keyword>Montana</keyword>
<keyword>California</keyword>
<keyword>Alaska</keyword>
<keyword>Idaho</keyword>
<keyword>Utah</keyword>
</placeKeys>
<placeKeys>
<thesaName>
<resTitle>Common geographic areas</resTitle>
</thesaName>
<keyword>United States</keyword>
</placeKeys>
<themeKeys>
<keyword>Sn skarn deposits</keyword>
<keyword>W veins</keyword>
<keyword>Sn greisen deposits</keyword>
<keyword>Arc-related porphyry Mo</keyword>
<keyword>deposit type</keyword>
<keyword>Au-W breccia</keyword>
<keyword>Brine</keyword>
<keyword>Porphyry Mo-Nb</keyword>
<keyword>Climax Mo deposits</keyword>
<keyword>Epithermal Mn</keyword>
<keyword>Polymetallic veins</keyword>
<keyword>Porphyry Cu</keyword>
<keyword>W skarn deposits</keyword>
<keyword>Alluvial placer Sn</keyword>
<keyword>Porphyry Mo-Cu</keyword>
<keyword>Disseminated pluton Au-Sb</keyword>
<keyword>Placer Au-W</keyword>
<keyword>Replacement in calcareous schists Au-Ag-Sb</keyword>
</themeKeys>
<themeKeys>
<keyword>Mining District</keyword>
<keyword>Open Pit Mine</keyword>
<keyword>Mineral Region</keyword>
<keyword>Placer Mine</keyword>
<keyword>Area</keyword>
<keyword>Mine Shaft</keyword>
<keyword>Adit</keyword>
<keyword>Mineral District</keyword>
<keyword>Brine Mine</keyword>
<keyword>Deposit</keyword>
<keyword>Mine Feature</keyword>
<keyword>Underground Workings</keyword>
<keyword>Mineral Occurrence</keyword>
</themeKeys>
<themeKeys>
<keyword>scheelite</keyword>
<keyword>platinum-group elements</keyword>
<keyword>hübnerite</keyword>
<keyword>fluorspar</keyword>
<keyword>rare-earth elements</keyword>
<keyword>ferberite</keyword>
</themeKeys>
<themeKeys>
<keyword>USGS Mineral Deposit Database (USMIN)</keyword>
<keyword>Mineral Resources Program (MRP)</keyword>
<keyword>critical mineral</keyword>
<keyword>Energy and Minerals Mission Area</keyword>
<keyword>Earth Mapping Resources Initiative (Earth MRI)</keyword>
<keyword>U.S. Geological Survey (USGS)</keyword>
<keyword>data release</keyword>
<keyword>Bureau of Land Management (BLM)</keyword>
<keyword>Department of the Interior (DOI)</keyword>
<keyword>Geology, Geophysics, and Geochemistry Science Center (GGGSC)</keyword>
<keyword>Region 7: Upper Colorado Basin</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>Alexandria Digital Library Feature Type Thesaurus</resTitle>
</thesaName>
<keyword>mine sites</keyword>
<keyword>mineral deposit areas</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Category</resTitle>
</thesaName>
<keyword>geoscientificInformation</keyword>
<keyword>location</keyword>
<keyword>economy</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>USGS Thesaurus</resTitle>
</thesaName>
<keyword>gold</keyword>
<keyword>copper</keyword>
<keyword>arsenic</keyword>
<keyword>lithium</keyword>
<keyword>sulfur</keyword>
<keyword>titanium</keyword>
<keyword>tungsten</keyword>
<keyword>geographic information systems</keyword>
<keyword>geospatial datasets</keyword>
<keyword>mineral resources</keyword>
<keyword>tin</keyword>
<keyword>metallic mineral resources</keyword>
<keyword>molybdenum</keyword>
<keyword>zinc</keyword>
<keyword>rhenium</keyword>
<keyword>vanadium</keyword>
<keyword>natural resource exploration</keyword>
<keyword>mineral deposits</keyword>
<keyword>iron</keyword>
<keyword>antimony</keyword>
<keyword>economic geology</keyword>
<keyword>silver</keyword>
<keyword>niobium</keyword>
<keyword>beryllium</keyword>
<keyword>lead</keyword>
</themeKeys>
<searchKeys>
<keyword>USGS Mineral Deposit Database (USMIN)</keyword>
<keyword>Mining District</keyword>
<keyword>Open Pit Mine</keyword>
<keyword>Sn skarn deposits</keyword>
<keyword>gold</keyword>
<keyword>copper</keyword>
<keyword>W veins</keyword>
<keyword>arsenic</keyword>
<keyword>Sn greisen deposits</keyword>
<keyword>lithium</keyword>
<keyword>mine sites</keyword>
<keyword>sulfur</keyword>
<keyword>North Carolina</keyword>
<keyword>Mineral Resources Program (MRP)</keyword>
<keyword>Nevada</keyword>
<keyword>scheelite</keyword>
<keyword>Mineral Region</keyword>
<keyword>Arc-related porphyry Mo</keyword>
<keyword>titanium</keyword>
<keyword>Texas</keyword>
<keyword>Placer Mine</keyword>
<keyword>tungsten</keyword>
<keyword>deposit type</keyword>
<keyword>geographic information systems</keyword>
<keyword>Au-W breccia</keyword>
<keyword>geospatial datasets</keyword>
<keyword>critical mineral</keyword>
<keyword>Brine</keyword>
<keyword>Area</keyword>
<keyword>Porphyry Mo-Nb</keyword>
<keyword>Energy and Minerals Mission Area</keyword>
<keyword>platinum-group elements</keyword>
<keyword>Climax Mo deposits</keyword>
<keyword>Epithermal Mn</keyword>
<keyword>Earth Mapping Resources Initiative (Earth MRI)</keyword>
<keyword>U.S. Geological Survey (USGS)</keyword>
<keyword>Mine Shaft</keyword>
<keyword>Polymetallic veins</keyword>
<keyword>United States</keyword>
<keyword>mineral resources</keyword>
<keyword>New Mexico</keyword>
<keyword>tin</keyword>
<keyword>Adit</keyword>
<keyword>data release</keyword>
<keyword>hübnerite</keyword>
<keyword>fluorspar</keyword>
<keyword>Porphyry Cu</keyword>
<keyword>Bureau of Land Management (BLM)</keyword>
<keyword>metallic mineral resources</keyword>
<keyword>Mineral District</keyword>
<keyword>Washington</keyword>
<keyword>Brine Mine</keyword>
<keyword>Deposit</keyword>
<keyword>Mine Feature</keyword>
<keyword>molybdenum</keyword>
<keyword>zinc</keyword>
<keyword>rhenium</keyword>
<keyword>W skarn deposits</keyword>
<keyword>Alluvial placer Sn</keyword>
<keyword>vanadium</keyword>
<keyword>mineral deposit areas</keyword>
<keyword>natural resource exploration</keyword>
<keyword>geoscientificInformation</keyword>
<keyword>Porphyry Mo-Cu</keyword>
<keyword>Disseminated pluton Au-Sb</keyword>
<keyword>Arizona</keyword>
<keyword>Underground Workings</keyword>
<keyword>Colorado</keyword>
<keyword>Montana</keyword>
<keyword>Placer Au-W</keyword>
<keyword>mineral deposits</keyword>
<keyword>Mineral Occurrence</keyword>
<keyword>Department of the Interior (DOI)</keyword>
<keyword>location</keyword>
<keyword>economy</keyword>
<keyword>rare-earth elements</keyword>
<keyword>Geology</keyword>
<keyword>Geophysics</keyword>
<keyword>and Geochemistry Science Center (GGGSC)</keyword>
<keyword>ferberite</keyword>
<keyword>iron</keyword>
<keyword>California</keyword>
<keyword>antimony</keyword>
<keyword>economic geology</keyword>
<keyword>Alaska</keyword>
<keyword>silver</keyword>
<keyword>niobium</keyword>
<keyword>beryllium</keyword>
<keyword>Idaho</keyword>
<keyword>lead</keyword>
<keyword>Utah</keyword>
<keyword>Replacement in calcareous schists Au-Ag-Sb</keyword>
<keyword>Region 7: Upper Colorado Basin</keyword>
</searchKeys>
<resConst>
<LegConsts>
<useLimit>Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty.</useLimit>
<othConsts>None. Please see 'Distribution Info' for details.</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although these data have been processed successfully on a computer system at the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and (or) contained herein.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc>Esri ArcGIS 10.7.1 (Build 11595) Service Pack N/A (Build N/A)</envirDesc>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>1933-01-01</tmBegin>
<tmEnd>2020-01-01</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-147.402</westBL>
<eastBL>-78.4712</eastBL>
<southBL>31.421</southBL>
<northBL>66.261</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<suppInfo>The Esri ArcGIS 10.7.1 geodatabase contains 1 point and 2 polygon feature classes, 8 attribute tables, and 15 relationship classes. Relationship classes link tables using the Ftr_ID or Site_ID fields. Feature classes are also provided as Esri shapefiles; attribute tables are provided as Excel and comma-separated values (CSV) files. The description of each database layer (feature class) and attribute table is provided below, followed by general information about concepts and terms used in the development of the database. Metadata is provided in extensible markup language (XML), hypertext markup language (HTML), and text-formatted (TXT) formats. DATABASE LAYERS AND TABLES The Loc_Pt feature class contains point locations of mineral regions, mineral occurrences (deposits), and mine features, and the attribute information describing the location, source report, scale of the map used to obtain the location, and if the location has a polygonal footprint in the Loc_Poly feature class. In the database, all features have point locations, except for surface workings. The Loc_Poly feature class contains footprints or polygons of areas, deposits, and mining districts. If a source report shows a location as a polygon, the polygon is digitized, and the approximate centroid of the polygon is added to the Loc_Pt layer. Attribute information about the location is provided in the Loc_Pt layer. Mines are represented as points in the database, even when footprints are presented in source reports. Where possible, the approximate extent of the mining operation area, determined from imagery, is presented in the surface workings (Loc_Poly_Sw) layer. The Loc_Poly_Sw feature class contains the approximate area of mining-related activity, or "surface workings" as shown on Esri imagery. These polygonal outlines have no corresponding point location in the database, nor do they have links to other tables. The attribute information for surface workings contains the date of the imagery and basic location information including state and county names. Surface workings must be at least 1,000 feet (ft) (300 meters[m]) in one dimension to be digitized, and multiple workings that are 500 ft (150 m) or less apart are combined into one outline. No attempt is made to distinguish between the types of surface workings (for example, roads, pits, leach pads, waste piles, etc.), even when presented in source reports. The Dep_Model table contains mineral deposit model and geoenvironmental model classifications for a deposit included in the database. The Descr_Sum table contains relevant descriptions found in source reports. These descriptions are attributed according to the type of description, such as Geology, History, Production, Resources, etc. Descriptions pertain to individual features or to larger sites. The authors do not paraphrase nor combine descriptions, and therefore, when a database feature is described in multiple reports, the feature will have multiple entries. The GeolMinOcc table contains information about the geology of mineral deposits and prospects. Every attempt was made to compile information as reported in the source report. For example, if one source report states the valuable material as "chalcopyrite and scheelite", and another reports "copper carbonates", the attribute field Value_Mat will contain all values. The value in the Ref_ID field is the primary source report for the record, for example, "Hotz and Willden (1964)". All information in the record comes from the primary source report unless an attribute field value contains a number in parentheses. This number denotes another source report whose Ref_ID is given in the Remarks field. Full citations for source reports are provided in the References table and adhere to USGS citation style. The History table contains information derived from publicly available sources regarding the status of a mineral region, mineral occurrence, or mine feature through time. Values in the Status field indicate a condition or phase for the time period stated in the Year_From and Year_To fields. This information may not reflect the current status of a feature. For example, if the attribute record shows the status of a mine is "Active" and the Year_From and Year_To dates are 1925 and 1956 respectively, the mine was active from 1925 to 1956; it is unknown if the mine is still active. The Last_Updt field shows the date that the record was last updated by the authors. The Production table contains published production data for mines. Production is listed by commodity and reported as shown in the source reports. Reported production values are totaled by the USGS authors for the time period defined by the Year_From and Year_To fields. If production is reported for a group of features, the Ftr_ID will show "-1111" and the production is assigned to the "site" or Site_ID that groups those mines on the Site table. The contained SI commodity amount (CntSIComAm) for the contained SI commodity (CntSICom) has been provided in one consistent unit (metric tons) for the user which is typically calculated by USGS authors. A value ending with "111" as a decimal trailer indicates the value was calculated by USGS authors. For example, if a grade is calculated by USGS authors to be 0.05 percent, the value recorded in the database will be 0.05111. Conversion factors used by USGS authors can be found on the USGS_Tungsten_ver2_Merged_Excel file under the Conversions tab. Decimal trailers are not reported in the Entity and Attribute section for ranges. Where a range in values are provided for attribute fields such as Mat_Amnt, Grade, Contained, etc., the average of the range is reported within the field and the range of values are noted within the Remarks field. For consistency, production values are converted to the SI units by the USGS authors. The References table contains the citation of the map or report(s) from which the point, polygon, or attribute information is obtained. The table also assigns a short reference (Ref_ID) that is used throughout the database. This table does not have a relationship class allowing the user to relate to other tables since Ref_IDs from tables such as the Production table may have multiple references. The Resources table contains reported resource data for mineral deposits. Data are compiled for the most recent mineral resource when available. Resource values were recorded as shown in source reports, including year reported, resource amount, units, and classification system(s). The definition of terms (for example, inferred, proven, probable, etc.) used in various resource classification systems may change through time. Resources extracted from older sources might not be compliant with current rules and guidelines in minerals industry standards such as NI 43-101 or the Joint Ore Reserves Committee Code (JORC Code). The way the resource is reported dictates the number of records for each deposit. For example, if data from a single deposit are reported for an inferred resource and a proven reserve, data from both classifications will be reported as separate records, unless it is stated that the proven reserve is inclusive of the inferred resource. If resource data are reported for a group of features rather than an individual deposit, the Ftr_ID will show "-1111" and the resource is assigned to the "site" or Site_ID that groups those deposits on the Site table. The CntSIComAm for the CntSICom has been provided in one consistent unit (metric tons) for the user which is typically calculated by USGS authors. A value ending with "111" as a decimal trailer indicates the value was calculated by USGS authors. For example, if a value in the Grade field is calculated by USGS authors to be 0.05 percent, then the value recorded in the database will be 0.05111. Conversion factors used by the USGS authors can be found on the USGS_Tungsten_ver2_Merged_Excel file under the Conversions tab. Decimal trailers are not reported in the Entity and Attribute section for ranges. Where a range in values is provided for attribute fields such as Mat_Amnt, Grade, Contained, etc., the average of the range is reported within the field and the range of values is noted within the Remarks field. For consistency, resource values are converted to the International System of Units (SI units) by the USGS authors. Inclusion of material in the database is for descriptive purposes only and does not imply endorsement by the U.S. Government. The Site table is used to identify related features, such as a deposit and the mine(s) operating on it, or a mine and its related deposits. Each site has a unique identification value in the Site_ID field. A Site_ID is also assigned to mineral regions, such as mining districts, which are represented as a single polygon or point feature in the database. The Site_ID is used in all tables except the References table and Loc_Poly_Sw feature class. The Site table also indicates where information about a site occurs within the database. For example, if the Resources field in the Site table contains the value "Yes", resource information is available in the Resources table. GENERAL INFORMATION Mineral regions may be a mineralized area, a mineral district, or a mining district. Mineral areas have similar geology and deposit types. Mineral districts are usually named and are defined by a group of deposits of similar type, origin, and (or) commodity. Mining districts represent historic administrative areas organized by miners under the mining laws of the United States. Mining districts are typically an area containing a group of mines that exploited the same or related commodity. Mining district polygons may overlap. Mine features are man-made features associated with the process of extracting, processing, or concentrating ore materials. In this database, mine features have a point location, and where possible, the polygon boundary showing the extent of surface workings identified from imagery. No attempt is made to distinguish specific mine features like pits, dumps, tailings, etc. within the surface workings outline. Mineral occurrences, defined as a concentration of a mineral considered potentially valuable, can be deposits, prospects, or showings in USGS mineral deposit databases (USMIN). Mineral deposits have a defined size and may have a grade indicated by current and (or) past production, and (or) a resource estimate. The locations of mineral regions, mine features, and mineral occurrences are commonly represented as points in source maps and reports, and occasionally as footprints (polygon outlines). In this database, all features have a point location, and some have an additional polygonal footprint. Surface workings in the Loc_Poly_Sw feature class are the exception—they do not have a corresponding point location or attribute information in the Loc_Pt feature class. Otherwise, for points that have polygonal boundaries, the Loc_Pt feature class attribute field Loc_Poly contains the value "Yes" and the boundary definition is described in the field Poly_Def field. For example, "Approximate extent of the mining district from the map", or "Outline of scheelite-bearing tactite on map". Each point and polygon feature is uniquely identified by a Ftr_ID. The Site_ID is used to indicate groups of related features, or "sites". Tables are linked (related) using the Ftr_ID or the Site_ID fields. Some tables have more than one record describing a feature. For example, a point denoting a mine location may have many records in the Production table summarizing the dates and amounts of material produced. The database is designed to allow the user to navigate from the point or polygon layers to the linked table information or from the tables to the point and polygon layers. All data are derived from publicly available sources. The Last_Updt field shows the date that the record was last updated by the USGS authors. Full citations are listed in the References table, and each citation is assigned a short citation (Ref_ID) that is used for identification in the database. Except for the Loc_Poly feature class, the primary reference(s) is noted in the Ref_ID field. Additional references are enumerated after attribute field values, and the corresponding short reference is in the Remarks field. For example, the Commodity field shows "copper; gold (1); silver (1); tungsten". This indicates the commodities "copper and tungsten" are derived from the primary reference denoted in the Ref_ID field as "Pattee (1960)" and "gold and silver" is derived from a secondary reference denoted in the Remarks field as "(1) Geach (1972)". In the GeolMinOcc table, lists in different fields may not correspond. For example, if the Commodity field shows "copper; tungsten", the Value_Mat field may list the associated ore minerals in a different order. The data in lists are alphabetized to prevent duplication of values as authors compile the dataset, with individual values separated by semicolons. Listed fields are present in the Site, Loc_Pt, and GeolMinOcc tables. Field or attribute records that contain "Null" values in the file geodatabase were checked for available data and no data were found. In some cases, an entire field may contain no information. These "Null" fields are maintained in the database structure for consistency with related USGS products and for possible future use if information becomes available. Additionally, values in the fields Commodity, and Material may be lumped into groups such as platinum-group elements (PGE). For the purpose of the USMIN database, the PGE group includes the commodities iridium (Ir), osmium (Os), palladium (Pd), platinum (Pt), rhodium (Rh), ruthenium (Ru). Two points may occupy the same location. This occurs when there is a deposit with a mine, and the location of either the mine or the deposit is unknown. For example, a report provides a map showing the location of a deposit. The report also provides production data for underground "Mine X" that is associated with the deposit but does not provide the location of "Mine X". In this case, a second point representing "Mine X" is placed at the point location of the deposit. Polygon features may overlap. Viewing polygons as outlines without color fills will show where polygon overlap occurs. In the attribute section of this metadata, attribute fields from all feature classes and tables are listed in alphabetic order; corresponding feature classes and tables are listed in parentheses after the field name in the Attribute Label. For example, "Mat_Amnt (Production, Resources)" indicates the attribute field Mat_Amnt occurs in the Production table and in the Resources table.</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-169.104104</westBL>
<eastBL Sync="TRUE">-78.422442</eastBL>
<northBL Sync="TRUE">66.261619</northBL>
<southBL Sync="TRUE">31.420997</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="013"/>
</tpCat>
<tpCat>
<TopicCatCd value="005"/>
</tpCat>
</dataIdInfo>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>The locations of mineral regions, mine features, and mineral occurrences (deposits) are represented as points, and some of these point locations have corresponding "footprints" or polygonal outlines. The polygonal footprint may represent the approximate outline of a mineral occurrence or mineral region. The exceptions are areas disturbed by mining-related activity, or surface workings, which are derived from imagery rather than published reports. Surface working outlines have no corresponding point location, nor do they have links to other tables. Polygonal outlines, except for surface workings, may overlap. Overlapping surface workings are merged into a single outline. Surface workings do not distinguish different types of mine features, such as pits, tailings piles, dumps, etc. Two points may occupy the same location. This occurs when there is a deposit with a mine, and the central location of either the mine or the deposit is unknown. For example, a report provides a map showing the location of a deposit. The report also provides production data for underground "Mine X" that is mining the deposit but does not provide the location of "Mine X". In this case, a second point representing "Mine X" is placed at the point location of the deposit.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Mineral region, mine feature, and mineral occurrence geospatial and attribute data are compiled for the United States. Data are limited to publicly available sources for the time period between 1933 and 2020. Common literature sources include government and private industry annual reports, NI 43-101 reports, journal articles, company websites, and USGS publications. To more completely populate the Production and Resources tables, select values are calculated by USGS authors and are indicated by "111" as a decimal trailer.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>Unique values in attribute fields were checked through frequency analyses. The unique values in each attribute field were reviewed and checked for spelling, consistency of terms, accuracy, adherence to established vocabularies, and completeness. Values calculated by USGS authors were reviewed and verified. Further information regarding calculations can be obtained from USGS authors. Floating-point numerical values may be reported to 8 decimal places. Default setting in the ArcGIS geodatabase which typically show 6 decimal places, may be formatted to show the full numerical value. When converting from an ArcGIS file geodatabase attribute table to Excel, precision of numeric values may change. The values from the ArcGIS file geodatabase are accurate and should be used for any calculations or analyses.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Locations of features are compiled from published coordinates and by digitizing from georeferenced raster images of maps or imagery. The locational accuracy of features is dependent on the accuracy of the source maps, which generally ranged in map scale from 1:10,000 to 1:1,000,000. The scale of the source maps is recorded as "Large" for 1:24,000 scale or larger, "Medium" for maps scales between 1:24,000 and 250,000; and "Small" for scales smaller than 1:250,000, in the Loc_Scale field.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>Vertical accuracy in the data set is not applicable.</measDesc>
</report>
<dataLineage>
<dataSource>
<srcDesc>Reference used by the authors to develop standardized vocabularies for the database and attribute tables. The use of this reference is denoted as Schanz (1980) in this metadata.</srcDesc>
<srcMedName>
<MedNameCd value="018"/>
</srcMedName>
<srcCitatn>
<resTitle>The United Nations’ endeavor to standardize mineral resource classification</resTitle>
<resAltTitle>Schanz (1980)</resAltTitle>
<date>
<pubDate>1980-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>John J. Schanz, Jr.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>publication</fgdcGeoform>
</presForm>
<otherCitDet>Schanz, J.J., Jr., 1980, The United Nations’ endeavor to standardize mineral resource classification: National Resources Forum 4, p. 307-313, https://doi.org/10.1111/j.1477-8947.1980.tb00989.x.</otherCitDet>
<citOnlineRes>
<linkage>https://doi.org/10.1111/j.1477-8947.1980.tb00989.x</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1980-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Reference used by the authors to develop standardized vocabularies for the database and attribute tables. The use of this reference is denoted as American Esri (2020) in these metadata.</srcDesc>
<srcMedName>
<MedNameCd value="018"/>
</srcMedName>
<srcCitatn>
<resTitle>GIS dictionary</resTitle>
<resAltTitle>Esri (2020)</resAltTitle>
<date>
<pubDate>2020-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Esri</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>publication</fgdcGeoform>
</presForm>
<otherCitDet>Esri, 2020, GIS dictionary: Esri web page, accessed May 4, 2020, at https://support.esri.com/en/other-resources/gis-dictionary.</otherCitDet>
<citOnlineRes>
<linkage>https://support.esri.com/en/other-resources/gis-dictionary</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2020-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Reference used by the authors to develop standardized vocabularies for the database and attribute tables. The use of this reference is denoted as American Neuendorf and others (2011) in these metadata.</srcDesc>
<srcMedName>
<MedNameCd value="018"/>
</srcMedName>
<srcCitatn>
<resTitle>Glossary of geology</resTitle>
<resAltTitle>Neuendorf and others (2011)</resAltTitle>
<date>
<pubDate>2011-01-01</pubDate>
</date>
<resEd>5</resEd>
<citRespParty>
<rpOrgName>Julia A. Jackson</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Klaus K.E. Neuendorf</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>James P. Mehl, Jr.</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>American Geosciences Institute</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Alexandria, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>Publication (Book)</fgdcGeoform>
</presForm>
<otherCitDet>Neuendorf, K.K.E., Mehl, J.P., Jr., and Jackson, J.A., 2011, Glossary of geology (5th ed.): Alexandria, VA, American Geosciences Institute, 779 p.</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2011-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Reference used by the authors to develop standardized vocabularies for the database and attribute tables. The use of this reference is denoted as American Geosciences Institute (1997) in this metadata.</srcDesc>
<srcMedName>
<MedNameCd value="018"/>
</srcMedName>
<srcCitatn>
<resTitle>Dictionary of mining, mineral, and related terms</resTitle>
<resAltTitle>American Geosciences Institute (1997)</resAltTitle>
<date>
<pubDate>1997-01-01</pubDate>
</date>
<resEd>2</resEd>
<citRespParty>
<rpOrgName>American Geosciences Institute</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Alexandria, VA</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>American Geosciences Institute</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>Publication (Book)</fgdcGeoform>
</presForm>
<otherCitDet>American Geosciences Institute, 1997, Dictionary of mining, mineral, and related terms (2d ed.): Alexandria, VA, American Geosciences Institute, 646 p.</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1997-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Reference used by the authors to develop standardized vocabularies for the database and attribute tables. The use of this reference is denoted as Canadian Institute of Mining, Metallurgy and Petroleum (2014) in this metadata.</srcDesc>
<srcMedName>
<MedNameCd value="018"/>
</srcMedName>
<srcCitatn>
<resTitle>CIM definition standards for mineral resources &amp; mineral reserves</resTitle>
<resAltTitle>Canadian Institute of Mining, Metallurgy and Petroleum (2014)</resAltTitle>
<date>
<pubDate>2014-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Canadian Institute of Mining, Metallurgy and Petroleum</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Canadian Institute of Mining, Metallurgy and Petroleum</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>CIM Website</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>publication</fgdcGeoform>
</presForm>
<otherCitDet>Canadian Institute of Mining, Metallurgy and Petroleum, 2014, CIM definition standards for mineral resources &amp; mineral reserves: Canadian Institute of Mining, Metallurgy and Petroleum web page, accessed May 4, 2020, at https://mrmr.cim.org/media/1128/cim-definition-standards_2014.pdf.</otherCitDet>
<citOnlineRes>
<linkage>https://mrmr.cim.org/media/1128/cim-definition-standards_2014.pdf</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2014-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>A literature search of publicly available mineral resource information was conducted for tungsten element deposits in the United States. Priority was given to identifying existing databases or compilations with high quality locations and data attributes that could be utilized directly in a geographic information system (GIS). The literature search identified sources of data on mines, mineral occurrences, mineral regions, and resource and production data. Relevant information was acquired, reviewed for quality and geospatial information, and digitally captured. Mines described in published reports were captured as point locations. Mining activity and production were recorded in the History and Production tables. Where possible, the approximate extent of the mining operation area was captured from imagery in the surface workings layer (see Loc_Poly_Sw). Surface workings were digitized if the ground disturbance was at least 1,000 feet (300 meters) in one dimension. The outlines of adjacent surface workings were merged if they were within 500 feet (150 meters) of one another. Mineral occurrences, defined as a concentration of a mineral considered potentially valuable, were compiled and attributed as deposits. Mineral deposits have a defined size and may have a grade indicated by current and (or) past production, and (or) a resource estimate. Mineral occurrences were represented as points and as polygons if the aerial extent or "footprint" of a deposit was available. Each polygon was attributed to describe the reported boundary type, such as the extent of the estimated resource, the grade limit or grade-thickness, or the limit of mineralization. The footprints of mineral deposits overlapped in some areas. Production and resource information is compiled as reported and consequently shows variable units. USGS authors made every attempt to provide material amount, grade, and contained commodity data. If two of the three values are reported, the missing value was calculated by the USGS authors. These values are denoted by "111" as a decimal trailer. For consistency, the three fields were converted to SI units by the USGS authors, and contained material is reported as metric tons for all commodities. Converted values are reported in fields denoted by "SI" in the field name. Where a range in values is provided for material amount, grade, etc., the average of the range is reported within the attribute field and the reported range is noted within the Remarks field. In some instances, the cut-off grade of the primary commodity determines the cut-off grade of coproducts. For example, at the Main Pipe of the Cave Peak site in Texas the reported cut-off grade is 0.06 percent Mo. The cut-off grade for all commodities is reported as "0.06 percent Mo". In some instances, the reported commodity is a compound. When this occurs, the commodity is converted to its elemental form and the converted amount is stated in SI units. For example, the commodity tungsten trioxide (WO3) is reported in the Material field. The USGS authors converted the reported quantity of WO3 to the elemental form W in SI units and populated the fields CntSIComAm and CntSIComUt accordingly. Mineral regions are attributed as areas, mineral districts, or mining districts. Areas are defined by similar geology and deposit types. Mineral districts are areas, usually designated by name, defined by a group of deposits of similar type, origin, and (or) commodity. Mining districts are historic administrative areas organized by miners under the mining laws of the United States. Mining districts are typically an area containing a group of mines that exploited the same or related commodity. Mineral region polygons may overlap. All data were spatially integrated using ArcGIS. All attribute data were compiled from publicly available sources published between 1933 and 2020. Standardized vocabularies were developed by USGS authors and include definitions from American Geosciences Institute (1997), Canadian Institute of Mining, Metallurgy and Petroleum (2014), Esri (2020), Neuendorf and others (2011), and Schanz (1980). Data were checked throughout the compilation process for accuracy of locations; and completeness, accuracy, and consistency of attributes.</stepDesc>
<stepDateTm>2018-01-01</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Version 2.0 Revised and reposted August 31, 2020 Version 2.0 of the database includes modifications to the format of several field values, changes to the data structure, the addition of new records, and correction of errors. These changes are described below. The format of the field Ftr_Name was expanded to include the site name. The new format is "Site name, Feature name", for example, "Boriana, Boriana deposit". The format of the field "Material" in the Resources and Production tables was expanded to include the material and the known chemical formula. For example, the material molybdenum disulfide is now presented as "molybdenum disulfide (MoS2)". The data structure was modified to place the MinReg_ID field before the Site_ID field in the Site table. The data structure was modified to include the field MinReg_ID in the Loc_Pt feature class. The data structure was modified to exclude the fields Rcvry_Amt, Rcvry_Unit, Prod_USD, RcvryAmtSI, RcvryUntSI from the Production table.</stepDesc>
<stepDateTm>2020-01-01</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Poly_SpatialJoin">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<eainfo>
<detailed Name="Poly_SpatialJoin">
<enttyp>
<enttypl>Attribute Fields</enttypl>
<enttypd>The attribute fields contain attribute information associated with features or records in the data set. Attribute fields occur in data layer(s) noted in parentheses.</enttypd>
<enttypds>USGS Authors</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Join_Count</attrlabl>
<attalias Sync="TRUE">Join_Count</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">TARGET_FID</attrlabl>
<attalias Sync="TRUE">TARGET_FID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MinReg_ID</attrlabl>
<attalias Sync="TRUE">MinReg_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Site_ID</attrlabl>
<attalias Sync="TRUE">Site_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ftr_ID</attrlabl>
<attalias Sync="TRUE">Ftr_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ftr_Name</attrlabl>
<attalias Sync="TRUE">Ftr_Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Other_Name</attrlabl>
<attalias Sync="TRUE">Other_Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Last_Updt</attrlabl>
<attalias Sync="TRUE">Last_Updt</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ftr_Group</attrlabl>
<attalias Sync="TRUE">Ftr_Group</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ftr_Type</attrlabl>
<attalias Sync="TRUE">Ftr_Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Commodity</attrlabl>
<attalias Sync="TRUE">Commodity</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Lat_WGS84</attrlabl>
<attalias Sync="TRUE">Lat_WGS84</attalias>
<attrtype Sync="TRUE">Single</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Long_WGS84</attrlabl>
<attalias Sync="TRUE">Long_WGS84</attalias>
<attrtype Sync="TRUE">Single</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Pt_Def</attrlabl>
<attalias Sync="TRUE">Pt_Def</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Poly_Def</attrlabl>
<attalias Sync="TRUE">Poly_Def</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">State</attrlabl>
<attalias Sync="TRUE">State</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">County</attrlabl>
<attalias Sync="TRUE">County</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Loc_Scale</attrlabl>
<attalias Sync="TRUE">Loc_Scale</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Loc_Date</attrlabl>
<attalias Sync="TRUE">Loc_Date</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ref_Detail</attrlabl>
<attalias Sync="TRUE">Ref_Detail</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Ref_ID</attrlabl>
<attalias Sync="TRUE">Ref_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">150</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Remarks</attrlabl>
<attalias Sync="TRUE">Remarks</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Loc_Poly</attrlabl>
<attalias Sync="TRUE">Loc_Poly</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ANSICODE</attrlabl>
<attalias Sync="TRUE">ANSICODE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AREAID</attrlabl>
<attalias Sync="TRUE">AREAID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">22</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FULLNAME</attrlabl>
<attalias Sync="TRUE">FULLNAME</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MTFCC</attrlabl>
<attalias Sync="TRUE">MTFCC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ALAND</attrlabl>
<attalias Sync="TRUE">ALAND</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AWATER</attrlabl>
<attalias Sync="TRUE">AWATER</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">INTPTLAT</attrlabl>
<attalias Sync="TRUE">INTPTLAT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">11</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">INTPTLON</attrlabl>
<attalias Sync="TRUE">INTPTLON</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">12</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Area</attrlabl>
<attalias Sync="TRUE">Shape_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
<overview>
<eaover>The entity and attribute information provide the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set.</eaover>
<eadetcit>The entity and attribute information are generated by the individual and (or) agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information.</eadetcit>
</overview>
</eainfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="4326"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.2(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Poly_SpatialJoin">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
