BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Table 2: Suspended particulate matter (SPM) concentrations in lake water Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_809857)
Range: longitude = -87.90352 to -87.90352°E, latitude = 43.017834 to 43.017834°N, depth = 2.0 to 2.0m, time = 2018-11-08T15:43:00Z to 2018-11-20T16:09:00Z
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.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: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  sample {
    String bcodmo_name "sample";
    String description "sample identifier";
    String long_name "Sample";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "unitless";
  }
  ISO_DateTime_Local {
    String bcodmo_name "ISO_DateTime_Local";
    String description "sample collection local date and time; ISO formatted yyyy-mm-ddTHH:MM:SS (UTC- 6 hr)";
    String long_name "ISO Date Time Local";
    String source_name "ISO_DateTime_Local";
    String time_precision "1970-01-01T00:00Z";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.54169178e+9, 1.54273014e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "sample collection date and time; ISO formatted yyyy-mm-ddTHH:MM:SSZ (converted to UTC from local: UTC- 6 hr)";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DTUT8601/";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 43.017835, 43.017835;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude; north is positive";
    String ioos_category "Location";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -87.903521, -87.903521;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude; east is positive";
    String ioos_category "Location";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range 2.0, 2.0;
    String axis "Z";
    String bcodmo_name "depth";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "sample depth";
    String ioos_category "Location";
    String long_name "Depth";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/DEPH/";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  SPM_b {
    Float32 _FillValue NaN;
    Float32 actual_range 0.64, 3.62;
    String bcodmo_name "SPM";
    String description "suspended particulate matter (>0.45 microns)";
    String long_name "SPM B";
    String units "grams/meter^3 (g m-3)";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description 
"A detailed description of the methods for determining in situ 210Pb, 210Bi,
and 210Po activities is given by Waples (2020).
 
A second manuscript describing the use of Pb-210, Bi-210, and Po-210 as
particle tracers in aquatic systems is currently in review for Limnology and
Oceanography (March/2020).
 
Lake water samples (~ 50 L) for radionuclide analyses were collected from the
slip (43.017835, -87.903521) with a submersible pump from a depth of 2 m on 08
November, 15 November, and 20 November 2018.
 
Water samples collected by submersible pump were weighed and filtered through
nitrocellulose filters (0.45 um, 293 mm, Millipore) within two hours of sample
collection to separate dissolved and particle-bound nuclide fractions of
210Pb, 210Bi, and 210Po. Yield monitors of 207Bi and 209Po (Eckert & Ziegler
Isotope Products) were then added to both fractions. No lead monitor was
required. Dissolved nuclide fractions (< 0.45 um) of 210Pb, 210Bi, and 210Po
were co-precipitated onto newly formed ferric hydroxide and collected by
filtration. Both particle-bound and dissolved nuclide fractions were then
digested in concentrated nitric acid. Bismuth and polonium were completely
separated from lead on EmporeTM anion solid phase extraction (SPE) disks (3M,
47 mm, product number 2252, now manufactured by CDS Analytical). Eluate from
the particle-bound fraction was re-spiked with 207Bi and set aside for ~one
month for the determination of particle-bound 210Pb (via 210Bi in secular
equilibrium with its parent). Anion SPE disks were then counted\\u2013 first
for 210Bi via b-decay on a low background gas-flow proportional detector with
anticoincidence circuitry (G542 System, Gamma Products), then for 207Bi via
g-emission to determine yield. Polonium was then removed from the SPE disks,
plated to copper, and a-counted for 210Po and the yield monitor 209Po. Total
210Pb was determined in a separate water sample via 210Bi that had grown into
secular equilibrium with its parent. Activity calculations including
uncertainty propagation and decay corrections are all fully described by
Waples (2020).
 
Lake water samples (~ 50 L) for radionuclide analyses were collected from the
slip (43.017835, -87.903521) with a submersible pump from a depth of 2 m on 08
November, 15 November, and 20 November 2018.
 
Software used:  
 - Maestro software (v. 6.04 and 6.06, Advanced Measurement Technology)  
 - SigmaPlot (v. 11, Systat Software)  
 - Excel (v. 2002, Microsoft)";
    String awards_0_award_nid "806356";
    String awards_0_award_number "OCE-1639865";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1639865";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "Henrietta N Edmonds";
    String awards_0_program_manager_nid "51517";
    String cdm_data_type "Other";
    String comment 
"Table 2. Suspended particulate matter (SPM) concentrations in lake water  
   Lake Michigan, Nov. 2018 
   PI: J. Waples (UW-Milwaukee) 
   version date: 2020-04-22";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.3  19 Dec 2019";
    String dataset_current_state "Final and no updates";
    String date_created "2020-04-22T20:49:57Z";
    String date_modified "2020-05-20T12:28:18Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.809857.1";
    Float64 Easternmost_Easting -87.903521;
    Float64 geospatial_lat_max 43.017835;
    Float64 geospatial_lat_min 43.017835;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -87.903521;
    Float64 geospatial_lon_min -87.903521;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 2.0;
    Float64 geospatial_vertical_min 2.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-04-18T23:57:57Z (local files)
2024-04-18T23:57:57Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_809857.das";
    String infoUrl "https://www.bco-dmo.org/dataset/809857";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, date, depth, dmo, erddap, iso, ISO_DateTime_UTC, latitude, local, longitude, management, oceanography, office, preliminary, sample, spm, SPM_b, time";
    String license "https://www.bco-dmo.org/dataset/809857/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/809857";
    Float64 Northernmost_Northing 43.017835;
    String param_mapping "{'809857': {'latitude': 'flag - latitude', 'depth': 'flag - depth', 'longitude': 'flag - longitude', 'ISO_DateTime_UTC': 'flag - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/809857/parameters";
    String people_0_affiliation "University of Wisconsin";
    String people_0_affiliation_acronym "UW-Milwaukee";
    String people_0_person_name "James T. Waples";
    String people_0_person_nid "806359";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Woods Hole Oceanographic Institution";
    String people_1_affiliation_acronym "WHOI BCO-DMO";
    String people_1_person_name "Nancy Copley";
    String people_1_person_nid "50396";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "Bi 210 measurement";
    String projects_0_acronym "Bi 210 measurement";
    String projects_0_description 
"Naturally occurring radioactive nuclides provide invaluable \"clocks\" with which to investigate a wide range of processes in earth and environmental sciences. Nuclides with shorter half-lives are well suited to studying rapid processes, but are often present at very low concentrations and are particularly difficult to measure. The goal of this Early Concept Grant for Exploratory Research (EAGER) is to develop and demonstrate a new analytical method for measuring bismuth-210 (half life, 5 days) in lake water, seawater, and associated particles. Because bismuth tends to become associated with particles more than its parent isotope lead-210 (half life, 22 years), the bismuth-210/lead-210 daughter/parent pair can potentially be used to investigate very short time-scale processes associated with particle (sediment) formation and cycling in lakes and the coastal ocean. Knowledge about such processes is important to understanding carbon and nutrient cycling in these productive and dynamic areas.
The specific goals of this exploratory project are to 1) demonstrate an improved method for measuring the lead-210/bismuth-210/polonium-210 trio in aquatic system samples; 2) measure lead-210/bismuth-210/polonium-210 in Lake Michigan; and 3) explore the feasibility of using bismuth-210/lead-210 disequilibrium as a proxy for particle flux. The project would support an undergraduate student researcher for the summer.";
    String projects_0_end_date "2019-06";
    String projects_0_geolocation "Lake Michigan 43.0 N 87.9 W";
    String projects_0_name "The measurement and use of bismuth-210 as a tracer of particle flux in aquatic systems";
    String projects_0_project_nid "806357";
    String projects_0_start_date "2016-07";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.017835;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "latitude,longitude,depth";
    String summary "Table 2. Suspended particulate matter (SPM) concentrations in lake water, Lake Michigan, Nov. 2018";
    String time_coverage_end "2018-11-20T16:09:00Z";
    String time_coverage_start "2018-11-08T15:43:00Z";
    String title "Table 2: Suspended particulate matter (SPM) concentrations in lake water";
    String version "1";
    Float64 Westernmost_Easting -87.903521;
    String xml_source "osprey2erddap.update_xml() v1.5";
  }
}

 

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.

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.02
Disclaimers | Privacy Policy | Contact