X-ray fluorescence (XRF) scans of gravity cores and push cores from the Escanaba Trough (Gorda Ridge), soil mode

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

Frequently anticipated questions:

What does this data set describe?

Title:
X-ray fluorescence (XRF) scans of gravity cores and push cores from the Escanaba Trough (Gorda Ridge), soil mode
Abstract:
This portion of the data release contains X-ray fluorescence (XRF) data from push cores and gravity cores collected from the Escanaba Trough vent field, Gorda Ridge, in the northeast Pacific Ocean. These data were collected in 2022 (USGS Field Activity 2022-621-FA). The XRF data were collected with the sensor in “soil" mode and are provided in comma-delimited files (.csv).
Supplemental_Information:
Additional information about the field activity or activities from which these data were derived is available online at:
https://cmgds.marine.usgs.gov/fan_info.php?fan=2022-621-FA
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Adamczyk, Katlin Bowman, Gartman, Amy, Favela, Jaycee, and Tidwell, Jacob, 20250317, X-ray fluorescence (XRF) scans of gravity cores and push cores from the Escanaba Trough (Gorda Ridge), soil mode: data release DOI:10.5066/P13B46QX, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Adamczyk, Katlin Bowman, Gartman, Amy, Favela, Jaycee, and Tidwell, Jacob, 2025, Computed tomography (CT) scans, photographs, geochemistry, grain-size and total carbon analysis, X-ray fluorescence (XRF) scans, X-ray diffraction (XRD), magnetic susceptibility, and gamma-ray bulk density data of gravity cores and push cores from the Escanaba Trough (Gorda Ridge): data release DOI:10.5066/P13B46QX, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Adamczyk, K., Gartman, A., Favela, J., and Tidwell, J., 2025, Computed tomography (CT) scans, photographs, geochemistry, grain-size and total carbon analysis, X-ray fluorescence (XRF) scans, X-ray diffraction (XRD), magnetic susceptibility, and gamma-ray bulk density data of gravity cores and push cores from the Escanaba Trough (Gorda Ridge): U.S. Geological Survey data release, https://doi.org/10.5066/P13B46QX
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -127.5362
    East_Bounding_Coordinate: -127.4076
    North_Bounding_Coordinate: 41.1632
    South_Bounding_Coordinate: 40.6957
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/671aab7dd34efed5620fb829?name=XRF.JPG&allowOpen=true (JPEG)
    Line plots of XRF metal concentrations verses sediment core depth.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Aug-2022
    Ending_Date: 08-Aug-2022
    Currentness_Reference:
    Time data were compiled to completion of the last process step
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: comma-delimited text
  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):
      • Point (2493)
    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.001. Longitudes are given to the nearest 0.001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
  7. How does the data set describe geographic features?
    GC01-X_soil.csv, GC01-Y_soil.csv, GC01-Z_soil.csv, GC03-X_soil.csv, GC03-Y_soil.csv, GC03-Z_soil.csv, GC04-X_soil.csv, GC04-Y_soil.csv, GC04-Z_soil.csv, GC05-Z_soil.csv, GC06-X_soil.csv, GC06-Y_soil.csv, GC06-Z_soil.csv, GC08-X_soil.csv, GC08-Y_soil.csv, GC08-Z_soil.csv, GC09-Y_soil.csv, GC09-Z_soil.csv, J2-1418-PC03_soil.csv,.csv, J2-1418-PC06_soil.csv, J2-1418-PC08_soil.csv, J2-1418-PC12_soil.csv, J2-1418-PC15_soil.csv, 'J2-1419-PC01_soil.csv, J2-1419-PC02_soil.csv, J2-1419-PC05_soil.csv, J2-1419-PC08_soil.csv, J2-1419-PC11_soil.csv, J2-1419-PC14_soil.csv, J2-1420-PC01_soil.csv, J2-1420-PC02_soil.csv, J2-1420-PC05_soil.csv, J2-1420-PC08_soil.csv, J2-1420-PC11_soil.csv, J2-1420-PC14_soil.csv, J2-1421-PC01_soil.csv, J2-1421-PC02_soil.csv, J2-1421-PC05_soil.csv, J2-1422-PC01_soil.csv, J2-1422-PC04_soil.csv, J2-1422-PC07_soil.csv, J2-1422-PC10_soil.csv, J2-1422-PC13_soil.csv, J2-1424-PC01_soil.csv, J2-1424-PC04_soil.csv, J2-1424-PC07_soil.csv, J2-1424-PC10_soil.csv, J2-1424-PC13_soil.csv, J2-1425-PC01_soil.csv, J2-1426-PC01_soil.csv, J2-1426-PC04_soil.csv, J2-1426-PC07_soil.csv, J2-1426-PC10_soil.csv, J2-1426-PC13_soil.csv
    Comma-separated value (CSV) files containing XRF data. The first row is a header row. The file name corresponds to the core id. TN403_CoreLocations contains the latitude, longitude, and water depth for each core id. Values of -9999 indicate that the XRF measurements are not available. The ranges listed in the following attributes represent the combined range domains for all files. (Source: Producer defined)
    core_depth_cm
    Measured depth below top of core liner (Source: producer defined)
    Range of values
    Minimum:0.0
    Maximum:152.0
    Units:centimeters
    Resolution:.1
    XRF_TotalCounts
    The total number of X-ray photons detected by the XRD during a measurement. Values of -9999 indicate that data are not available. (Source: producer defined)
    Range of values
    Minimum:0
    Maximum:1339838
    Units:counts
    Resolution:1
    XRF_Live_Time_sec
    The total time the XRF was detecting photons during a measurement. This is less than the set 20 second scan time. Values of -9999 indicate that data are not available. (Source: producer defined)
    Range of values
    Minimum:10
    Maximum:18
    Units:seconds
    Resolution:1
    Mn_ppm
    Manganese abundance in parts per million (ppm). Values of -9999 indicate that manganese data are not available. The limit of detection was 5.00-8.00 ppm. (Source: producer defined)
    Range of values
    Minimum:-205.93
    Maximum:21024.06
    Units:parts per million
    Resolution:.01
    Mn-Error_ppm
    Estimated error of manganese abundance in parts per million (ppm). Values of -9999 indicate that manganese data are not available. (Source: producer defined)
    Range of values
    Minimum:2.07
    Maximum:203.04
    Units:parts per million
    Resolution:.01
    Fe_ppm
    Iron abundance in parts per million (ppm). Values of -9999 indicate that iron data are not available. The limit of detection was 10.00-20.00 ppm. (Source: producer defined)
    Range of values
    Minimum:1.61
    Maximum:998593.04
    Units:parts per million
    Resolution:.01
    Fe-Error_ppm
    Estimated error of iron abundance in parts per million (ppm). Values of -9999 indicate that iron data are not available. (Source: producer defined)
    Range of values
    Minimum:4.14
    Maximum:19584.86
    Units:parts per million
    Resolution:.01
    Cu_ppm
    Copper abundance in parts per million (ppm). Values of -9999 indicate that copper data are not available. The limit of detection was 5.00-8.00 ppm. (Source: producer defined)
    Range of values
    Minimum:-89.79
    Maximum:21499.59
    Units:parts per million
    Resolution:.01
    Cu-Error_ppm
    Estimated error of copper abundance in parts per million (ppm). Values of -9999 indicate that copper data are not available. (Source: producer defined)
    Range of values
    Minimum:1.36
    Maximum:466.80
    Units:parts per million
    Resolution:.01
    Pb_ppm
    Lead abundance in parts per million (ppm). Values of -9999 indicate that lead data are not available. The limit of detection was 3.00-5.00 ppm. (Source: producer defined)
    Range of values
    Minimum:-15.95
    Maximum:12909.97
    Units:parts per million
    Resolution:.01
    Pb-Error_ppm
    Estimated error of lead abundance in parts per million (ppm). Values of -9999 indicate that lead data are not available. (Source: producer defined)
    Range of values
    Minimum:.94
    Maximum:277.94
    Units:parts per million
    Resolution:.01
    S_ppm
    Sulfur abundance in parts per million (ppm). Values of -9999 indicate that sulfur data are not available. The limit of detection was not reported. (Source: producer defined)
    Range of values
    Minimum:-350.05
    Maximum:566710.25
    Units:parts per million
    Resolution:.01
    S-Error_ppm
    Estimated error of sulfur abundance in parts per million (ppm). Values of -9999 indicate that sulfur data are not available. (Source: producer defined)
    Range of values
    Minimum:98.89
    Maximum:17902.77
    Units:parts per million
    Resolution:.01
    Ca_ppm
    Calcium abundance in parts per million (ppm). Values of -9999 indicate that calcium data are not available. The limit of detection was 30.00-50.00 ppm. (Source: producer defined)
    Range of values
    Minimum:-17288.10
    Maximum:19740.13
    Units:parts per million
    Resolution:.01
    Ca-Error_ppm
    Estimated error of calcium abundance in parts per million (ppm). Values of -9999 indicate that calcium data are not available. (Source: producer defined)
    Range of values
    Minimum:13.81
    Maximum:451.72
    Units:parts per million
    Resolution:.01
    Entity_and_Attribute_Overview: The first line of the csv file is a header line.
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Katlin Bowman Adamczyk
    • Amy Gartman
    • Jaycee Favela
    • Jacob Tidwell
  2. Who also contributed to the data set?
    Exploring the Seafloor and Oceanic Footprints is an interagency effort involving the National Oceanic and Atmospheric Administration, the U.S. Geological Survey, and the Bureau of Ocean Energy Management. Funding is acknowledged from NOAA Ocean Exploration via its Ocean Exploration Fiscal Year 2019 Funding Opportunity and through the National Oceanographic Partnership Program (NOPP), from the USGS Coastal and Marine Hazards and Resources Enhanced Funding Opportunities, and from the Bureau of Ocean Energy Management through Interagency Agreement M19PG00021 with the United States Geological Survey.
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

Data were obtained to characterize downcore geochemical properties of sediments. These data are intended for science researchers, students, policy makers, and the general public.

How was the data set created?

  1. From what previous works were the data drawn?
    TN403_CoreLocations (source 1 of 2)
    Adamczyk, Katlin, Gartman, Amy, Favela, Jaycee, and Tidwell, Jacob, 2025, Location and water depth for gravity cores and push cores from the Escanaba Trough (Gorda Ridge): U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: U.S. Geological Survey data release
    Source_Contribution:
    Latitude, longitude, and water depth information for gravity cores and push cores from this same data release
    TN403_Geochemistry (source 2 of 2)
    Adamczyk, Katlin, Gartman, Amy, Favela, Jaycee, and Tidwell, Jacob, 2025, Geochemistry of sediment subsamples from gravity and push cores from the Escanaba Trough (Gorda Ridge).

    Online Links:

    Type_of_Source_Media: U.S. Geological Survey data release
    Source_Contribution:
    Element concentrations for sediment subsamples from this same data release
  2. How were the data generated, processed, and modified?
    Date: 13-Jun-2022 (process 1 of 2)
    Push core and gravity core samples were collected on the R/V Thomas G. Thompson between May 24, 2022, and June 13, 2022, during the TN403 Escanaba Trough expedition, which was led and staffed by USGS employees. Push cores were pushed into sediment at 37 locations by ROV Jason’s manipulator arm in water depths between 3,201 and 3,301 meters. Gravity cores were collected using a gravity corer at 7 locations in water depths between 3209 and 3304 meters. Gravity cores greater than 60 cm in length were cut into sections onboard the ship and labeled ‘X’ (0-60 cm), ‘Y’ (60-120 cm), and ‘Z’ (>120 cm). All cores were stored upright and refrigerated until return to shore.
    Date: 08-Aug-2022 (process 2 of 2)
    Cores were split into "working" and "archive" halves in the lab. Sediment surfaces were cleaned and smoothed on the "archive" halves of split cores. A four micron-thick ultralene film that is transparent to x-rays was applied to the sediment surface in order to protect the XRF window. Cores were loaded onto the track of a Geotek Multi Sensor Core Logger (MSCL) with an Olympus Delta Professional XRF gun mounted to an arm that moves the XRF sensor vertically on and off the core surface. The XRF sensor was calibrated before each scan using a 316-alloy reference coin. The XRF window is 1x1 cm square and measurements were collected between 0.5 and 2 cm downcore, automated by the motors on the MSCL. The XRF was run in "soil" mode with two beams at 20 seconds each. Data were processed with Geotek MSCL software and elemental abundances are reported in parts per million (ppm). Geochem mode processes the data as a closed sum compositional dataset, assuming that all components add up to 100 percent.
  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?
    No formal attribute accuracy tests were conducted.
  2. How accurate are the geographic locations?
    The locations of push core samples were determined using ROV Jason’s ultra-short baseline (USBL) navigation. Accuracy for this depth is approximately 6-26 m. The locations of gravity core samples were determined using the R/V Thomas G. Thompson’s GPS navigation, which is accurate to less than 5 m. A formal accuracy assessment of the horizontal positional information in the dataset has not been conducted.
  3. How accurate are the heights or depths?
    For push core samples, the vertical accuracy was determined with ROV Jason’s altimeter, which is accurate to less than 1 m. For gravity core samples, the vertical accuracy was determined with the R/V Thomas G. Thompson’s multibeam bathymetry system. No formal positional accuracy tests were conducted.
  4. Where are the gaps in the data? What is missing?
    Dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    XRF element concentrations were compared to geochemistry subsample element concentrations (TN403_Geochemistry, published as part of this data release) collected from the same depth intervals. Elements that showed linear agreement at an R-squared value greater than 0.3 are included in this data release.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originator of the dataset and in products derived from these data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in .csv format contained in a single file.
  3. What legal disclaimers am I supposed to read?
    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 on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  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 can be viewed with Microsoft Excel or any text reader.

Who wrote the metadata?

Dates:
Last modified: 17-Mar-2025
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/ScienceBase/DR_P13B46QX/TN403_XRF_soil_Metadata.faq.html>
Generated by mp version 2.9.51 on Tue Apr 1 10:12:10 2025