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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Total dissolved Cr concentration and isotopic composition in the ETNP from
RR1804-05 and KM1919-20] - Total dissolved chromium (Cr) concentration and
isotopic composition in the Eastern Tropical North Pacific from samples
collected on R/V Roger Revelle and R/V Kilo Moana in April-May 2018 and Sept-
Oct 2019 (Cr Isotope Oceanography of the Eastern Tropical North Pacific Ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_925726_v1)
Range: longitude = -115.2 to -105.7°E, depth = 6.0 to 3500.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 15.1, 27.1;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -115.2, -105.7;
    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 6, 3500;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  CTD_Oxygen {
    Float32 actual_range 0.63, 231.18;
    String long_name "Ctd_oxygen";
    String units "micromoles per kilogram (umol/kg)";
  }
  total_dissolved_Cr {
    Float32 actual_range 2.26, 5.02;
    String long_name "Total_dissolved_cr";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  total_dissolved_d53Cr {
    Float32 actual_range 0.6, 1.85;
    String long_name "Total_dissolved_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.925726.1";
    Float64 Easternmost_Easting -105.7;
    Float64 geospatial_lon_max -105.7;
    Float64 geospatial_lon_min -115.2;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 3500.0;
    Float64 geospatial_vertical_min 6.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T15:55:47Z (local files)
2024-11-08T15:55:47Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_925726_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/925726";
    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 
"Understanding the cycling of chromium (Cr) and how chromium stable isotopes (δ53Cr) are altered in response to different processes in the modern ocean is important in our interpretation of marine sedimentary δ53Cr records, a promising redox proxy. Therefore, it is crucial to investigate the geochemical processes of Cr in reducing environments such as oxygen deficient zones (ODZs). In this study, we investigated the cycling of Cr in the Eastern Tropical North Pacific (ETNP) ODZ by analyzing the [Cr] and δ53Cr of total dissolved Cr and Cr(III). Our Cr(III) data at two inshore stations shows profile features and Cr reduction isotopic fractionation factor (-1.5‰) similar to an offshore station in a previous study. We also observed significant Cr scavenging signals in the upper 1000 meters (m) throughout the ODZ with an inshore-offshore variability in its magnitude. Specifically, anoxic bottom waters on the continental slope see the greatest Cr scavenging with heaviest δ53Cr (+1.85‰). Our estimates of the scavenged Cr isotopic composition are within error of the anoxic and euxinic marine sedimentary δ53Cr. This implies that the vertical transport of Cr to the seafloor and subsequent diagenesis may not generate significant isotopic fractionation for Cr. This is the first thorough investigation into the Cr cycling in the ETNP ODZ and demonstrated promising usage of marine sedimentary δ53Cr as a redox proxy for ancient oceans.

In the ODZ, oxygen is consumed by degrading sinking particles and reaches extremely low levels (too low to support aerobic life) from 100m to 800m depth. However, microbes that can use other oxidants such as nitrate to metabolize organic carbon live there, and we showed that they also convert soluble anionic chromate Cr(VI) to cationic Cr(III), about half of which is scavenged onto sinking particles and removed to the seafloor. This reduction is accompanied by preferential reduction of light Cr isotopes, so the Cr(III) is 1.3‰ lighter than the source Cr(VI). The removal of part of this light Cr(III) by scavenging leaves the residual total Cr heavier than the source Cr. The analyzed samples listed here were chosen to be from the center and margins of the ETNP ODZ and over extremely reducing continental margin sediments.";
    String title "[Total dissolved Cr concentration and isotopic composition in the ETNP from RR1804-05 and KM1919-20] - Total dissolved chromium (Cr) concentration and isotopic composition in the Eastern Tropical North Pacific from samples collected on R/V Roger Revelle and R/V Kilo Moana in April-May 2018 and Sept-Oct 2019 (Cr Isotope Oceanography of the Eastern Tropical North Pacific Ocean)";
    Float64 Westernmost_Easting -115.2;
  }
}

 

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