ATL_FAC: usSEABED facies data for the entire U.S. Atlantic Coast

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

Frequently-anticipated questions:


What does this data set describe?

    Title:
    ATL_FAC: usSEABED facies data for the entire U.S. Atlantic Coast
    Abstract:
    The facies data layer (_FAC.txt) is a point coverage of known sediment samplings, inspections, and probings from the usSEABED data collection and integrated using the software system dbSEABED. The facies data layer (_FAC.txt)represents concatenated information about components (minerals and rock type), genesis (igneous, metamorphic, carbonate, terrigenous), and other appropriate groupings of information about the seafloor. The facies data are parsed from written descriptions from cores, grabs, photographs, and videos, and may apply only to a subsample as denoted by the Top, Bottom, and SamplePhase fields. Lack of values in a defined facies field does not necessarily imply lack of the components defining that field, but may imply a lack of data for that field.
    Supplemental_Information:
    This layer can be used in a relational data base, using the DataSetKey to link to the ATL_SRC.txt file for brief metadata information and to formal metadata written on each source, and to the other data files of usSEABED using the SiteKey or SampleKey as relational links.

  1. How should this data set be cited?

    U.S. Geological Survey, and Colorado, University of , 2005, ATL_FAC: usSEABED facies data for the entire U.S. Atlantic Coast:.

    Online Links:

    This is part of the following larger work.

    Reid, J.M., Reid, J.A., Jenkins, C.J., Hastings, M.E., Williams, S.J., and Poppe, L.J., 2005, usSEABED: Atlantic Coast Offshore Surficial Sediment Data Release: Data Series 118, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Science Center, Woods Hole, MA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -81.99860
    East_Bounding_Coordinate: -65.00000
    North_Bounding_Coordinate: 44.90600
    South_Bounding_Coordinate: 23.02000

  3. What does it look like?

    <https://pubs.usgs.gov/ds/2005/118/data/atl_fac.jpg> (JPEG)
    Image map showing extent of data layer coverage

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

    Calendar_Date: 2005
    Currentness_Reference: publication date

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

    Geospatial_Data_Presentation_Form: vector digital data

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

      • Point (13679)

    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.00001. Longitudes are given to the nearest 0.00001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    Point
    Sample location (Source: Source reports)

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Forams
    Those samples with a foraminferal component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a foraminifera, benthic foraminifera, planktonic foraminifera, large foraminifera, or arenaceous foraminifera component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    LATITUDE

    Shell
    Shell (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a specific shell or shell debris component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    WATERDEPTH

    HardPlant
    Hard marine plants (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a coralline algae, coral algae, halimeda, or calcareous algae component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    SAMPLEBASE

    SITE

    DATASETKEY

    Latitude
    Latitude coordinate of sample location (Source: Source data)

    location information in decimal degrees

    SampleTop
    Measured subbottom depth information for each point sample (top) (Source: Source data)

    Subsample location information in meters

    SiteKey
    Site key (relational link) (Source: dbSEABED MNEt program)

    Unique sequential numeric key to information about the same site in other usSEABED data files

    Carbonate
    Those samples with a carbonate component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a specific carbonate, calcareous crust, calcite, dolomite, limestone, or siderite component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    Volcanic
    Those samples with a volcanic component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a specific volcanic rock (volrck and vol_rck), basalt, pumice, volcanic glass, or volcanic sediment; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    Carbon
    Those samples with a carbon component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a organic carbon, bitumin, coal, or peat component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    SilcPelag
    Silceous pelagic fauna/flora (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a diatom, radiolaria, or siliceous ooze component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    Coral
    Corals (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a coral, coral reef, coral debris, or solitary coral component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    METAMORPHI

    MINERALIZE
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    AUTHFEMN

    OOZE

    CARBON

    GEOCHEMSIG

    FORAMS

    OTHERCALCP

    Ooze
    Those samples with a ooze component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a calcareous ooze, siliceous ooze, or other ooze component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    SHELL
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    CORAL

    HARDPLANT

    Longitude
    Longitude coordinate of sample location (Source: Source data)

    location information in decimal degrees

    IGNEOUS

    DataSetKey
    Data set key (relational link) (Source: dbSEABED MNEt program)

    Unique sequential numeric key to SRC file

    VOLCANIC

    SampleKey
    Sample key (relational link) (Source: Source data)

    Unique sequential numeric key to information about the same sample or subsample in other usSEABED data files

    METAMORPHI

    Igneous
    Those samples with a igneous component (Source: db9_dct.rtf, db9_FAC.txt for U.S. waters)

    Result of filters based on fuzzy set theory determining degree of membership (0-100) for samples that include those terms which denote a specific igneous rock, andesite, basalt, gabbro, ultramafic, or granite component; see table D in the data publication (Larger_Work_Citation) for list of trigger terms under each component mentioned.

    AUTHFEMN

    OOZE

    CARBON

    GEOCHEMSIG

    FORAMS

    OTHERCALCP

    SILCPELAG

    SHELL

    CORAL

    HARDPLANT


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    We thank the following interns for their assistance in data entry, coding, and data testing: Viness Ubert, Emma Mitchell, Emily Denham and Shea Quinn.

  3. To whom should users address questions about the data?

    Jane A. Reid
    U.S. Geological Survey
    Geologist
    Pacific Science Center
    Santa Cruz, CA 95060
    USA

    831-427-4727 (voice)
    jareid@usgs.gov

    Contact_Instructions: email preferred


Why was the data set created?

The Facies layer can be used to investigate the known information about a particular area of the seafloor. These data are intended for science researchers, policy makers, students, and the general public. The data can be used with geographic information systems (GIS) software to display geologic and oceanographic information.


How was the data set created?

  1. From what previous works were the data drawn?

    Varies with source (source 1 of 1)
    Various, Unpublished and published material, See separate listing, ATL_SRC.txt, and links provided therein, within this publication for the specific sources and associated metadata.: Various, Various.

    Other_Citation_Details:
    X number of sources, both published and unpublished, are used as the sources of information for usSEABED. Metadata for each source is linked through the usSEABED source file (ATL_SRC.txt). Sources include the U.S. Geological Survey (USGS), the U.S. Army Corps of Engineers (USACE), Minerals Management Service (MMS), National Oceanic and Atmospheric Administration (NOAA), Virginia Institute of Marine Science (VIMS), the Maryland and New Jersey State Geological Surveys (MGS, NJGS), NOAA's National Geophysical Data Center (NGDC), the Smithsonian Institution, and others.
    Type_of_Source_Media: Hard copy and digital
    Source_Contribution:
    Point locations, descriptions, and various analytical data (textural, granulometric, geochemical, geophysical, acoustic) on sediments, rock exposure, and benthos. Varies with source.

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

    (process 1 of 1)
    Source data may be digitized as necessary (typed or scanned in), with a visual inspection of digitized data to the source report and corrections as necessary, and are tested for completeness in Microsoft Excel as appropriate. Other digital data may be decoded using source-specific programs, downloaded via the web, or sent directly to the USGS or University of Colorado via email. Data are formatted into the dbSEABED Data Entry template (db9_DataEntry.xls, version 08/07/2004) by hand, and tested using the dbSEABED relational database program (RDBi, version 01/05/2005) for correctness of formatting. Data are compiled into source data resource files (DRF) and processed through the dbSEABED data mining program (MNEt, version 04/07/2005) program, using the dbSEABED thesaurus (db9_dct.rtf, version 04/07/2005) and facies set up file for U.S. waters (db9_FAC.txt, version 04/07/2005). Data are iteratively reprocessed and corrected until noted errors are fixed, as recorded by the _RBDS.2fx and _MNE.DGN files. Data are exercised in a GIS for location tests and useability.

    Person who carried out this activity:

    U.S. Geological Survey
    c/o Jamey M. Reid
    IT Specialist (Data Management)
    USGS Woods Hole Science Centers
    Woods Hole, MA 02543-1598

    (508) 548-8700 x2204 (voice)
    jreid@usgs.gov

    Contact_Instructions: email preferred
    Data sources produced in this process:
    • ATL_FAC.txt

  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?

    Accuracy of each attribute is dependent on the accuracy of the original source description and the values calculated by the mining software, dbSEABED. Values are based on filters using fuzzy set theory and represent a measure of truth about the attribute.

  2. How accurate are the geographic locations?

    Locational accuracy is dependent on both the accuracy of the navigational technique and the level of detail about the location as recorded in the individual data sources, and may vary widely (ie.g., from 0.005 km (differential GPS) in the more recent surveys to greater than 2 km based on radar, Loran, or dead reckoning in the older surveys. Users of the data should note the metadata written about the original sources and use their own criteria for assessing the accuracy of the locations.

  3. How accurate are the heights or depths?

    Depth determinations, both water depth and subsample depth, are dependent on the accuracy of the depth determination technique and the level of detail noted in the original source. Users of the data should note the metadata written about the original sources and use their own criteria for assessing the accuracy of the locations.

  4. Where are the gaps in the data? What is missing?

    Additional useable data may exist in this area; the authors appreciate any information and leads.

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

    Data in the usSEABED data collection are based on the observations and analyses of others, filtered through a unifying and mining software. Each source report varies in type of information/data recorded and format. Only those observations that are recorded can be filtered and mined; only presence (not absences) of information can be noted.


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:
Public domain data from the U.S. Government are freely redistributable with the proper metadata and source attribution. Please recognize the U.S. Geological Survey (USGS) as the source of this information.

  1. Who distributes the data set? (Distributor 1 of 1)

    U.S. Geological Survey
    c/o Jamey M. Reid
    IT Specialist (Data Management)
    USGS Woods Hole Science Center
    Woods Hole, MA 02543-1598

    (508) 548-8700 x2204 (voice)
    jreid@usgs.gov

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

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    Although this data set has been used by the U.S. Geological Survey (USGS), no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and/or related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials.

    Trade, firm, or product names and other references to non-USGS products and services are provided for information only and do not constitute endorsement or warranty, express or implied, by the USGS, USDOI, or U.S. Government, as to their suitability, content, usefulness, functioning, completeness, or accuracy.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    These data are available in Environmental Systems Research Institute (ESRI) shapefile format. The user must have ArcGIS® or ArcView® 3.0 or greater software to read and process the data file. In lieu of ArcView or ArcGIS, the user may utilize another GIS application package capable of importing the data. A free data viewer, arcexplorer, capable of displaying the data is available from ESRI at www.esri.com.


Who wrote the metadata?

Dates:
Last modified: 08-Apr-2005
Last Reviewed: 12-May-2005

Metadata author:
Jane A. Reid
U.S. Geological Survey
Geologist
Pacific Science Center
Santa Cruz, CA 95060
USA

831-427-4727 (voice)
jareid@usgs.gov

Contact_Instructions: email preferred
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:


Generated by mp version 2.7.33 on Wed May 18 11:18:50 2005