BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[CliOMZ AT50-10 Underway Sampling Log] - Log for the samples taken using the Underway system on board of the R/V Atlantis during the CliOMZ AT50-10 expedition from Golfito, Costa Rica to San Diego, USA that occurred in May - June of 2023. (Collaborative Research: Underexplored Connections between Nitrogen and Trace Metal Cycling in Oxygen Minimum Zones Mediated by Metalloenzyme Inventories)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_922268_v1)
Range:	depth = 5.0 to 5.0m
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 {
  Cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Station_number {
    String long_name "Station_number";
    String units "unitless";
  }
  Start_Date_UTC {
    String long_name "Start_date_utc";
    String units "UTC";
  }
  Start_Time_UTC {
    String long_name "Start_time_utc";
    String units "UTC";
  }
  End_Date_UTC {
    String long_name "End_date_utc";
    String units "UTC";
  }
  End_Time_UTC {
    String long_name "End_time_utc";
    String units "UTC";
  }
  Start_Lat {
    Float32 actual_range -10.06429, 31.25079;
    String long_name "Start_lat";
    String units "decimal degrees";
  }
  Start_Long {
    Float32 actual_range -120.2789, -88.97095;
    String long_name "Start_long";
    String units "decimal degrees";
  }
  End_Lat {
    Float32 actual_range -10.06429, 31.25079;
    String long_name "End_lat";
    String units "decimal degrees";
  }
  End_Long {
    Float32 actual_range -120.2789, -88.97095;
    String long_name "End_long";
    String units "decimal degrees";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 5.0, 5.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Sampling_device {
    String long_name "Sampling_device";
    String units "unitless";
  }
  At_station_or_transit {
    String long_name "At_station_or_transit";
    String units "unitless";
  }
  Filter_type {
    String long_name "Filter_type";
    String units "unitless";
  }
  Volume_filtered {
    Float32 actual_range 4.542492, 652.8;
    String long_name "Volume_filtered";
    String units "liters (L)";
  }
  DEPLOYMENT_COMMENTS {
    String long_name "Deployment_comments";
    String units "unitless";
  }
  SAMPLE_PRFEIX {
    String long_name "Sample_prfeix";
    String units "unitless";
  }
  SUPOR_0_2_PROTEIN1 {
    Float32 actual_range 0.5, 0.5;
    String long_name "Supor_0_2_protein1";
    String units "unitless";
  }
  SUPOR_0_2_PROTEIN2 {
    Float32 actual_range 0.125, 0.125;
    String long_name "Supor_0_2_protein2";
    String units "unitless";
  }
  SUPOR_0_2_DNA1 {
    Float32 actual_range 0.125, 0.125;
    String long_name "Supor_0_2_dna1";
    String units "unitless";
  }
  SUPOR_0_2_DNA2 {
    Float32 actual_range 0.0625, 0.125;
    String long_name "Supor_0_2_dna2";
    String units "unitless";
  }
  SUPOR_0_2_eDNA {
    Float32 actual_range 0.0625, 0.0625;
    String long_name "Supor_0_2_edna";
    String units "unitless";
  }
  SUPOR_0_2_pMetal {
    String long_name "Supor_0_2_pmetal";
    String units "unitless";
  }
  SUPOR_0_2_POS {
    Float32 actual_range 0.125, 0.125;
    String long_name "Supor_0_2_pos";
    String units "unitless";
  }
  NITEX_51_PROTEIN1 {
    Float32 actual_range 0.75, 0.75;
    String long_name "Nitex_51_protein1";
    String units "unitless";
  }
  NITEX_51_DNA1 {
    Float32 actual_range 0.125, 0.125;
    String long_name "Nitex_51_dna1";
    String units "unitless";
  }
  NITEX_51_pMetal {
    Float32 actual_range 0.13, 0.13;
    String long_name "Nitex_51_pmetal";
    String units "unitless";
  }
  GFF_PROTEIN1 {
    Float32 actual_range 0.25, 0.25;
    String long_name "Gff_protein1";
    String units "unitless";
  }
  GFF_CA {
    Float32 actual_range 0.125, 0.125;
    String long_name "Gff_ca";
    String units "unitless";
  }
  GFF_PIGS {
    Float32 actual_range 0.05, 0.05;
    String long_name "Gff_pigs";
    String units "unitless";
  }
  GFF_POC {
    Float32 actual_range 0.05, 0.05;
    String long_name "Gff_poc";
    String units "unitless";
  }
  GFF_HG {
    Float32 actual_range 0.525, 0.525;
    String long_name "Gff_hg";
    String units "unitless";
  }
  SAMPLE_COMMENTS {
    String long_name "Sample_comments";
    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.922268.1";
    Float64 geospatial_vertical_max 5.0;
    Float64 geospatial_vertical_min 5.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:42:55Z (local files)
2024-11-08T05:42:55Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_922268_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/922268";
    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 is the log for the samples taken using the Underway system on board of the R/V Atlantis during the CliOMZ AT50-10 expedition from Golfito, Costa Rica to San Diego, USA that occurred in May - June of 2023.  The log contains metadata associated with the locations where samples were collected, including coordinates, depth, time, volume filtered, filter type, and subsamples' fractions. A Geotech in-line acrylic filter holder connected to a flowmeter were attached to the Underway water flow and particulates were collected. The Science party included members from WHOI, UCSB, UTGRV, and Clark University";
    String title "[CliOMZ AT50-10 Underway Sampling Log] - Log for the samples taken using the Underway system on board of the R/V Atlantis during the CliOMZ AT50-10 expedition from Golfito, Costa Rica to San Diego, USA that occurred in May - June of 2023. (Collaborative Research: Underexplored Connections between Nitrogen and Trace Metal Cycling in Oxygen Minimum Zones Mediated by Metalloenzyme Inventories)";
  }
}

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