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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Cocos Ridge C14 Data] - Radiocarbon (C14) calendar ages measured on pelagic
foraminifera species collected from sediment cores from the Cocos
Ridge (Eastern Equatorial Pacific) acquired during cruise SR2113 between
November - December 2021. (Collaborative Research: New approaches to study
calcium carbonate dissolution on the sea floor and its impact on paleo-proxy
interpretations)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_925313_v1)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Station (unitless) ?          "1"    "5"
 Date (unitless) ?          "2021-12-01"    "2021-12-14"
 Latitude (degrees_north) ?          5.35008    6.78487
 longitude (degrees_east) ?          -88.26095    -86.59988
  < slider >
 depth (Water_column_depth, m) ?          1630    3223
  < slider >
 Sediment_Depth (centimeters (cm)) ?          0.25    30.5
 Foram_sp (unitless) ?          "Globigerinoides ru..."    "Trilobatus sacculi..."
 AphiaID (unitless) ?          113444    1026286
 C14_age (year (yr)) ?          859    23557
 
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 {
  Station {
    String long_name "Station";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 5.35008, 6.78487;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -88.26095, -86.59988;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 1630, 3223;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Water_column_depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Sediment_Depth {
    Float32 actual_range 0.25, 30.5;
    String long_name "Sediment_depth";
    String units "centimeters (cm)";
  }
  Foram_sp {
    String long_name "Foram_sp";
    String units "unitless";
  }
  AphiaID {
    Int32 actual_range 113444, 1026286;
    String long_name "Aphiaid";
    String units "unitless";
  }
  C14_age {
    Int32 actual_range 859, 23557;
    String long_name "C14_age";
    String units "year (yr)";
  }
 }
  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.925313.1";
    Float64 Easternmost_Easting -86.59988;
    Float64 geospatial_lon_max -86.59988;
    Float64 geospatial_lon_min -88.26095;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 3223.0;
    Float64 geospatial_vertical_min 1630.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-05T14:50:41Z (local files)
2024-11-05T14:50:41Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_925313_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/925313";
    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.";
    String sourceUrl "(local files)";
    String summary "These data include radiocarbon (C14) calendar ages measured on pelagic foraminifera species collected from sediment cores from the Cocos Ridge in the Eastern Equatorial Pacific. This cruise was aboard the R/V Sally Ride between 2021-11-20 and 2021-12-20. Instruments used were a multicorer and accelerator mass spectrometry . These data contributed to our understanding of the carbonate chemistry system in this region, particularly regarding carbonate dissolution in deep-sea sediments. Patrick Rafter (UC Irvine) measured C14 calendar ages.";
    String title "[Cocos Ridge C14 Data] - Radiocarbon (C14) calendar ages measured on pelagic foraminifera species collected from sediment cores from the Cocos Ridge (Eastern Equatorial Pacific) acquired during cruise SR2113 between November - December 2021. (Collaborative Research: New approaches to study calcium carbonate dissolution on the sea floor and its impact on paleo-proxy interpretations)";
    Float64 Westernmost_Easting -88.26095;
  }
}

 

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