Mica deposits of the Blue Ridge in North Carolina

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

Frequently anticipated questions:


What does this data set describe?

Title: Mica deposits of the Blue Ridge in North Carolina
Abstract: Point locations with characteristics of mines and prospects.
  1. How might this data set be cited?
    Lesure, Frank Gardner, 1968, Mica deposits of the Blue Ridge in North Carolina: Professional Paper 577, U.S. Geological Survey, Reston, Virginia.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -83.598930397999
    East_Bounding_Coordinate: -81.209519531999
    North_Bounding_Coordinate: 36.439323142
    South_Bounding_Coordinate: 35.0275958720001
  3. What does it look like?
    https://mrdata.usgs.gov/pp577/pp577-large.png (PNG)
    Mine and prospect locations with county boundaries, (768 x 512 pixels)
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 1968
    Currentness_Reference:
    Publication date of the original report
  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 (2181)
    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?
    datadxny
    Data dictionary, explaining tables and fields (Source: USGS)
    id
    Record ID.

    Row identifier within datadxny table. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:1
    Maximum:52
    Resolution:1
    tblorder
    Table order.

    Order in which this table should appear in some presentations. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:1
    Maximum:3
    Resolution:1
    tblname
    Table name.

    Name of the table. Textual values of no more than 20 characters. (Source: this data release)
    ValueDefinition
    pointsTable containing point locations and site names
    descriptionsTable containing descriptions of sites or deposits
    datadxnyThe data dictionary table describes tables and fields in the database
    number
    Ordinal position.

    Order in which this field occurs in the RDBMS. Integer values. Integer of width 4. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for number.
    Range of values
    Minimum:1
    Maximum:18
    Resolution:1
    label
    Field label.

    Label of the field in the RDBMS. Textual values of no more than 32 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for label.
    category
    Category.

    General category of information provided by the contents of the field. Textual values of no more than 50 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 2 records have no value for category.
    short_desc
    Short description.

    Descriptive name of the field used in some presentations, not constrained by rules affecting the label. Textual values of no more than 40 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 1 records have no value for short_desc.
    description
    Description.

    Longer description of the purpose and contents of the field. Textual values of no more than 4096 characters. (Source: this data release) Plain text not abbreviated
    link
    Link.

    URL providing more information about the field. Textual values of no more than 96 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 52 records have no value for link.
    origin
    Origin of field.

    Abbreviation of an organization, data set, or other entity responsible for defining the field. Textual values of no more than 12 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 52 records have no value for origin.
    sqltype
    SQL type.

    Data type of the field as used in the RDBMS. Textual values of no more than 8 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for sqltype.
    dbftype
    DBF field type.

    Data type of the field when expressed in DBF. Textual values of no more than 1 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for dbftype.
    width
    Field width.

    Field width when expressed in DBF. Integer values. Integer of width 4. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 3 records have no value for width.
    Range of values
    Minimum:1
    Maximum:4096
    Resolution:1
    prec
    Precision.

    Precision of the field (places to right of decimal) when expressed in DBF, only for numeric fields. Integer values. Integer of width 4. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 47 records have no value for prec.
    Range of values
    Minimum:0
    Maximum:8
    Resolution:1
    units
    Units of measure.

    Units of measure of the field values. Textual values of no more than 64 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 50 records have no value for units.
    points
    Point locations of mica occurrences from plates 2,3,4,5, and 6 of the report (Source: USGS)
    gid
    Row.

    Row identifier in the table. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:1
    Maximum:2181
    Resolution:1
    id
    Point ID.

    Point identifier. Textual values of no more than 8 characters. (Source: this data release) Unique identifer for each point in the form NCMPx-nnnn where x is the plate number and nnnn is the 3- or 4-digit location number on that plate.
    map_number
    Map ID.

    Numbered location on the map (plates). These are modified by adding the plate number multiplied by 1000 in order to combine data from multiple plates without introducing ambiguity. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:0
    Maximum:6399
    Resolution:1
    feature
    Feature type.

    Type of feature, mine, prospect, or unnamed prospect. Textual values of no more than 16 characters. (Source: this data release)
    ValueDefinition
    Unnamed ProspectSites shown on the plates (that is, maps) but not numbered or named
    MineSites named in the report as mines, presumably indicates production had occurred
    ProspectNamed sites indicated as prospects, presumably indicates production had not occurred
    DepositNamed sites indicated as deposits, production may have occurred
    name
    Name.

    Name of the site. Textual values of no more than 61 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 821 records have no value for name.
    Names, not abbreviated.
    other_name
    Alternative name.

    Alternative names by which the site is known. Textual values of no more than 61 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 1969 records have no value for other_name.
    Names, not abbreviated.
    state
    State.

    State in which the site is located. Textual values of no more than 16 characters. (Source: this data release)
    ValueDefinition
    North CarolinaUS state of North Carolina
    county
    County.

    County in which the site is located. Textual values of no more than 64 characters. (Source: this data release) Place names, not abbreviated
    map_area
    District.

    District name, one of the areas shown on plate 3. Textual values of no more than 50 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 2181 records have no value for map_area.
    Place names, not abbreviated
    commodity
    Commodity.

    Commodity name. Textual values of no more than 64 characters. (Source: this data release)
    ValueDefinition
    MicaAny of the sheet silicate minerals commonly referred to as mica, includes muscovite and biotite.
    source
    Source.

    Source of information. Textual values of no more than 63 characters. (Source: this data release) Reference to the source report
    notes
    Notes.

    Notes about the digitizing process. Textual values of no more than 100 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 2111 records have no value for notes.
    Descriptive text, not abbreviated
    point_x
    Longitude.

    Geographic longitude, WGS84. Real numbers stored in double precision. (Source: this data release)
    Range of values
    Minimum:-83.598930398
    Maximum:35.367724902
    Units:decimal degrees
    point_y
    Latitude.

    Geographic latitude, WGS84. Real numbers stored in double precision. (Source: this data release)
    Range of values
    Minimum:35.027595872
    Maximum:36.439323142
    Units:decimal degrees
    geom
    Geometry.

    Point geometry. Geometry(Point,4326) of width 64. (Source: this data release) Normally invisible, may be expressed as well-known binary texts.
    desc_id
    Description ID.

    Record in the descriptions table providing more detail for this point. Integer values. Integer of width 4. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 822 records have no value for desc_id.
    Range of values
    Minimum:1
    Maximum:1363
    Resolution:1
    descriptions
    Characteristics of the mineral occurrence, prospect, or mine from table 4 of the report (Source: USGS)
    id
    Row.

    Table row number. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:1
    Maximum:1363
    Resolution:1
    map_number
    Map ID.

    Location number on map, plus plate number multiplied by 1000 to make these values distinct. Integer values. Integer of width 4. (Source: this data release)
    Range of values
    Minimum:2001
    Maximum:6399
    Resolution:1
    name
    Name.

    Name of mine, prospect, or occurrence. Textual values of no more than 80 characters. (Source: this data release) Plain text names
    source
    Source.

    Source of information. Textual values of no more than 80 characters. (Source: this data release) List of abbreviated references, includes CMC = Colonial Mica Corporation; DMEA = Defense Minerals Exploration Administration; OME = Office of Minerals Exploration; USGS = U.S. Geological Survey; OF = USGS open-file reports and maps.
    work_period
    Periods worked.

    Years in which the site was actively worked. Textual values of no more than 80 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 46 records have no value for work_period.
    Lists of years or other time periods such as WWI = World War I; WWII = World War II.
    work_size
    Workings.

    Description of workings, with measurements given in feet. Textual values of no more than 200 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 27 records have no value for work_size.
    Descriptive text, not abbreviated.
    muscovite
    Muscovite.

    Description of the muscovite found at the site. Textual values of no more than 200 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 29 records have no value for muscovite.
    Descriptive text, not abbreviated. Descriptive terms are explained on page 17 of the report.
    production
    Production.

    Production at the site. Textual values of no more than 80 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 418 records have no value for production.
    Descriptive terms indicating material produced (sheet = mica; feldspar, clay, scrap), size (small = < 500 lb; moderate = 500 - 10,000 lb; large = > 10,000 lb) and time period (WWI = World War I; WWII = World War II; int = intermittent, or a year or range of years).
    shape
    Pegmatite shape.

    Shape of the pegmatite body containing muscovite. Textual values of no more than 40 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 265 records have no value for shape.
    Descriptive morphological terms, not abbreviated.
    size
    Pegmatite size.

    Size of the pegmatite body containing muscovite. Textual values of no more than 80 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 302 records have no value for size.
    Lists of dimensions, sometimes expressed as a range of values, using the following abbreviations to indicate the characteristic of the deposit whose dimensions were given: D = depth; L = length; T = thickness; avg = average. Numerical values in feet.
    strike
    Pegmatite strike.

    Orientation (strike) of the pegmatite. Textual values of no more than 20 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 184 records have no value for strike.
    Compass directions with verbal or numerical modifiers
    dip
    Pegmatite dip.

    Orientation (dip) of the pegmatite. Textual values of no more than 40 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 270 records have no value for dip.
    Compass directions with verbal or numerical modifiers
    plunge
    Pegmatite plunge.

    Orientation (plunge) of the pegmatite. Textual values of no more than 20 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 1176 records have no value for plunge.
    Compass directions
    rel_wallrock
    Relation to wall rock.

    Geometrical relationship of the pegmatite to the wall rock surrounding it. Textual values of no more than 40 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 340 records have no value for rel_wallrock.
    Plain text emphasizing concordance or discordance
    wallrock
    Wall rock.

    Description of the wall rock. Textual values of no more than 80 characters. (Source: this data release)
    ValueDefinition
    (no value)Information not available for this record. 179 records have no value for wallrock.
    Plain text, lithologic terms
    weathering
    Weathering.

    Weathering at the site. Textual values of no more than 80 characters. (Source: this data release) Plain text abbreviating only feet as "ft".
    remarks
    Remarks.

    Remarks. Textual values of no more than 400 characters. (Source: this data release) Descriptive text, mostly focused on the mineralogical character of the pegmatite. Uses the following abbreviations for minerals: B = biotite; F = feldspar; M = muscovite; P = perthite; Pl = plagioclase; Q = quartz.
    point_id
    Point ID.

    Record in the points table providing coordinates for this site. Textual values of no more than 12 characters. (Source: this data release) Alphanumeric identifiers without scientific significance

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Lesure, Frank Gardner
  2. Who also contributed to the data set?
    Painstaking digitizing and digital entry of these data was carried out by E. G. Boyce of the USGS, with technical assistance from Kelly Habestroh of the USGS library. Rearrangement of the digital information for distribution through web services and download, as well as composition of the metadata, was carried out by Peter Schweitzer of USGS.
  3. To whom should users address questions about the data?
    Peter N Schweitzer
    USGS ER GD
    Geologist
    12201 Sunrise Valley Drive
    Reston, VA
    USA

    703-648-6533 (voice)
    703-648-6252 (FAX)
    pschweitzer@usgs.gov

Why was the data set created?

Digitizing this previously published information was prompted by the need for information to support the development of forest management plans by the U.S. Forest Service. But the recovery in digital form of printed information of this nature is a key goal of the mineral occurrence database project of the USGS.

How was the data set created?

  1. From what previous works were the data drawn?
    pp577 (source 1 of 1)
    Lesure, Frank Gardner, 1968, Mica deposits of the Blue Ridge in North Carolina: Professional Paper 577, U.S. Government Printing Office, Washington DC.

    Online Links:

    Type_of_Source_Media: paper
    Source_Contribution:
    The subject dataset was created by digitizing this previously published work.
  2. How were the data generated, processed, and modified?
    Date: 2016 (process 1 of 2)
    The paper plates and printed reports of USGS Professional Paper 577 were scanned at high resolution. The plates contain maps at 1:62,500 (3 and 6) and 1:250,000 (2, 4, and 5) scale; these were geographically registered and the points digitized using ArcGIS 10.3. Table 4 of the report was converted to digital form using Dragon voice recognition software with the exception of the remarks field, whose contents were obtained by optical character recognition software. The text of the report (pages 1-17) was scanned at high resolution and subject to optical character recognition as well; the result is provided as a PDF document whose text may be selected or searched. Person who carried out this activity:
    Edward G Boyce
    Midwest Region
    Info Tech Specialist (Data Mgmt)
    U.S. Geological Survey
    Mail Stop 954
    12201 Sunrise Valley Dr
    Reston, VA
    USA

    703-648-6149 (voice)
    703-648-6252 (FAX)
    egboyce@usgs.gov
    Data sources used in this process:
    • pp577
    Date: Jul-2016 (process 2 of 2)
    Digital copies of the data for each plate (as shapefiles) and for each part of table 4 (as Microsoft Excel documents) were converted to SQL code for entry into the PostgreSQL relational database using PostGIS geographic extensions.

    Point and descriptive table row identifiers were disambiguated by including the plate number in each ID field. Where tabular information were listed as coming from plate "5 or 6" the records were matched manually using the names of the sites to assign correct ID values.

    A number of simple corrections were made to name fields and other data fields to remove extraneous punctuation, carriage returns, and to establish one-to-one relationships between corresponding rows in the points and descriptions tables.

    For each record, an XML and a JSON representation of the complete data record was created so that this information can be flexibly re-expressed in the future using appropriate technology (at this writing, 2016, reports of individual sites are composed by transforming the XML representation of the data into HTML using an XSLT stylesheet).

    A geospatial map service was configured to provide these data to the public in the form of an Open Geospatial Consortium Web Map Specification service. The data are provided in an interactive web map interface using this service.

    This metadata record was written to provide detailed documentation of the history of this data conversion effort. Person who carried out this activity:
    Peter N Schweitzer
    USGS ER GD
    Geologist
    12201 Sunrise Valley Drive
    Reston, VA
    USA

    703-648-6533 (voice)
    703-648-6252 (FAX)
    pschweitzer@usgs.gov
  3. What similar or related data should the user be aware of?
    U.S. Geological Survey, 2016, (Complete metadata record).

    Online Links:

    Other_Citation_Details: XML format

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?
    Users should note that this information is not a substantive update of the locations or characteristics of these mineral deposits or operations. The report was published by USGS in 1968 and it is likely that changes in the working status of mines and prospects have occurred since then, and it may be that new deposits have been located which were not known to the author of the 1968 report at the time.
  5. How consistent are the relationships among the observations, including topology?
    It should be noted that more than one mine or prospect may be associated with each map location on the plates. The location numbers are not distinct between map sheets, so in these data the map_number field was adjusted by adding the plate number multiplied by 1000 to each original map number. So map_number values between 2000 and 2999 are located on plate 2, values between 3000 and 3999 are located on plate 3, and so on.

    The maps depicted on the plates did not differentiate feature types graphically. Feature types specified in the feature field of the points table are taken from the feature name, and points shown without numbers are presumed to be unnamed prospects.

    The map scales of the plates vary. Plates 3 and 6, which show the largest number of features, are mapped at 1:62,500, while plates 2,4, and 5 are mapped at 1:250,000. The consequence of this difference is that we should expect the geographic locations to be more precise if they were plotted on plates 3 or 6 than if they were plotted on plates 2.4. or 5.

    The printed text contains numerous instances of words hyphenated across lines. A few of these have been corrected, but some likely remain in the descriptive fields.

    Mines and prospect names that appear in parentheses in the report and spreadsheet are separated into Other Names in the shapefiles attribute tables.

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 ER GD
    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 Professional Paper 577, digitized 2016
  3. What legal disclaimers am I supposed to read?
    These data are released on the condition that neither the U.S. Geological Survey (USGS) nor the United States Government may be held liable for any damages resulting from authorized or unauthorized use. The USGS provides these data "as is" and makes no guarantee or warranty concerning the accuracy of information contained in the 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.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 07-Dec-2016
Metadata author:
Schweitzer, Peter, N
Eastern Mineral Resources Team
12201 Sunrise Valley Drive Mail Stop 954
Reston, VA
USA

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

This page is <https://mrdata.usgs.gov/metadata/pp577.faq.html>
Generated by mp version 2.9.47 on Mon Mar 26 17:20:49 2018