BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Atmospheric pO2 data] - SOS-Argo floats: atmospheric pO2 data acquired in different ocean basins between May 2012 and July 2023 (The Biological Pump in the Eastern Equatorial Pacific: in situ measurements of Oxygen and Nitrate)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_915289_v1)
Range:	longitude = -179.99 to 180.0°E
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 {
  Float {
    String long_name "Float";
    String units "unitless";
  }
  Float_Profile {
    Int32 actual_range 1, 318;
    String long_name "Float_profile";
    String units "unitless";
  }
  Matlab_Time {
    String long_name "Matlab_time";
    String units "unitless";
  }
  Excel_Time {
    Int32 actual_range 41063, 45116;
    String long_name "Excel_time";
    String units "unitless";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -179.99, 180.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Latitude {
    Float32 actual_range -59.214, 52.558;
    String long_name "Latitude";
    String units "degrees_north";
  }
  O2_tphase {
    Float32 actual_range -175.9, 212.75;
    String long_name "O2_tphase";
    String units "degrees";
  }
  O2_temp {
    Float32 actual_range -3.033, 35.736;
    String long_name "O2_temp";
    String units "degrees Celsius (C)";
  }
  Matlab_time_HumanReadable {
    String long_name "Matlab_time_humanreadable";
    String units "unitless";
  }
  O2_optode {
    Float32 actual_range -833.55, 3751.1;
    String long_name "O2_optode";
    String units "atmospheres (atm)";
  }
 }
  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.915289.1";
    Float64 Easternmost_Easting 180.0;
    Float64 geospatial_lon_max 180.0;
    Float64 geospatial_lon_min -179.99;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:16:06Z (local files)
2024-11-08T06:16:06Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_915289_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/915289";
    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 contains data from Argo floats deployed by the Emerson group at the University of Washington between May 2012 and July 2023.  

The name SOS-Argo stands for “Special Oxygen Sensor Argo” Floats.  These floats have standard Argo sensors for hydrostatic pressure, temperature, and salinity in addition to an Aanderaa oxygen sensor  (optode) installed on a 61 cm stalk above the end cap of the float.  The tall stalk allows the float to make atmospheric pO2 measurements uncontaminated by surface waters while the float is at the surface during data transfer to shore. The atmospheric pO2 data are used for in situ calibration of the O2 sensor against atmospheric pO2.";
    String title "[Atmospheric pO2 data] - SOS-Argo floats: atmospheric pO2 data acquired in different ocean basins between May 2012 and July 2023 (The Biological Pump in the Eastern Equatorial Pacific: in situ measurements of Oxygen and Nitrate)";
    Float64 Westernmost_Easting -179.99;
  }
}

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