BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[IUE of marine AOA under different temp and FE] - Iron use efficiency (IUE) of the model marine ammonia-oxidizing archaea (AOA), Nitrosopumilus maritimus, under controlled laboratory conditions across a range of temperatures and iron concentrations (Collaborative Research: The impact of ocean warming on bioactive trace metal requirements and use efficiencies of marine nitrifying microorganisms)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_1005573_v1)
Information:	Summary \| License \| 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:

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:

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 {
  Condition {
    String long_name "Condition";
    String units "unitless";
  }
  total_iron_concentration {
    Float32 actual_range 250.0, 1250.0;
    String long_name "Total_iron_concentration";
    String units "nanomole per liter (nM)";
  }
  Temperature {
    Float32 actual_range 23.0, 32.0;
    String long_name "Temperature";
    String units "degrees Celsius (°C)";
  }
  POC {
    Float32 actual_range 6.937911, 42.23716;
    String long_name "Poc";
    String units "micromole carbon per liter (μmol C L⁻¹)";
  }
  POC_std {
    Float32 actual_range 0.3982173, 4.123577;
    String long_name "Poc_std";
    String units "micromole carbon per liter (μmol C L⁻¹)";
  }
  Fe {
    Float32 actual_range 4.970169, 32.57187;
    String long_name "Fe";
    String units "nanomole per liter (nM)";
  }
  Fe_std {
    Float32 actual_range 0.2046685, 4.539876;
    String long_name "Fe_std";
    String units "nanomole per liter (nM)";
  }
  Fe_C_ratio {
    Float32 actual_range 196.6265, 1629.901;
    String long_name "Fe_c_ratio";
    String units "micromole per mole (μmol mol⁻¹)";
  }
  Fe_C_ratio_std {
    Float32 actual_range 39.63115, 434.4839;
    String long_name "Fe_c_ratio_std";
    String units "micromole per mole (μmol mol⁻¹)";
  }
  Carbon_fixation {
    Float32 actual_range 0.6162478, 38.78683;
    String long_name "Carbon_fixation";
    String units "micromole carbon per liter per day (μmol C L⁻¹ d⁻¹)";
  }
  Carbon_fixation_std {
    Float32 actual_range 0.2243485, 1.271145;
    String long_name "Carbon_fixation_std";
    String units "micromole carbon per liter per day (μmol C L⁻¹ d⁻¹)";
  }
  iron_use_efficiency {
    Float32 actual_range 5.27038, 67.75703;
    String long_name "Iron_use_efficiency";
    String units "micromole carbon per hour per micromole iron (μmol C h⁻¹ μmol Fe⁻¹)";
  }
  iron_use_efficiency_std {
    Float32 actual_range 0.4163427, 12.08571;
    String long_name "Iron_use_efficiency_std";
    String units "micromole carbon per hour per micromole iron (μmol C h⁻¹ μmol Fe⁻¹)";
  }
  Replicates {
    Int32 actual_range 3, 3;
    String long_name "Replicates";
    String units "count";
  }
 }
  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.1005573.1";
    String history 
"2026-09-20T03:58:12Z (local files)
2026-09-20T03:58:12Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_1005573_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/1005573";
    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 "This dataset quantifies iron use efficiency (IUE) of the model marine ammonia-oxidizing archaea, Nitrosopumilus maritimus, under controlled laboratory conditions across a range of temperatures (23, 27, and 32 degrees Celsius) and iron concentrations (iron-replete, 1250 nM; iron-limited, 250 nM). Measurements include carbon fixation rates derived from 14C-bicarbonate incorporation assays and cellular iron quotas determined by inductively coupled plasma mass spectrometry (ICP-MS), from which IUE was calculated. Experiments were conducted in batch cultures with biological replicates for each treatment to assess the interactive effects of temperature and iron limitation on AOA physiology.";
    String title "[IUE of marine AOA under different temp and FE] - Iron use efficiency (IUE) of the model marine ammonia-oxidizing archaea (AOA), Nitrosopumilus maritimus, under controlled laboratory conditions across a range of temperatures and iron concentrations (Collaborative Research: The impact of ocean warming on bioactive trace metal requirements and use efficiencies of marine nitrifying microorganisms)";
  }
}

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