BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Dissolved Mercury Speciation in the California Current System] - Dissolved mercury (Hg) speciation in the California Current System from samples collected on R/V Roger Revelle cruise RR2105 in July to August 2021 (California Current Ecosystem Long Term Ecological Research site)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_926873_v1)
Range:	longitude = -130.548 to -120.4065°E, depth = 9.59 to 599.456m, time = 2021-07-19T23:00:00Z to 2021-08-09T19:00:00Z
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

)

Time range:

[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 {
  Water_Mass {
    String long_name "Water_mass";
    String units "unitless";
  }
  Station_Name {
    String long_name "Station_name";
    String units "unitless";
  }
  ISO_DateTime_PDT {
    String long_name "Iso_datetime_pdt";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6267356e+9, 1.6285356e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Latitude {
    Float32 actual_range 34.42333, 36.56186;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -130.548, -120.4065;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Trace_Metal_Cast_Num {
    Int32 actual_range 5, 39;
    String long_name "Trace_metal_cast_num";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 9.59, 599.456;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth_m";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Temperature_C {
    Float32 actual_range 5.5118, 18.434;
    String long_name "Temperature_c";
    String units "degrees Celsius";
  }
  Salinity_PSU {
    Float32 actual_range 28.0836, 34.3083;
    String long_name "Salinity_psu";
    String units "practical salinity units (PSU)";
  }
  Oxygen_umol_kg {
    Float32 actual_range 10.45, 306.672;
    String long_name "Oxygen_umol_kg";
    String units "micromole per kilogram (umol/kg)";
  }
  Density_kg_m3 {
    Float32 actual_range 1023.462, 1029.822;
    String long_name "Density_kg_m3";
    String units "kilogram per cubed meter (kg/m^3)";
  }
  DMHg_fM {
    Float32 actual_range 1.57, 461.62;
    String long_name "Dmhg_fm";
    String units "femtomolar (fM)";
  }
  DMHg_Flag {
    Int32 actual_range 0, 1;
    String long_name "Dmhg_flag";
    String units "unitless";
  }
  Hg0_fM {
    Float32 actual_range 6.4, 312.36;
    String long_name "Hg0_fm";
    String units "femtomolar (fM)";
  }
  Hg0_Flag {
    Int32 actual_range 0, 1;
    String long_name "Hg0_flag";
    String units "unitless";
  }
  MMHg_fM {
    Float32 actual_range 11.34, 81.62;
    String long_name "Mmhg_fm";
    String units "femtomolar (fM)";
  }
  MMHg_Flag {
    Int32 actual_range 0, 1;
    String long_name "Mmhg_flag";
    String units "unitless";
  }
  THg_pM {
    Float32 actual_range 0.0895, 2.5597;
    String long_name "Thg_pm";
    String units "picomolar (pM)";
  }
  THg_Flag {
    Int32 actual_range 0, 1;
    String long_name "Thg_flag";
    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.926873.1";
    Float64 Easternmost_Easting -120.4065;
    Float64 geospatial_lon_max -120.4065;
    Float64 geospatial_lon_min -130.548;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 599.456;
    Float64 geospatial_vertical_min 9.59;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-19T15:19:30Z (local files)
2024-11-19T15:19:30Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_926873_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/926873";
    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 "Monomethylmercury (MMHg) is a neurotoxicant that biomagnifies in marine food webs, reaching high concentrations in apex predators. To predict changes in oceanic MMHg concentrations, it is important to quantify its sources and sinks. Here, we study mercury speciation in the California Current System through cruise sampling and modeling. Previous work in the California Current System has found that upwelling impacts mercury biogeochemistry by transporting mercury-enriched deep waters to productive surface waters. These upwelled waters originate within the California Undercurrent water mass and are subsequently advected as a surface water parcel to the California Current. By comparing the two major water masses, we find that the California Undercurrent contains elevated dissolved total mercury (Hg) and Dimethylmercury (DMHg) concentrations by 57% and 60%, respectively, compared to the California Current. We explain that these differences result from losses during advection, specifically scavenging and DMHg demethylation. We calculate a net DMHg demethylation rate constant of 1.8 ± 0.9% per day; and build an empirically constrained mass budget model to demonstrate that DMHg demethylation accounts for 59% of surface MMHg sources. These findings illustrate that DMHg is a significant source of MMHg in this region, challenging the current understanding of the major sources of marine MMHg. These data are associated with Adams et al., 2024 (doi: 10.21203/rs.3.rs-3909481/v1).";
    String time_coverage_end "2021-08-09T19:00:00Z";
    String time_coverage_start "2021-07-19T23:00:00Z";
    String title "[Dissolved Mercury Speciation in the California Current System] - Dissolved mercury (Hg) speciation in the California Current System from samples collected on R/V Roger Revelle cruise RR2105 in July to August 2021 (California Current Ecosystem Long Term Ecological Research site)";
    Float64 Westernmost_Easting -130.548;
  }
}

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