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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Cr concentration and isotope data using dissolved Cr and different Cr species
from RR1805] - Chromium (Cr) concentration and isotope data determined using
dissolved Cr and different Cr species from samples collected on R/V Roger
Revelle cruise RR1805 in April-May 2018 (Cr Isotope Oceanography of the Eastern
Tropical North Pacific Ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_925569_v1)
Range: longitude = -107.0 to -106.0°E, depth = 10.0 to 500.0m
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 {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 17.0, 20.2;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -107.0, -106.0;
    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 10, 500;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Total_dissolved_Cr {
    Float32 actual_range 2.29, 3.21;
    String long_name "Total_dissolved_cr";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  Total_dissolved_d53Cr {
    Float32 actual_range 1.04, 1.32;
    String long_name "Total_dissolved_d53cr";
    String units "permil (‰)";
  }
  CrIII {
    Float32 actual_range 0.85, 2.16;
    String long_name "Criii";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  d53CrIII {
    Float32 actual_range -0.14, 0.31;
    String long_name "D53criii";
    String units "permil (‰)";
  }
  CrIII_pcnt_of_total {
    Float32 actual_range 26.0, 79.0;
    String long_name "Criii_pcnt_of_total";
    String units "percent (%)";
  }
  Calculated_CrVI {
    Float32 actual_range 0.58, 2.36;
    String long_name "Calculated_crvi";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  Calculated_d53CrVI {
    Float32 actual_range 1.5, 5.33;
    String long_name "Calculated_d53crvi";
    String units "permil (‰)";
  }
  Measured_CrVI {
    Float32 actual_range 0.99, 1.52;
    String long_name "Measured_crvi";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  Measured_d53Cr {
    Float32 actual_range 2.23, 2.98;
    String long_name "Measured_d53cr";
    String units "permil (‰)";
  }
 }
  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.925569.1";
    Float64 Easternmost_Easting -106.0;
    Float64 geospatial_lon_max -106.0;
    Float64 geospatial_lon_min -107.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 500.0;
    Float64 geospatial_vertical_min 10.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:46:17Z (local files)
2024-11-08T05:46:17Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_925569_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/925569";
    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 "Changes in chromium (Cr) isotope ratios due to fractionation between trivalent (Cr(III)) and hexavalent (Cr(VI)) are being utilized by geologists to infer oxygen conditions in past environments. But there is little information available on Cr in the modern ocean to ground-truth these inferences. Transformations between the two chromium redox species are important processes in oceanic Cr cycling. Here we present profiles of hexavalent and trivalent Cr concentrations and stable isotope ratios from the Eastern Tropical North Pacific (ETNP) oxygen deficient zone (ODZ) which support theoretical and experimental studies that predict that lighter Cr is preferentially reduced in low oxygen environments, and that residual dissolved Cr becomes heavier due to removal of particle-reactive Cr(III) on sinking particles. The Cr(III) maximum dominantly occurs in the upper portion of the ODZ, implying that microbial activity (dependent on the sinking flux of organic matter) may be the dominant mechanism for this transformation, rather than a simple inorganic chemical conversion between the species depending on the redox potential.";
    String title "[Cr concentration and isotope data using dissolved Cr and different Cr species from RR1805] - Chromium (Cr) concentration and isotope data determined using dissolved Cr and different Cr species from samples collected on R/V Roger Revelle cruise RR1805 in April-May 2018 (Cr Isotope Oceanography of the Eastern Tropical North Pacific Ocean)";
    Float64 Westernmost_Easting -107.0;
  }
}

 

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