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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Bottle sampling comments associated with the US GEOTRACES North Atlantic
Transect from the R/V Knorr KN204-01 cruise in the subtropical N. Atlantic
during 2011 (U.S. GEOTRACES NAT project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3664)
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 station_GEOTRC (integer) ?          1    24
 cruise_part (text) ?          "A"    "B"
 cast_GEOTRC (integer) ?          1    12
 date (unitless) ?          20111107    20111209
 time2 (Time, HHMMSS) ?          "003145"    "234549"
 time (ISO Date Time UTC, UTC) ?          2011-11-07T03:45:12.00Z    2011-12-09T20:24:07.20Z
  < slider >
 latitude (degrees_north) ?          17.39999    39.70143
  < slider >
 longitude (degrees_east) ?          -69.8644    -24.50004
  < slider >
 type (text) ?          "GT-C"    "SIOR"
 sample_bottle_GEOTRC (integer) ?          1    24
 sample_GEOTRC (integer) ?          -999    8080
 property (text) ?          "bot"    "sio3"
 code (integer) ?          2    9
 who (text) ?          "clog"    "web"
 comments (text) ?          "0013: Salt/niskin..."    "water likely not f..."
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more info)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  station_GEOTRC {
    Byte _FillValue 127;
    Byte actual_range 1, 24;
    String bcodmo_name "station";
    String description "GEOTRACES station number; ranges from 1 through 12 for KN199-04 and 1 through 24 for KN204-01. Stations 7 and 9 were skipped on KN204-01. Originally submitted as 'station', this parameter name has been changed to conform to BCO-DMO's GEOTRACES naming conventions.";
    String long_name "Station GEOTRC";
    String units "integer";
  }
  cruise_part {
    String bcodmo_name "cruise_part";
    String description "Identifier for a segment of a cruise leg, where a leg may have been broken into parts";
    String long_name "Cruise Part";
    String units "text";
  }
  cast_GEOTRC {
    Byte _FillValue 127;
    Byte actual_range 1, 12;
    String bcodmo_name "cast";
    String description "Cast identifier numbered consecutively within a station.  Originally submitted as 'cast_no'; this parameter name has been changed to conform to BCO-DMO's GEOTRACES naming conventions.";
    String long_name "Cast GEOTRC";
    String units "integer";
  }
  date {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20111107, 20111209;
    String bcodmo_name "date";
    String description "Event date in the format YYYYMMDD";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String units "unitless";
  }
  time2 {
    String bcodmo_name "time";
    String description "Event time";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "HHMMSS";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.320637512e+9, 1.3234622472e+9;
    String axis "T";
    String bcodmo_name "ISO_DateTime_UTC";
    String description "Date/Time formatted to ISO 8601 standard. T indicates start of time string; Z indicates UTC. Calculated using 'date' and 'time' parameters as input.";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/DTUT8601/";
    String source_name "ISO_DateTime_UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 17.39999, 39.70143;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Event  Latitude (South is negative)";
    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.8644, -24.50004;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Event Longitude (West is negative)";
    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";
  }
  type {
    String bcodmo_name "cast_type";
    String description "Rosette type (GT-C or ODF/SIOR)";
    String long_name "Type";
    String units "text";
  }
  sample_bottle_GEOTRC {
    Byte _FillValue 127;
    Byte actual_range 1, 24;
    String bcodmo_name "sample";
    String description "Unique identification numbers given to samples taken from bottles; rangies from 1 to 24; often used synonymously with bottle number.  Originally submitted as 'SampNo'; this parameter name has been changed to conform to BCO-DMO's GEOTRACES naming conventions.";
    String long_name "Sample Bottle GEOTRC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "integer";
  }
  sample_GEOTRC {
    Int16 _FillValue 32767;
    Int16 actual_range -999, 8080;
    String bcodmo_name "sample";
    String description "Unique identifying number for US GEOTRACES samples; ranges from 5033 to 6078 for KN199-04 and from 6112 to 8148 for KN204-01. Originally submitted as 'GeoNo', this parameter name has been changed to conform to BCO-DMO's GEOTRACES naming conventions.";
    String long_name "Sample GEOTRC";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P02/current/ACYC/";
    String units "integer";
  }
  property {
    String bcodmo_name "unknown";
    String description "Property sampled";
    String long_name "Property";
    String units "text";
  }
  code {
    Byte _FillValue 127;
    Byte actual_range 2, 9;
    String bcodmo_name "flag";
    String description "Property sampled code";
    String long_name "Code";
    String units "integer";
  }
  who {
    String bcodmo_name "person";
    String description "Person entering comment";
    String long_name "Who";
    String units "text";
  }
  comments {
    String bcodmo_name "comment";
    String description "Bottle sampling comment";
    String long_name "Comments";
    String units "text";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description 
"Refer to [KN204-01 A/B\\u00a0 Cruise
Report](\\\\\"http://bcodata.whoi.edu/US_GEOTRACES/AtlanticSection/STS_Prelim_GT11_Doc.pdf\\\\\")
for detailed descriptions of acquisition and processing methodologies";
    String awards_0_award_nid "54753";
    String awards_0_award_number "OCE-0926423";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0926423";
    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 awards_1_award_nid "54938";
    String awards_1_award_number "OCE-0926092";
    String awards_1_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0926092";
    String awards_1_funder_name "NSF Division of Ocean Sciences";
    String awards_1_funding_acronym "NSF OCE";
    String awards_1_funding_source_nid "355";
    String awards_1_program_manager "Donald L. Rice";
    String awards_1_program_manager_nid "51467";
    String cdm_data_type "Other";
    String comment 
"Version: 05 June 2012 
 PIs: Boyle; et al 
 GT11/KN204-01 parts A and B, Bottle Sampling Comments 
 Change from cruise_id to cruise_part. January 30, 2013";
    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 "2012-06-05T18:09:38Z";
    String date_modified "2020-03-26T18:48:19Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.3664.1";
    Float64 Easternmost_Easting -24.50004;
    Float64 geospatial_lat_max 39.70143;
    Float64 geospatial_lat_min 17.39999;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -24.50004;
    Float64 geospatial_lon_min -69.8644;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-19T08:05:06Z (local files)
2024-03-19T08:05:06Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_3664.html";
    String infoUrl "https://www.bco-dmo.org/dataset/3664";
    String institution "BCO-DMO";
    String instruments_0_acronym "GO-FLO";
    String instruments_0_dataset_instrument_description 
"CTD/Hydrographic Measurements Program
Two types of rosette/SBE9plus CTD casts (65 SIOR/30L-Niskin and 40  GT-C/15L-GoFlo) were made at 22 station locations during GEOTRACES 2011.
13 shallow and 13 deep McLane pump profiles were done at all Full and  Super Stations, with an SBE19plus CTD attached to the end of the wire.";
    String instruments_0_dataset_instrument_nid "5632";
    String instruments_0_description "GO-FLO bottle cast used to collect water samples for pigment, nutrient, plankton, etc. The GO-FLO sampling bottle is specially designed to avoid sample contamination at the surface, internal spring contamination, loss of sample on deck (internal seals), and exchange of water from different depths.";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/30/";
    String instruments_0_instrument_name "GO-FLO Bottle";
    String instruments_0_instrument_nid "411";
    String instruments_0_supplied_name "GO-FLO Bottle";
    String instruments_1_acronym "Niskin bottle";
    String instruments_1_dataset_instrument_description 
"CTD/Hydrographic Measurements Program
Two types of rosette/SBE9plus CTD casts (65 SIOR/30L-Niskin and 40  GT-C/15L-GoFlo) were made at 22 station locations during GEOTRACES 2011.
13 shallow and 13 deep McLane pump profiles were done at all Full and  Super Stations, with an SBE19plus CTD attached to the end of the wire.";
    String instruments_1_dataset_instrument_nid "5631";
    String instruments_1_description "A Niskin bottle (a next generation water sampler based on the Nansen bottle) is a cylindrical, non-metallic water collection device with stoppers at both ends.  The bottles can be attached individually on a hydrowire or deployed in 12, 24 or 36 bottle Rosette systems mounted on a frame and combined with a CTD.  Niskin bottles are used to collect discrete water samples for a range of measurements including pigments, nutrients, plankton, etc.";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0412/";
    String instruments_1_instrument_name "Niskin bottle";
    String instruments_1_instrument_nid "413";
    String instruments_1_supplied_name "Niskin bottle";
    String instruments_2_acronym "CTD SBE 911plus";
    String instruments_2_dataset_instrument_description 
"CTD/Hydrographic Measurements Program
Two types of rosette/SBE9plus CTD casts (65 SIOR/30L-Niskin and 40  GT-C/15L-GoFlo) were made at 22 station locations during GEOTRACES 2011.
13 shallow and 13 deep McLane pump profiles were done at all Full and  Super Stations, with an SBE19plus CTD attached to the end of the wire.";
    String instruments_2_dataset_instrument_nid "5633";
    String instruments_2_description "The Sea-Bird SBE 911plus is a type of CTD instrument package for continuous measurement of conductivity, temperature and pressure.  The SBE 911plus includes the SBE 9plus Underwater Unit and the SBE 11plus Deck Unit (for real-time readout using conductive wire) for deployment from a vessel. The combination of the SBE 9plus and SBE 11plus is called a SBE 911plus.  The SBE 9plus uses Sea-Bird's standard modular temperature and conductivity sensors (SBE 3plus and SBE 4). The SBE 9plus CTD can be configured with up to eight auxiliary sensors to measure other parameters including dissolved oxygen, pH, turbidity, fluorescence, light (PAR), light transmission, etc.). more information from Sea-Bird Electronics";
    String instruments_2_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0058/";
    String instruments_2_instrument_name "CTD Sea-Bird SBE 911plus";
    String instruments_2_instrument_nid "591";
    String instruments_2_supplied_name "CTD Sea-Bird SBE 911plus";
    String keywords "bco, bco-dmo, biological, bottle, cast, cast_GEOTRC, chemical, code, comments, cruise, cruise_part, data, dataset, date, dmo, erddap, geotrc, iso, latitude, longitude, management, oceanography, office, part, preliminary, property, sample, sample_bottle_GEOTRC, sample_GEOTRC, station, station_GEOTRC, time, time2, type, who";
    String license "https://www.bco-dmo.org/dataset/3664/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3664";
    Float64 Northernmost_Northing 39.70143;
    String param_mapping "{'3664': {'lat': 'flag - latitude', 'lon': 'flag - longitude', 'ISO_DateTime_UTC': 'master - time'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3664/parameters";
    String people_0_affiliation "Massachusetts Institute of Technology";
    String people_0_affiliation_acronym "MIT";
    String people_0_person_name "Edward A. Boyle";
    String people_0_person_nid "50984";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Massachusetts Institute of Technology";
    String people_1_affiliation_acronym "MIT";
    String people_1_person_name "Edward A. Boyle";
    String people_1_person_nid "50984";
    String people_1_role "Contact";
    String people_1_role_type "related";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Stephen R. Gegg";
    String people_2_person_nid "50910";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_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 "http://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.39999;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Bottle sampling comments associated with the US GEOTRACES North Atlantic Transect from the R/V Knorr KN204-01 cruise in the subtropical N. Atlantic during 2011 (U.S. GEOTRACES NAT project)";
    String time_coverage_end "2011-12-09T20:24:07.20Z";
    String time_coverage_start "2011-11-07T03:45:12.00Z";
    String title "Bottle sampling comments associated with the US GEOTRACES North Atlantic Transect from the R/V Knorr KN204-01 cruise in the subtropical N. Atlantic during 2011 (U.S. GEOTRACES NAT project)";
    String version "1";
    Float64 Westernmost_Easting -69.8644;
    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.02
Disclaimers | Privacy Policy | Contact