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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GT10-11 - Particulate Po Pb] - Particulate 210Po and 210Pb from R/V Knorr
KN199-04, KN204-01 in the Subtropical northern Atlantic Ocean from 2010-2011 (U.
S. GEOTRACES NAT project) (U.S. GEOTRACES North Atlantic Transect)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3917)
Range: longitude = -69.799 to -9.66°E, latitude = 17.3503 to 39.6994°N, depth = 26.0 to 5485.0m, time = 2010-10-16T10:15:00Z to (now?)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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 {
  cruise_id {
    String bcodmo_name "cruise_id";
    String description "Official cruise identifier e.g. KN199-04 = R/V Knorr cruise number 199-04";
    String long_name "Cruise Id";
    String units "dimensionless";
  }
  cruise_name {
    String bcodmo_name "Cruise Name";
    String description "project designated cruise name";
    String long_name "Cruise Name";
    String units "dimensionless";
  }
  station_GEOTRC {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 20;
    String bcodmo_name "station";
    String description "GEOTRACES station number";
    String long_name "Station GEOTRC";
    String units "dimensionless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range 26.0, 5485.0;
    String axis "Z";
    String bcodmo_name "depth";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "final depth of pump sample. For KN199-4: reported depth is the target depth from wire out. For KN204-1: reported depth is corrected depth using RBR data loggers.";
    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";
  }
  cast_GEOTRC {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 2, 8;
    String bcodmo_name "cast";
    String description "Cast identifier numbered consecutively within a station. Values were added from the intermediate US GEOTRACES master file (see Processing Description).";
    String long_name "Cast GEOTRC";
    String units "dimensionless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 17.3503, 39.6994;
    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 -69.799, -9.66;
    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";
  }
  event_GEOTRC {
    Int16 _FillValue 32767;
    Int16 actual_range 2009, 3229;
    String bcodmo_name "event";
    String description "Unique identifying number for US GEOTRACES sampling events; ranges from 2001 to 2225 for KN199-04 events and from 3001 to 3282 for KN204-01 events. Values were added from the intermediate US GEOTRACES master file (see Processing Description).";
    String long_name "Event GEOTRC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/EVTAGFL/";
    String units "dimensionless";
  }
  sample_GEOTRC {
    Int16 _FillValue 32767;
    Int16 actual_range 5033, 7799;
    String bcodmo_name "sample";
    String description "Unique identifying number for US GEOTRACES samples";
    String long_name "Sample GEOTRC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "dimensionless";
  }
  sample_bottle_GEOTRC {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 8;
    String bcodmo_name "sample";
    String description "Unique identification numbers given to samples taken from bottles; ranges from 1 to 24; often used synonymously with bottle number. Values were added from the intermediate US GEOTRACES master file (see Processing Description).";
    String long_name "Sample Bottle GEOTRC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "dimensionless";
  }
  bottle_GEOTRC {
    String bcodmo_name "bottle";
    String description "Alphanumeric characters identifying bottle type (e.g. NIS representing Niskin and GF representing GOFLO) and position on a CTD rosette. Values were added from the intermediate US GEOTRACES master file (see Processing Description).";
    String long_name "Bottle GEOTRC";
    String units "dimensionless";
  }
  instr {
    String bcodmo_name "instrument";
    String description 
"instrument used for sample collection:
McL-Prof = McLane Profiler;
30-ODF = Ocean Data Facility 12 bottle 30 liter Niskin rosette.";
    String long_name "Instr";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2872241e+9, NaN;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date and time (UTC) variable recorded at the bottle sampling time in ISO compliant format. Values were added from the intermediate US GEOTRACES master file (see Processing Description). This standard is based on ISO 8601:2004(E) and takes on the following form: 2009-08-30T14:05:00[.xx]Z (UTC time)";
    String ioos_category "Time";
    String long_name "BTL 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 units "seconds since 1970-01-01T00:00:00Z";
  }
  Po_210 {
    Float32 _FillValue NaN;
    Float32 actual_range 0.29, 4.978;
    String bcodmo_name "trace_metal_conc";
    String description "particulate Polonium-210 activity";
    String long_name "Po 210";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P03/current/C035/";
    String units "dpm (nuclear decays per minute)/100 kilgrams";
  }
  Po_210_sd {
    Float32 _FillValue NaN;
    Float32 actual_range 0.021, 0.261;
    String bcodmo_name "trace_metal_sd";
    Float64 colorBarMaximum 50.0;
    Float64 colorBarMinimum 0.0;
    String description "particulate Polonium-210 activity error";
    String long_name "Po 210 Sd";
    String units "dpm/100 kilgrams";
  }
  Pb_210 {
    Float32 _FillValue NaN;
    Float32 actual_range 0.195, 6.802;
    String bcodmo_name "trace_metal_conc";
    String description "particulate Lead-210 activity";
    String long_name "PB 210";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P03/current/C035/";
    String units "dpm/100 kilgrams";
  }
  Pb_210_sd {
    Float32 _FillValue NaN;
    Float32 actual_range 0.015, 0.382;
    String bcodmo_name "trace_metal_sd";
    Float64 colorBarMaximum 50.0;
    Float64 colorBarMinimum 0.0;
    String description "particulate Lead-210 activity error";
    String long_name "PB 210 SD";
    String units "dpm/100 kilgrams";
  }
  Po_Pb_ratio {
    Float32 _FillValue NaN;
    Float32 actual_range 0.109, 8.221;
    String bcodmo_name "unknown";
    String description "activity ratio of Polonium to Lead";
    String long_name "Po Pb Ratio";
    String units "dimensionless";
  }
  Po_Pb_ratio_sd {
    Float32 _FillValue NaN;
    Float32 actual_range 0.036, 0.751;
    String bcodmo_name "unknown";
    Float64 colorBarMaximum 50.0;
    Float64 colorBarMinimum 0.0;
    String description "activity ratio of Polonium to Lead error";
    String long_name "Po Pb Ratio Sd";
    String units "dimensionless";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description 
"Currently the recommended assay of both dissolved and particulate seawater
samples are outlined in GEOTRACES procedures manual at:  
[http://www.obs-vlfr.fr/GEOTRACES/science/intercalibration/222-sampling-and-
sample-handling-protocols-for-geotraces-cruises](\\\\\"http://www.obs-
vlfr.fr/GEOTRACES/science/intercalibration/222-sampling-and-sample-handling-
protocols-for-geotraces-cruises\\\\\")  
 It is also published in Baskaran, et al. (2013).";
    String awards_0_award_nid "55174";
    String awards_0_award_number "OCE-0961351";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0961351";
    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 "Donald L. Rice";
    String awards_0_program_manager_nid "51467";
    String cdm_data_type "Other";
    String comment 
"Please note that data may not be final, pending intercalibration results and 
 further analysis. If you are interested in following changes to US GEOTRACES 
 NAT data, there is an RSS feed available via the BCO-DMO US GEOTRACES  
 <a href=\"https://www.bco-dmo.org/project/2066\" target=\"_blank\">project page</a>. 
  
  version: 14 June 2013 
  
  PI: M. Baskaran (Wayne State U) 
  
  Particulate Po-210 and Pb-210 activity from GEOTRACES NAZT cruises";
    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 date_created "2013-04-19T17:59:26Z";
    String date_modified "2020-03-30T19:38:58Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.3917.2";
    Float64 Easternmost_Easting -9.66;
    Float64 geospatial_lat_max 39.6994;
    Float64 geospatial_lat_min 17.3503;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -9.66;
    Float64 geospatial_lon_min -69.799;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 5485.0;
    Float64 geospatial_vertical_min 26.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:48:11Z (local files)
2024-11-08T05:48:11Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_3917.das";
    String infoUrl "https://www.bco-dmo.org/dataset/3917";
    String institution "BCO-DMO";
    String instruments_0_acronym "CTD Sea-Bird";
    String instruments_0_dataset_instrument_description "A self-recording Seabird 19plus CTD, deployed at the end of the line for both cruises.";
    String instruments_0_dataset_instrument_nid "6208";
    String instruments_0_description "Conductivity, Temperature, Depth (CTD) sensor package from SeaBird Electronics, no specific unit identified. This instrument designation is used when specific make and model are not known. See also other SeaBird instruments listed under CTD. More information from Sea-Bird Electronics.";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/130/";
    String instruments_0_instrument_name "CTD Sea-Bird";
    String instruments_0_instrument_nid "447";
    String instruments_0_supplied_name "CTD Sea-Bird";
    String instruments_1_acronym "McLane Pump";
    String instruments_1_dataset_instrument_nid "6143";
    String instruments_1_description "McLane pumps sample large volumes of seawater at depth. They are attached to a wire and lowered to different depths in the ocean. As the water is pumped through the filter, particles suspended in the ocean are collected on the filters. The pumps are then retrieved and the contents of the filters are analyzed in a lab.";
    String instruments_1_instrument_name "McLane Pump";
    String instruments_1_instrument_nid "627";
    String instruments_1_supplied_name "McLane Pump";
    String keywords "bco, bco-dmo, biological, bottle, bottle_GEOTRC, btl, BTL_ISO_DateTime_UTC, cast, cast_GEOTRC, chemical, cruise, cruise_id, cruise_name, data, dataset, date, depth, dmo, erddap, event, event_GEOTRC, geotrc, instr, iso, latitude, longitude, management, name, oceanography, office, Pb_210, Pb_210_sd, Po_210, Po_210_sd, Po_Pb_ratio, Po_Pb_ratio_sd, preliminary, ratio, sample, sample_bottle_GEOTRC, sample_GEOTRC, station, station_GEOTRC, time";
    String license "https://www.bco-dmo.org/dataset/3917/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3917";
    Float64 Northernmost_Northing 39.6994;
    String param_mapping "{'3917': {'lat': 'master - latitude', 'depth': 'flag - depth', 'BTL_ISO_DateTime_UTC': 'flag - time', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3917/parameters";
    String people_0_affiliation "Wayne State University";
    String people_0_affiliation_acronym "WSU";
    String people_0_person_name "Mark Baskaran";
    String people_0_person_nid "51673";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "University of Delaware";
    String people_1_person_name "Thomas M. Church";
    String people_1_person_nid "50676";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Queens College";
    String people_2_affiliation_acronym "CUNY QC";
    String people_2_person_name "Gillian Stewart";
    String people_2_person_nid "51674";
    String people_2_role "Co-Principal Investigator";
    String people_2_role_type "originator";
    String people_3_affiliation "Woods Hole Oceanographic Institution";
    String people_3_affiliation_acronym "WHOI BCO-DMO";
    String people_3_person_name "Nancy Copley";
    String people_3_person_nid "50396";
    String people_3_role "BCO-DMO Data Manager";
    String people_3_role_type "related";
    String project "U.S. GEOTRACES NAT";
    String projects_0_acronym "U.S. GEOTRACES NAT";
    String projects_0_description 
"Much of this text appeared in an article published in OCB News, October 2008, by the OCB Project Office.
The first U.S. GEOTRACES Atlantic Section will be specifically centered around a sampling cruise to be carried out in the North Atlantic in 2010. Ed Boyle (MIT) and Bill Jenkins (WHOI) organized a three-day planning workshop that was held September 22-24, 2008 at the Woods Hole Oceanographic Institution. The main goal of the workshop, sponsored by the National Science Foundation and the U.S. GEOTRACES Scientific Steering Committee, was to design the implementation plan for the first U.S. GEOTRACES Atlantic Section. The primary cruise design motivation was to improve knowledge of the sources, sinks and internal cycling of Trace Elements and their Isotopes (TEIs) by studying their distributions along a section in the North Atlantic (Figure 1). The North Atlantic has the full suite of processes that affect TEIs, including strong meridional advection, boundary scavenging and source effects, aeolian deposition, and the salty Mediterranean Outflow. The North Atlantic is particularly important as it lies at the \"origin\" of the global Meridional Overturning Circulation.
It is well understood that many trace metals play important roles in biogeochemical processes and the carbon cycle, yet very little is known about their large-scale distributions and the regional scale processes that affect them. Recent advances in sampling and analytical techniques, along with advances in our understanding of their roles in enzymatic and catalytic processes in the open ocean provide a natural opportunity to make substantial advances in our understanding of these important elements. Moreover, we are motivated by the prospect of global change and the need to understand the present and future workings of the ocean's biogeochemistry. The GEOTRACES strategy is to measure a broad suite of TEIs to constrain the critical biogeochemical processes that influence their distributions. In addition to these \"exotic\" substances, more traditional properties, including macronutrients (at micromolar and nanomolar levels), CTD, bio-optical parameters, and carbon system characteristics will be measured. The cruise starts at Line W, a repeat hydrographic section southeast of Cape Cod, extends to Bermuda and subsequently through the North Atlantic oligotrophic subtropical gyre, then transects into the African coast in the northern limb of the coastal upwelling region. From there, the cruise goes northward into the Mediterranean outflow. The station locations shown on the map are for the \"fulldepth TEI\" stations, and constitute approximately half of the stations to be ultimately occupied.
Figure 1. The proposed 2010 Atlantic GEOTRACES cruise track plotted on dissolved oxygen at 400 m depth. Data from the World Ocean Atlas (Levitus et al., 2005) were plotted using Ocean Data View (courtesy Reiner Schlitzer). [click on the image to view a larger version]
Hydrography, CTD and nutrient measurements will be supported by the Ocean Data Facility (J. Swift) at Scripps Institution of Oceanography and funded through NSF Facilities. They will be providing an additional CTD rosette system along with nephelometer and LADCP. A trace metal clean Go-Flo Rosette and winch will be provided by the group at Old Dominion University (G. Cutter) along with a towed underway pumping system.
The North Atlantic Transect cruise began in 2010 with KN199 leg 4 (station sampling) and leg 5 (underway sampling only) (Figure 2).
KN199-04 Cruise Report (PDF)
Figure 2. The red line shows the cruise track for the first leg of the US Geotraces North Atlantic Transect on the R/V Knorr in October 2010.  The rest of the stations (beginning with 13) will be completed in October-December 2011 on the R/V Knorr (courtesy of Bill Jenkins, Chief Scientist, GNAT first leg). [click on the image to view a larger version]
The section completion effort resumed again in November 2011 with KN204-01A,B (Figure 3).
KN204-01A,B Cruise Report (PDF)
Figure 3. Station locations occupied on the US Geotraces North Atlantic Transect on the R/V Knorr in November 2011.  [click on the image to view a larger version]
Data from the North Atlantic Transect cruises are available under the Datasets heading below, and consensus values for the SAFe and North Atlantic GEOTRACES Reference Seawater Samples are available from the GEOTRACES Program Office: Standards and Reference Materials
ADCP data are available from the Currents ADCP group at the University of Hawaii at the links below:KN199-04   (leg 1 of 2010 cruise; Lisbon to Cape Verde)KN199-05   (leg 2 of 2010 cruise; Cape Verde to Charleston, NC)KN204-01A (part 1 of 2011 cruise; Woods Hole, MA to Bermuda)KN204-01B (part 2 of 2011 cruise; Bermuda to Cape Verde)";
    String projects_0_end_date "2013-08";
    String projects_0_geolocation "Subtropical western and eastern North Atlantic Ocean";
    String projects_0_name "U.S. GEOTRACES North Atlantic Transect";
    String projects_0_project_nid "2066";
    String projects_0_project_website "https://www.geotraces.org/";
    String projects_0_start_date "2010-10";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 17.3503;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Particulate 210Po and 210Pb from R/V Knorr KN199-04, KN204-01 in the Subtropical northern Atlantic Ocean from 2010-2011.";
    String time_coverage_start "2010-10-16T10:15:00Z";
    String title "[GT10-11 - Particulate Po Pb] - Particulate 210Po and 210Pb from R/V Knorr KN199-04, KN204-01 in the Subtropical northern Atlantic Ocean from 2010-2011 (U.S. GEOTRACES NAT project) (U.S. GEOTRACES North Atlantic Transect)";
    String version "2";
    Float64 Westernmost_Easting -69.799;
    String xml_source "osprey2erddap.update_xml() v1.3";
  }
}

 

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