BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Dissolved organic Fe-binding ligand data from the FRidge (GA13) expedition] - Dissolved organic Fe-binding ligand data from the FRidge (GA13) expedition on RRS James Cook (cruise JC156) from December 2017 to February 2018 (Are strong ligands and dissolved iron tightly coupled in hydrothermal systems?)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_923065_v1)
Range:	longitude = -45.12 to -32.28°E, latitude = 26.03 to 37.29°N, depth = 685.0 to 4452.0m
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Draw land mask:

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

)

Click on the map to specify a new center point.

Zoom:

[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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 26.03, 37.29;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude_deg_n";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -45.12, -32.28;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude_deg_e";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Station {
    Int32 actual_range 8, 38;
    String long_name "Station";
    String units "unitless";
  }
  Geotraces_ID {
    Int32 actual_range 409, 1977;
    String long_name "Geotraces_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 685, 4452;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth_m";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  dFe_nM {
    Float32 actual_range 0.41, 90.25;
    String long_name "Dfe_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L1_nM {
    Float32 actual_range 0.7, 12.8;
    String long_name "L1_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L1_err_nM {
    Float32 actual_range 0.05, 0.47;
    String long_name "L1_err_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L2_nM {
    Float32 actual_range 1.47, 12.6;
    String long_name "L2_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L2_err_nM {
    Float32 actual_range 0.08, 1.59;
    String long_name "L2_err_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L3_nM {
    Float32 actual_range 2.05, 79.7;
    String long_name "L3_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  L3_err_nM {
    Float32 actual_range 0.22, 30.4;
    String long_name "L3_err_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  LT_nM {
    Float32 actual_range 1.3, 80.41;
    String long_name "Lt_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  LT_err_nM {
    Float32 actual_range 0.06, 30.71;
    String long_name "Lt_err_nm";
    String units "nanomoles per liter (nmol L-1)";
  }
  logK1 {
    Float32 actual_range 12.02, 13.42;
    String long_name "Logk1";
    String units "unitless";
  }
  logK1_err {
    Float32 actual_range 0.1, 0.72;
    String long_name "Logk1_err";
    String units "unitless";
  }
  logK2 {
    Float32 actual_range 11.05, 12.0;
    String long_name "Logk2";
    String units "unitless";
  }
  logK2_err {
    Float32 actual_range 0.07, 0.65;
    String long_name "Logk2_err";
    String units "unitless";
  }
  logK3 {
    Float32 actual_range 8.74, 10.97;
    String long_name "Logk3";
    String units "unitless";
  }
  log_K3_err {
    Float32 actual_range 0.04, 0.68;
    String long_name "Log_k3_err";
    String units "unitless";
  }
 }
  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.923065.1";
    Float64 Easternmost_Easting -32.28;
    Float64 geospatial_lat_max 37.29;
    Float64 geospatial_lat_min 26.03;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -32.28;
    Float64 geospatial_lon_min -45.12;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 4452.0;
    Float64 geospatial_vertical_min 685.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:47:44Z (local files)
2024-11-08T05:47:44Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_923065_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/923065";
    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 37.29;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 26.03;
    String summary "Samples were collected as part of the 2017-2018 U.K. GEOTRACES GA13 section cruise along the Mid-Atlantic Ridge (Cruise JC156 on RRS James Cook). Water samples from 11 venting and near venting locations were collected using a Seabird 911 conductivity, temperature, and depth (CTD) titanium rosette using conducting Kevlar wire with an oxidation-reduction potential (ORP) sensor to detect plumes. Teflon coated OTE (Ocean Test Equipment) bottles were pressurized to approximately 7 psi with 0.2 μm filtered air using an oil-free compressor. A Sartobran 300 (Sartorius) filter capsule (0.2 μm) was used to collect filtered seawater samples into clean 250 mL LDPE sample bottles. Bottles and caps were rinsed 3 times with the filtered sample before being filled. Samples were stored frozen at -20°C for organic iron-binding ligand characterization by voltammetry using competitive ligand exchange adsorptive cathodic stripping voltammetry. All dissolved organic iron-binding ligand samples were measured with a BASi controlled growth mercury electrode with an Ag/AgCl¬- reference electrode and platinum auxiliary electrode (Bioanalytical Systems Incorporated) using previously established methods for forward titrations (Buck et al., 2015, 2018; Bundy et al., 2018; Abualhaija and van den Berg, 2014; Hawkes et al., 2013 (Planet. Sci. Lett.)). Reverse titrations (Hawkes et al., 2013 (Anal. Chim. Acta)) were completed on 10 samples from Broken Spur, and TAG hydrothermal vent fields with dissolved iron concentrations between 19.01-90.25 nM.";
    String title "[Dissolved organic Fe-binding ligand data from the FRidge (GA13) expedition] - Dissolved organic Fe-binding ligand data from the FRidge (GA13) expedition on RRS James Cook (cruise JC156) from December 2017 to February 2018 (Are strong ligands and dissolved iron tightly coupled in hydrothermal systems?)";
    Float64 Westernmost_Easting -45.12;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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