BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [X-ray diffraction from seafloor sulfide deposits East Pacific Rise 9-10
North] - Synchrotron micro-probe X-ray diffraction data from seafloor sulfide
deposits collected during cruise AT42-09 on the East Pacific Rise (EPR) in
April 2019. (Collaborative Research: From hot to cold in the dark - shifts in
seafloor massive sulfide microbial communities as physical and geochemical
conditions change after venting ceases)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_937020_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Cruise (unitless) ?          "AT42-09"    "AT42-09"
 File_name (unitless) ?          "ALV5013_01_R01c/50..."    "ALV5019_03_R01a/AL..."
 Sample_name (unitless) ?          "ALV5013-01-R01b"    "ALV5019-03-R01a"
 sample_descrip (Time, unitless) ?          "T0"    "T0"
 Hydrotherml_vent_category (unitless) ?          "Type 1"    "Type 4"
 Location (unitless) ?          "Bio9"    "Mosh Pit"
 latitude (Lat_dd, degrees_north) ?          9.503203    9.846861
  < slider >
 longitude (Lon_dd, degrees_east) ?          -104.2936    -104.1749
  < slider >
 depth_f (Depth_mbs, m) ?          2506.12    2517.12
 Hdg (degrees) ?          34.0    178.0
 Date_collected (unitless) ?          "2019-04-04"    "2019-04-10"
 Time_collected (unitless) ?          "17:46:29"    "21:22:33"
 time (Iso_datetime_utc, UTC) ?          2019-04-04T17:56:20Z    2019-04-10T19:32:45Z
  < slider >
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  File_name {
    String long_name "File_name";
    String units "unitless";
  }
  Sample_name {
    String long_name "Sample_name";
    String units "unitless";
  }
  sample_descrip {
    String long_name "Time";
    String units "unitless";
  }
  Hydrotherml_vent_category {
    String long_name "Hydrotherml_vent_category";
    String units "unitless";
  }
  Location {
    String long_name "Location";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 9.503203, 9.846861;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Lat_dd";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -104.2936, -104.1749;
    String axis "X";
    String ioos_category "Location";
    String long_name "Lon_dd";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth_f {
    Float32 actual_range 2506.12, 2517.12;
    String long_name "Depth_mbs";
    String units "m";
  }
  Hdg {
    Float32 actual_range 34.0, 178.0;
    String long_name "Hdg";
    String units "degrees";
  }
  Date_collected {
    String long_name "Date_collected";
    String units "unitless";
  }
  Time_collected {
    String long_name "Time_collected";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.55440058e+9, 1.554924765e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.937020.1";
    Float64 Easternmost_Easting -104.1749;
    Float64 geospatial_lat_max 9.846861;
    Float64 geospatial_lat_min 9.503203;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -104.1749;
    Float64 geospatial_lon_min -104.2936;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-10-11T20:47:08Z (local files)
2024-10-11T20:47:08Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_937020_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/937020";
    String institution "BCO-DMO";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    Float64 Northernmost_Northing 9.846861;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 9.503203;
    String summary 
"Synchrotron micro-probe X-ray diffraction data were collected for seafloor sulfide deposits. Seafloor sulfide mineral samples were collected from hydrothermally active chimneys and inactive off-axis massive sulfide deposits at East Pacific Rise (EPR) 9.50°N in 2019-2021 on cruise AT42-09. Samples were collected using the HOV Alvin. Samples were placed in a positive-pressure glove bag flushed with N2 (g), sparged with N2, heat-sealed into mylar bags containing Anaeropaks, and stored at -20°C.

Epoxy embedded petrographic thin sections were created using these samples. Subsamples were dried for 24 hours under N2 (g), vacuum embedded in epoxy resin (Struers EpoFix Resin, 1L kit: Part #40200030) following manufacturer's guidelines, and cured under N2 (g) for 24 hours. Each epoxy-embedded sample was pre-cut using a wafering saw then sent to Spectrum Petrographics, Inc. (Washington, USA) for preparation as 30 micron thick, double-polished thin sections mounted on quartz slides using methods to limit sample exposure to water and ambient air. When not in use, thin-sections were stored under N2 (g) to limit oxidation. Thin sections were analyzed for X-ray diffraction at the X-ray Fluorescence Microprobe beamline \"XFM\", National Synchrotron Light Source II (NSLS II), Brookhaven National Laboratory, NY.";
    String time_coverage_end "2019-04-10T19:32:45Z";
    String time_coverage_start "2019-04-04T17:56:20Z";
    String title "[X-ray diffraction from seafloor sulfide deposits East Pacific Rise 9-10 North] - Synchrotron micro-probe X-ray diffraction data from seafloor sulfide deposits collected during cruise AT42-09 on the East Pacific Rise (EPR) in April 2019. (Collaborative Research: From hot to cold in the dark - shifts in seafloor massive sulfide microbial communities as physical and geochemical conditions change after venting ceases)";
    Float64 Westernmost_Easting -104.2936;
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 2.22
Disclaimers | Privacy Policy | Contact