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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD data from ARSV Laurence M. Gould LMG1110 in the Southern Ocean from
November to December 2011 (Salp_Antarctic project)
  RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_559174)
Range: longitude = -68.8352 to -53.5638°E, latitude = -65.0817 to -60.735°N, time = 2011-11-09T18:19:37Z to 2011-11-25T20:36:57Z
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() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
  station_std {
    Byte _FillValue 127;
    Byte actual_range 3, 28;
    String description "standard station numbers (as opposed to consecutive station numbers)";
    String ioos_category "Unknown";
    String long_name "Station Std";
    String units "number";
  }
  cast {
    String description "CTD cast number";
    String ioos_category "Unknown";
    String long_name "Cast";
    String units "number";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range -65.0817, -60.735;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude at the start of the cast";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -68.8352, -53.5638;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude at the start of the cast";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  day_gmt {
    String description "day of the month in Greenwich Mean Time (a.k.a.UTC)";
    String ioos_category "Time";
    String long_name "Day Gmt";
    String units "two digit day";
  }
  month_gmt {
    Byte _FillValue 127;
    Byte actual_range 11, 11;
    String description "month of the year in Greenwich Mean Time (a.k.a.UTC)";
    String ioos_category "Time";
    String long_name "Month Gmt";
    String units "two digit month";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2011, 2011;
    String description "year";
    String ioos_category "Time";
    String long_name "Year";
    String units "four digit year";
  }
  time_start_gmt {
    String description "time at the start of the cast: \"NMEA UTC (Time)\"";
    String ioos_category "Time";
    String long_name "Time Start Gmt";
    String units "HH:MM:SS";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.3208627772e+9, 1.322253417e+9;
    String axis "T";
    String description "ISO 8601 standard date and time";
    String ioos_category "Time";
    String long_name "ISO Date Time UTC";
    String source_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";
  }
  press {
    Float64 _FillValue NaN;
    Float64 actual_range 1.01, 1040.706;
    String description "water pressure at the point of data collection; can be considered depth within certain conditions";
    String ioos_category "Unknown";
    String long_name "Press";
    String units "decibars";
  }
  depth_w {
    Float32 _FillValue NaN;
    Float32 actual_range 1.0, 1028.0;
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "water depth at the data collection point";
    String ioos_category "Location";
    String long_name "Depth";
    String standard_name "depth";
    String units "meters";
  }
  temp {
    Float32 _FillValue NaN;
    Float32 actual_range -1.5671, 7.8363;
    String description "water temperature [ITS-90] from primary sensor";
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degrees C";
  }
  temp_2 {
    Float32 _FillValue NaN;
    Float32 actual_range -1.5679, 8.053;
    String description "water temperature [ITS-90] from secondary sensor";
    String ioos_category "Unknown";
    String long_name "Temp 2";
    String units "degrees C";
  }
  temp_diff {
    Float32 _FillValue NaN;
    Float32 actual_range -3.0284, 1.0407;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String description "temperature difference; secondary sensor - primary sensor";
    String ioos_category "Unknown";
    String long_name "Temp Diff";
    String units "degrees C";
  }
  cond {
    Float64 _FillValue NaN;
    Float64 actual_range 15.834489, 33.087143;
    String description "conductivity from primary sensor";
    String ioos_category "Unknown";
    String long_name "Cond";
    String units "milliSiemens per centimeter [mS/cm]";
  }
  cond_2 {
    Float64 _FillValue NaN;
    Float64 actual_range 15.100734, 33.790085;
    String description "conductivity from secondary sensor";
    String ioos_category "Unknown";
    String long_name "Cond 2";
    String units "milliSiemens per centimeter [mS/cm]";
  }
  O2_um_Kg {
    Float32 _FillValue NaN;
    Float32 actual_range 244.873, 599.509;
    String description "dissolved oxygen from primary CTD sensor";
    String ioos_category "Dissolved O2";
    String long_name "O2 Um Kg";
    String units "micromoles per Kilogram";
  }
  O2_ml_L {
    Float32 _FillValue NaN;
    Float32 actual_range 5.63472, 13.81129;
    String description "dissolved oxygen from primary CTD sensor";
    String ioos_category "Dissolved O2";
    String long_name "O2 Ml L";
    String units "milliliters per Liter";
  }
  O2_um_Kg_2 {
    Float32 _FillValue NaN;
    Float32 actual_range 98.217, 351.287;
    String description "dissolved oxygen from secondary CTD sensor";
    String ioos_category "Dissolved O2";
    String long_name "O2 Um Kg 2";
    String units "micromoles per Kilogram";
  }
  O2_ml_L_2 {
    Float32 _FillValue NaN;
    Float32 actual_range 2.26008, 8.09029;
    String description "dissolved oxygen from secondary CTD sensor";
    String ioos_category "Dissolved O2";
    String long_name "O2 Ml L 2";
    String units "milliliters per Liter";
  }
  fluor {
    Float32 _FillValue NaN;
    Float32 actual_range -0.0231, 3.0772;
    String description "fluorescence";
    String ioos_category "Optical Properties";
    String long_name "Fluor";
    String units "milligrams per cubic meter";
  }
  lat {
    Float32 _FillValue NaN;
    Float32 actual_range -65.08196, -60.73464;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "decimal degrees; negative = South";
  }
  lon {
    Float32 _FillValue NaN;
    Float32 actual_range -68.83512, -53.56455;
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "decimal degrees; negative = West";
  }
  sal_diff {
    Float32 _FillValue NaN;
    Float32 actual_range -11.7726, 21.1231;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String description "practical salinity difference; secondary sensor - primary sensor";
    String ioos_category "Unknown";
    String long_name "Sal Diff";
    String units "PSU";
  }
  cond_diff {
    Float64 _FillValue NaN;
    Float64 actual_range -11.651454, 17.052977;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String description "conductivity difference; secondary sensor - primary sensor";
    String ioos_category "Unknown";
    String long_name "Cond Diff";
    String units "milliSiemens per centimeter [mS/cm]";
  }
  sigma_t {
    Float32 _FillValue NaN;
    Float32 actual_range 12.4834, 32.2583;
    String description "water density from primary sensors";
    String ioos_category "Unknown";
    String long_name "Sigma T";
    String units "kilograms per cubic meter - 1000";
  }
  density_2 {
    Float64 _FillValue NaN;
    Float64 actual_range 1011.5131, 1032.6941;
    String description "water density from secondary sensors";
    String ioos_category "Physical Oceanography";
    String long_name "Density 2";
    String units "kilograms per cubic meter";
  }
  potemp {
    Float32 _FillValue NaN;
    Float32 actual_range -1.5684, 7.8361;
    String description "Potential Temperature [ITS-90] from primary sensors";
    String ioos_category "Unknown";
    String long_name "Potemp";
    String units "degrees C";
  }
  potemp_2 {
    Float32 _FillValue NaN;
    Float32 actual_range -1.5692, 8.0529;
    String description "Potential Temperature [ITS-90] from secondary sensors";
    String ioos_category "Unknown";
    String long_name "Potemp 2";
    String units "degrees C";
  }
  sound_vel {
    Float32 _FillValue NaN;
    Float32 actual_range 1438.96, 1477.88;
    String description "sound velocity [using Chen-Millero equation]";
    String ioos_category "Currents";
    String long_name "Sound Vel";
    String units "meters per second";
  }
  sal {
    Float32 _FillValue NaN;
    Float32 actual_range 15.9189, 40.1594;
    String description "salinity from primary sensor";
    String ioos_category "Unknown";
    String long_name "Sal";
    String units "practical salinity units (PSU)";
  }
  sal_2 {
    Float32 _FillValue NaN;
    Float32 actual_range 14.5748, 40.6746;
    String description "salinity from secondary sensor";
    String ioos_category "Unknown";
    String long_name "Sal 2";
    String units "practical salinity units (PSU)";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson,.odvTxt";
    String acquisition_description "\"\"";
    String awards_0_award_nid "54892";
    String awards_0_award_number "ANT-1044982";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1044982";
    String awards_0_funder_name "NSF Antarctic Sciences";
    String awards_0_funding_acronym "NSF ANT";
    String awards_0_funding_source_nid "369";
    String awards_0_program_manager "Dr Peter Milne";
    String awards_0_program_manager_nid "51468";
    String cdm_data_type "Other";
    String comment 
"LMG11-10 CTD data 
     A. Bucklin, Chief Scientist 
     version: 2014-01-27";
    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.2d  13 Jun 2019";
    String date_created "2015-05-19T18:55:29Z";
    String date_modified "2016-10-03T17:28:32Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.661344";
    Float64 Easternmost_Easting -53.5638;
    Float64 geospatial_lat_max -60.735;
    Float64 geospatial_lat_min -65.0817;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -53.5638;
    Float64 geospatial_lon_min -68.8352;
    String geospatial_lon_units "degrees_east";
    String history 
"2019-06-26T23:51:17Z (local files)
2019-06-26T23:51:17Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_559174.das";
    String infoUrl "https://www.bco-dmo.org/dataset/559174";
    String institution "BCO-DMO";
    String instruments_0_acronym "SBE-3 Temperature";
    String instruments_0_dataset_instrument_description 
"Calibration Page of the primary sensor with model and serial numbers.
Calibration Page of the secondary sensor with model and serial numbers.";
    String instruments_0_dataset_instrument_nid "559327";
    String instruments_0_description "The SBE-3 is a slow response, frequency output temperature sensor manufactured by Sea-Bird Electronics, Inc. (Bellevue, Washington, USA).  It has an initial accuracy of +/- 0.001 degrees Celsius with a stability of +/- 0.002 degrees Celsius per year and measures seawater temperature in the range of -5.0 to +35 degrees Celsius. more information from Sea-Bird Electronics";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/134/";
    String instruments_0_instrument_name "Sea-Bird SBE-3 Temperature Sensor";
    String instruments_0_instrument_nid "473";
    String instruments_0_supplied_name "Primary Temperature Sensor";
    String instruments_1_acronym "SBE-4 Conductivity";
    String instruments_1_dataset_instrument_description 
"Calibration sheet for primary conductivity sensor with model and serial numbers.
Calibration sheet for secondary conductivity sensor with model and serial numbers.";
    String instruments_1_dataset_instrument_nid "559328";
    String instruments_1_description "The Sea-Bird SBE-4 conductivity sensor is a modular, self-contained instrument that measures conductivity from 0 to 7 Siemens/meter.  The sensors (Version 2; S/N 2000 and higher) have electrically isolated power circuits and optically coupled outputs to eliminate any possibility of noise and corrosion caused by ground loops. The sensing element is a cylindrical, flow-through, borosilicate glass cell with three internal platinum electrodes. Because the outer electrodes are connected together, electric fields are confined inside the cell, making the measured resistance (and instrument calibration) independent of calibration bath size or proximity to protective cages or other objects.";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0417/";
    String instruments_1_instrument_name "Sea-Bird SBE-4 Conductivity Sensor";
    String instruments_1_instrument_nid "474";
    String instruments_1_supplied_name "Conductivity sensors";
    String instruments_2_acronym "SBE-43 DO";
    String instruments_2_dataset_instrument_description 
"Calibration sheet for primary Dissolved oxygen sensor with model and serial numbers.
Calibration sheet for secondary Dissolved oxygen sensor with model and serial numbers.� (This calibration sheet is not well reproduced.)";
    String instruments_2_dataset_instrument_nid "559329";
    String instruments_2_description "The Sea-Bird SBE 43 dissolved oxygen sensor is a redesign of the Clark polarographic membrane type of dissolved oxygen sensors. more information from Sea-Bird Electronics";
    String instruments_2_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0036/";
    String instruments_2_instrument_name "Sea-Bird SBE 43 Dissolved Oxygen Sensor";
    String instruments_2_instrument_nid "552";
    String instruments_2_supplied_name "Dissolved Oxygen sensors";
    String instruments_3_acronym "CTD SBE 911plus";
    String instruments_3_dataset_instrument_description 
"The Sea-Bird 911+ offers real-time operation via sea cable telemetry, includes a solid state
memory module, and has a maximum depth of 6800 m. The CTD is mounted on a 24-bottle
General Oceanics rosette. �
�";
    String instruments_3_dataset_instrument_nid "559326";
    String instruments_3_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_3_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0058/";
    String instruments_3_instrument_name "CTD Sea-Bird SBE 911plus";
    String instruments_3_instrument_nid "591";
    String instruments_3_supplied_name "CTD";
    String instruments_4_acronym "ECO AFL/FL";
    String instruments_4_dataset_instrument_description 
"Calibration page for first� fluorometer.
\"The primary fluorometer was mis-calibrated (had the wrong scale factor in the calibration/processing file), so fluorescence data from the first four (or five) stations (Stns #22, #7, #8, #11) had to be re-processed with the correct scaling factor. Examination of the *.cnv file showed which casts had the miscalibrated data, as the max reading for fluorescence was ~ 0.05 mg/m3. For nearly every other station, maximum fluorescence readings were > 1.0 mg/m3. A secondary fluorometer was added to the CTD rosette between Stns #11 and #12, which verified that the issue was with the scale factor in the CTD processing software.\" (from Cruise Report)
The Default Scale Factor in the Calibration sheet, 25, is the correct scale factor and was not the one used for the first four CTDs. (2,3,5,6 from stations 22,7,8,and 11, respectively)� The fluorescence in those casts should not be used until corrected.
�";
    String instruments_4_dataset_instrument_nid "559330";
    String instruments_4_description 
"The Environmental Characterization Optics (ECO) series of single channel fluorometers delivers both high resolution and wide ranges across the entire line of parameters using 14 bit digital processing. The ECO series excels in biological monitoring and dye trace studies. The potted optics block results in long term stability of the instrument and the optional anti-biofouling technology delivers truly long term field measurements.
 more information from Wet Labs";
    String instruments_4_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0172/";
    String instruments_4_instrument_name "Wet Labs ECO-AFL/FL Fluorometer";
    String instruments_4_instrument_nid "592";
    String instruments_4_supplied_name "Fluorometer";
    String keywords "altimetry, bco, bco-dmo, biological, cast, chemical, cond, cond_2, cond_diff, currents, data, dataset, date, day, day_gmt, density, density_2, depth, depth_w, diff, dissolved, dissolved o2, dmo, erddap, fluor, iso, laboratory, lat_start, latitude, lon_start, longitude, management, month, month_gmt, O2, O2_ml_L, O2_ml_L_2, O2_um_Kg, O2_um_Kg_2, oceanography, office, optical, optical properties, oxygen, physical, physical oceanography, potemp, potemp_2, preliminary, press, profiler, properties, sal, sal_2, sal_diff, salinity, salinity-temperature-depth, satellite, sigma, sigma_t, sound, sound_vel, start, station, station_std, std, temp_2, temp_diff, temperature, time, time_start_gmt, vel, year";
    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 metadata_source "https://www.bco-dmo.org/api/dataset/559174";
    Float64 Northernmost_Northing -60.735;
    String param_mapping "{'559174': {'press': 'flag - depth', 'lon_start': 'flag - longitude', 'ISO_DateTime_UTC': 'master - time', 'lat_start': 'flag - latitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/559174/parameters";
    String people_0_affiliation "University of Connecticut";
    String people_0_affiliation_acronym "UConn - Avery Point";
    String people_0_person_name "Dr Ann Bucklin";
    String people_0_person_nid "50389";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Stony Brook University - SoMAS";
    String people_1_affiliation_acronym "SUNY-SB SoMAS";
    String people_1_person_name "Dr Joseph Warren";
    String people_1_person_nid "559320";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Ms Dicky Allison";
    String people_2_person_nid "50382";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_role_type "related";
    String project "Population ecology of Salpa thompsoni based on molecular indicators";
    String projects_0_acronym "Salp_Antarctic";
    String projects_0_description 
"The Antarctic salp, Salpa thompsoni, is an increasingly important player in the vulnerable Antarctic Peninsula pelagic ecosystem. Observations of high abundance of Salpa thompsoni during the summer in the Southern Ocean suggest that this species is capable of rapid somatic and population growth, and frequently forms dense blooms under favorable environmental conditions. The proposed research will examine genome-wide patterns of gene expression, target gene expression levels, and patterns of population genetic diversity and structure of the target salp species. Our preliminary results and data analysis have provided a promising basis for transcriptomic studies of S. thompsoni in the Southern Ocean. The proposed next steps in our genomic/transcriptomic analysis of Salpa thompsoni are: 1) completion of a reference transcriptome as a basis for genome-wide analysis of gene expression; 2) whole transcriptome shotgun sequencing (RNA-Seq) analysis to characterize gene expression in relation to individual characteristics and environmental conditions; 3) quantitative real-time PCR (qRT-PCR) characterization and validation of gene expression for 10-20 top differentially-expressed genes; and 4) detection of strand-specific allelic variation at SNP (Single Nucleotide Polymorphic) sites to analyze clonal diversity and population genetic diversity and structure. We hypothesize that: 1) deep analysis of the Salpa thompsoni transcriptome will reveal significant associations among selected set of differentially-expressed genes and critical life history stages and events (e.g., ontogenetic maturation, sexual reproduction, senescence) of the salp; and 2) the species will show variable levels of clonal diversity and significant genetic differentiation among salp populations in different regions of the Southern Ocean. Samples will be obtained from research cruises during 2011-2013 in diverse regions of the Southern Ocean; dedicated sample and data collection will be carried out during a cruise of the R/V LM GOULD (LMG11-10) to the Western Antarctic Peninsula region in November, 2011. The significance of this effort lies in new understanding of the molecular processes underlying the complex life history and population dynamics of S. thompsoni in relation to the Antarctic pelagic ecosystem and extreme and variable environmental conditions of the Southern Ocean.
Most of the data from this project are available from the Marine Geoscience Data System (MGDS), part of IEDA and is available�at http://www.marine-geo.org/tools/search/Files.php?data_set_uid=18148.";
    String projects_0_end_date "2014-05";
    String projects_0_geolocation "Southern Ocean";
    String projects_0_name "Population ecology of Salpa thompsoni based on molecular indicators";
    String projects_0_project_nid "2174";
    String projects_0_start_date "2011-06";
    String publisher_name "Ms Dicky Allison";
    String publisher_role "BCO-DMO Data Manager(s)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -65.0817;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "month_gmt, year";
    String summary 
"This is from the cruise report (see LGM1110 deployment page for link) and
particulary pertains to the Fluorescence data that were collected:
 
\\Preliminary CTD Results: A total of 20 CTD stations were occupied and
sampled during the cruise. Hydrographic data were collected in all sampling
regions of the study. Casts were sent to the shallower of 1,000 m or 5-10 m
above the bottom. The primary fluorometer was mis-calibrated (had the wrong
scale factor in the calibration/processing file), so fluorescence data from
the first four (or five) stations (Stns #22, #7, #8, #11) had to be re-
processed with the correct scaling factor. Examination of the *.cnv file
showed which casts had the miscalibrated data, as the max reading for
fluorescence was ~ 0.05 mg/m3. For nearly every other station, maximum
fluorescence readings were > 1.0 mg/m3. A secondary fluorometer was added to
the CTD rosette between Stns #11 and #12, which verified that the issue was
with the scale factor in the CTD processing software.\\
 
The data that are served have warnings about fluorescence numbers in the
headers of the casts at Stations 22, 7, 8 and 11.
 
Variables that were part of the data that have been rendered invisible from
the data online are: Elapsed time in seconds, modulo error count (always
zero), and nbin (number of scans per bin). Those numbers are available upon
request.
 
IEDA has published a DOI for another version of this dataset: 'Bucklin, A.,
(2015). 'Calibrated Hydrographic Data from Drake Passage acquired with a CTD
during the Laurence M. Gould expedition LMG1110 (2011).
doi:\\u00a0[10.1594/IEDA/318146](\\\\http://www.marine-
geo.org/tools/search/Files.php?tab=datacitation&data_set_uid=18146\\\\).";
    String time_coverage_end "2011-11-25T20:36:57Z";
    String time_coverage_start "2011-11-09T18:19:37Z";
    String title "CTD data from ARSV Laurence M. Gould LMG1110 in the Southern Ocean from November to December 2011 (Salp_Antarctic project)";
    String version "1";
    Float64 Westernmost_Easting -68.8352;
    String xml_source "osprey2erddap.update_xml() v1.5-beta";
  }
}

 

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