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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Globorotaloides hexagonus trace element ablation profiles] - Globorotaloides
hexagonus trace element ablation profiles from samples collected from MOCNESS
tows from R/V Sikuliaq cruise SKQ201701S in 2017 (Glacial-Interglacial Changes
in Oxygen Minimum Zones Using Deep-Dwelling, Low-Oxygen Planktic Foraminifera)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_919606_v1)
Range: longitude = 21.54 to 21.86°E
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
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.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    [The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  filename {
    String long_name "Filename";
    String units "unitless";
  }
  MOCNESS_cast {
    Int32 actual_range 716, 726;
    String long_name "Mocness_cast";
    String units "unitless";
  }
  net {
    String long_name "Net";
    String units "unitless";
  }
  foram {
    String long_name "Foram";
    String units "unitless";
  }
  file {
    Int32 actual_range 1, 7;
    String long_name "File";
    String units "unitless";
  }
  time_elapsed {
    Float32 actual_range 0.0, 77.27389;
    String long_name "Time";
    String units "seconds";
  }
  X24Mg_43Ca {
    Float32 actual_range 5.3896e-4, 0.01708233;
    String long_name "X24mg_43ca";
    String units "mol per mol";
  }
  X25Mg_43Ca {
    Float32 actual_range 3.6666e-4, 0.02849409;
    String long_name "X25mg_43ca";
    String units "mol per mol";
  }
  X55Mn_43Ca {
    Float32 actual_range -1.03e-6, 4.0048e-4;
    String long_name "X55mn_43ca";
    String units "mol per mol";
  }
  X66Zn_43Ca {
    Float32 actual_range 7.89e-6, 0.02254958;
    String long_name "X66zn_43ca";
    String units "mol per mol";
  }
  X88Sr_43Ca {
    Float32 actual_range 7.2343e-4, 0.0019683;
    String long_name "X88sr_43ca";
    String units "mol per mol";
  }
  X138Ba_43Ca {
    Float32 actual_range 1.45e-6, 0.05810508;
    String long_name "X138ba_43ca";
    String units "mol per mol";
  }
  depth_micron {
    Float32 actual_range 0.0, 30.90956;
    String long_name "Depth";
    String units "micron";
  }
  date_time_UTC {
    String long_name "Date_time_utc";
    String units "unitless";
  }
  Lat_in {
    Float32 actual_range 21.38, 21.68;
    String long_name "Lat_in";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 21.54, 21.86;
    String axis "X";
    String ioos_category "Location";
    String long_name "Lat_out";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  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.919606.1";
    Float64 Easternmost_Easting 21.86;
    Float64 geospatial_lon_max 21.86;
    Float64 geospatial_lon_min 21.54;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:16:01Z (local files)
2024-11-08T06:16:01Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_919606_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/919606";
    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 "The planktic foraminifer Globorotaloides hexagonus is found in temperate to tropical oxygen minimum zones (OMZs). Their preferred habitat make G. hexagonus an important species for the development of oxygen-related paleoproxies. Here we report trace-element-to-calcium (TE/Ca) ratios with depth in the shell of G. hexagonus from the Eastern Tropical North Pacific (21 N, 117 W) . Individuals were isolated from a series of Multiple Opening/Closing Net and Environmental Sensing System (MOCNESS) tows on the R/V Sikuliaq  in January and February 2017 and represent a wide range of depth habitats and  oxygen concentrations. Oxygen concentration and depth from MOCNESS are provided in the metadata for each sample. Trace elements (Mg, Mn, Zn, Sr, Ba, Ca) were quantified using laser ablation ICP-MS from the outside to the inside of the shell, allowing for a reconstruction of TE/Ca with depth in the shell. MOCNESS data were collected by Dr. Karen Wishner (URI),  ablation data were collected by Dr. Catherine Davis (NCSU) and Dr. Jennifer Fehrenbacher (OSU), and data were prepared by Dr. Shannon Doherty (NCSU and UAF).";
    String title "[Globorotaloides hexagonus trace element ablation profiles] - Globorotaloides hexagonus trace element ablation profiles from samples collected from MOCNESS tows from R/V Sikuliaq cruise SKQ201701S in 2017 (Glacial-Interglacial Changes in Oxygen Minimum Zones Using Deep-Dwelling, Low-Oxygen Planktic Foraminifera)";
    Float64 Westernmost_Easting 21.54;
  }
}

 

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