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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD data collected during MOCNESS hauls from ARSV Laurence M. Gould and RVIB
Nathaniel B. Palmer cruises LMG0203, NBP0104,and NBP0204 in the Southern Ocean
from 2001-2002 (SOGLOBEC project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2388)
Range: longitude = -999.0 to -64.1496°E, latitude = -999.0 to 33.064°N, depth = -245.0 to 8511.0m
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: 
[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 {
  datatype {
    String bcodmo_name "datatype";
    String description "sampling method - instrument type, e.g. MOCNESS-1 or MOCNESS-10";
    String long_name "Datatype";
  }
  cruiseid {
    String bcodmo_name "cruiseid";
    String description "cruise identification, e.g. NBP0202, for RVIB Palmer cruise 0202";
    String long_name "Cruiseid";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2001, 2002;
    String bcodmo_name "year";
    String description "year";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
  }
  brief_desc {
    String bcodmo_name "brief_desc";
    String description "brief cruise description, such as process or mooring";
    String long_name "Brief Desc";
  }
  tow {
    String bcodmo_name "tow";
    String description "tow number";
    String long_name "Tow";
  }
  day_gmt {
    String bcodmo_name "day_gmt";
    String description "day of month, GMT, 1 - 31";
    String long_name "Day Gmt";
  }
  month_gmt {
    String bcodmo_name "month_gmt";
    String description "month of year, GMT, 1 - 12";
    String long_name "Month Gmt";
  }
  station {
    String bcodmo_name "station";
    String description "station number, from event log";
    String long_name "Station";
  }
  station_std {
    String bcodmo_name "station_std";
    String description "standard station number, from event log";
    String long_name "Station Std";
  }
  yrday_gmt {
    Float64 _FillValue NaN;
    Float64 actual_range 103.827917, 255.027361;
    String bcodmo_name "yrday_gmt";
    String description "year day as a decimal, based on Julian calendar, GMT";
    String long_name "Yrday Gmt";
    String units "YYY.Y";
  }
  time_gmt {
    String bcodmo_name "time_gmt";
    String description "time, GMT using 24 hour clock to decimal minutes";
    String long_name "Time Gmt";
    String units "HHmm.m";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range -245.0, 8511.0;
    String axis "Z";
    String bcodmo_name "pressure";
    String description "depth of observation or sample";
    String ioos_category "Location";
    String long_name "Press";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/PRESPR01/";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  temp {
    String bcodmo_name "temperature";
    String description "temperature of water";
    String long_name "Temperature";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/TEMPP901/";
    String units "degrees C";
  }
  potemp {
    String bcodmo_name "potemp";
    String description "potential temperature or theta1";
    String long_name "Potemp";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/POTMCV01/";
    String units "degrees C";
  }
  sal {
    String bcodmo_name "sal";
    String description "salinity calculated from conductivity, bad values are set to 50";
    String long_name "Sal";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/PSALST01/";
  }
  sigma_0 {
    String bcodmo_name "sigma_0";
    String description "potential density1";
    String long_name "Sigma 0";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/SIGTPR01/";
    String units "kg/m3";
  }
  flvolt {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 8.318;
    String bcodmo_name "fluor voltage";
    String description "relative fluorescence (0-5 volts)";
    String long_name "Flvolt";
    String units "volts";
  }
  angle {
    String bcodmo_name "angle";
    String description "angle of net frame relative to vertical (0-89 degrees)";
    String long_name "Angle";
    String units "degrees";
  }
  flow {
    String bcodmo_name "flow";
    String description "consecutive flow counts";
    String long_name "Flow";
  }
  hzvel {
    String bcodmo_name "hzvel";
    String description "horizontal net velocity";
    String long_name "Hzvel";
    String units "m/min";
  }
  vtvel {
    String bcodmo_name "vtvel";
    String description "vertical net velocity";
    String long_name "Vtvel";
    String units "m/min";
  }
  vol_filt {
    String bcodmo_name "vol_filt";
    String description "volume filtered";
    String long_name "Vol Filt";
    String units "meters³";
  }
  trans_v {
    String bcodmo_name "trans_v";
    String description "transmissometry or light transmission, (0-5 volts)";
    String long_name "Trans V";
    String units "volts";
  }
  o2 {
    String bcodmo_name "dissolved Oxygen";
    String description "dissolved oxygen";
    String long_name "O2";
    String units "ml/liter";
  }
  lite {
    Float64 _FillValue NaN;
    String bcodmo_name "unknown";
    String description "down welling light";
    String long_name "Lite";
    String units "volts";
  }
  net {
    String bcodmo_name "net";
    String description "MOCNESS net number, (00-08)";
    String long_name "Net";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range -999.0, 33.064;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude, negative = South";
    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 -999.0, -64.1496;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude, negative = West";
    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";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"The MOCNESS is based on the Tucker Trawl principle (Tucker, 1951). The
particular MOCNESS system from which these CTD data came is one of two net
systems. The MOCNESS-1 has nine rectangular nets (1m x 1.4 m) which are opened
and closed sequentially by commands through conducting cable from the surface
(Wiebe et al., 1976). The MOCNESS-10 (with 10 m2 nets)carries 6 nets of 3.0-mm
circular mesh. In both systems, 'the underwater unit sends a data frame,
comprised of temperature, depth, conductivity, net-frame angle, flow count,
time, number of open net, and net opening/closing, to the deck unit in a
compressed hexadecimal format every 2 seconds and from the deck unit to a
microcomputer every 4 seconds... Temperature (to approximately 0.01 deg C) and
conductivity are measured with SEABIRD sensors. Normally, a modified
T.S.K.-flowmeter is used... Both the temperature and conductivity sensors and
the flow meter are mounted on top of the frame so that they face horizontally
when the frame is at a towing angle of 45deg... Calculations of salinity (to
approximately 0.01 o/oo S), potential temperature (theta), potential density
(sigma), the oblique and vertical velocities of the net, and the approximate
volume filtered by each net are made after each string of data has been
received by the computer.' (Wiebe et al., 1985) In addition, data were
collected from four other sensors attached to the frame: the Transmissometer,
the Fluorometer, the Down welling light sensor, and the Oxygen sensor. A
SeaBird underwater pump was also included in the sensor suite.";
    String awards_0_award_nid "54617";
    String awards_0_award_number "unknown SOGLOBEC NSF ANT";
    String awards_0_funder_name "NSF Antarctic Sciences";
    String awards_0_funding_acronym "NSF ANT";
    String awards_0_funding_source_nid "369";
    String cdm_data_type "Other";
    String comment 
"Displayed by /data/rgroman/ctd_so_mocness/mocpro_level1.pl, V2.07so/October 3, 2001 
   For MOC1 data, with filetype=pro 
 Displayed by /data/rgroman/ctd_so_mocness/mocpro_level2.pl, V2.13so/May 17, 2004 
   For /data12/sodata/lmg0104/moc, MOC1, pro, LMG0104, 2001 
 Displayed by /data/rgroman/ctd_so_mocness/mocpro_level3.pl, V1.51/January 28, 2000 
    Using data file /data12/sodata/lmg0104/moc/M01_01.PRO 
  Tow: M-01-001   LMG0104 
  Date: 01 May 2001 
  Temperature Probe #  2686  Conductivity Probe #  2250 
  Pressure Probe #  149 Oxygen Probe #  1 
  Transmissometer #   439 Fluorometer #  1";
    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 "2009-11-25T16:56:52Z";
    String date_modified "2019-03-06T18:39:29Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.2388.1";
    Float64 Easternmost_Easting -64.1496;
    Float64 geospatial_lat_max 33.064;
    Float64 geospatial_lat_min -999.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.1496;
    Float64 geospatial_lon_min -999.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 8511.0;
    Float64 geospatial_vertical_min -245.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-03-29T13:26:16Z (local files)
2024-03-29T13:26:16Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2388.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2388";
    String institution "BCO-DMO";
    String instruments_0_acronym "MOC1";
    String instruments_0_dataset_instrument_description "The MOCNESS is based on the Tucker Trawl principle (Tucker, 1951). The particular MOCNESS system from which these CTD data came is one of two net systems. The MOCNESS-1 has nine rectangular nets (1m x 1.4 m) which are opened and closed sequentially by commands through conducting cable from the surface (Wiebe et al., 1976).";
    String instruments_0_dataset_instrument_nid "4152";
    String instruments_0_description "The Multiple Opening/Closing Net and Environmental Sensing System or MOCNESS is a family of net systems based on the Tucker Trawl principle. The MOCNESS-1 carries nine 1-m2 nets usually of 335 micrometer mesh and is intended for use with the macrozooplankton.  All nets are black to reduce contrast with the background.  A motor/toggle release assembly is mounted on the top portion of the frame and stainless steel cables with swaged fittings are used to attach the net bar to the toggle release.  A stepping motor in a pressure compensated case filled with oil turns the escapement crankshaft of the toggle release which sequentially releases the nets to an open then closed position on command from the surface. -- from the MOCNESS Operations Manual (1999 + 2003).";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/NETT0097/";
    String instruments_0_instrument_name "MOCNESS1";
    String instruments_0_instrument_nid "437";
    String instruments_0_supplied_name "MOCNESS1";
    String instruments_1_acronym "MOC10";
    String instruments_1_dataset_instrument_description "The MOCNESS is based on the Tucker Trawl principle (Tucker, 1951). The particular MOCNESS system from which these CTD data came is one of two net systems. The MOCNESS-10 (with 10 m2 nets)carries 6 nets of 3.0-mm circular mesh. In both systems, \"the underwater unit sends a data frame, comprised of temperature, depth, conductivity, net-frame angle, flow count, time, number of open net, and net opening/closing, to the deck unit in a compressed hexadecimal format every 2 seconds and from the deck unit to a microcomputer every 4 seconds... Temperature (to approximately 0.01 deg C) and conductivity are measured with SEABIRD sensors. Normally, a modified T.S.K.-flowmeter is used... Both the temperature and conductivity sensors and the flow meter are mounted on top of the frame so that they face horizontally when the frame is at a towing angle of 45deg... Calculations of salinity (to approximately 0.01 o/oo S), potential temperature (theta), potential density (sigma), the oblique and vertical velocities of the net, and the approximate volume filtered by each net are made after each string of data has been received by the computer.\" (Wiebe et al., 1985)";
    String instruments_1_dataset_instrument_nid "4153";
    String instruments_1_description "The Multiple Opening/Closing Net and Environmental Sensing System (MOCNESS) is based on the Tucker Trawl principle (Tucker, 1951).  The MOCNESS-10 (with 10 m^2 nets) carries 6 nets of 3.0-mm circular mesh which are opened and closed sequentially by commands through conducting cable from the surface (Wiebe et al., 1976). In this system, \"the underwater unit sends a data frame, comprising temperature, depth, conductivity, net-frame angle, flow count, time, number of open net, and net opening/closing, to the deck unit in a compressed hexadecimal format every 2 seconds and from the deck unit to a microcomputer every 4 seconds\" (Wiebe et al., 1985).";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/NETT0097/";
    String instruments_1_instrument_name "MOCNESS10";
    String instruments_1_instrument_nid "438";
    String instruments_1_supplied_name "MOCNESS10";
    String keywords "altimetry, angle, bco, bco-dmo, biological, brief, brief_desc, chemical, cruiseid, data, dataset, datatype, day, day_gmt, depth, desc, dmo, erddap, filt, flow, flvolt, hzvel, laboratory, latitude, lite, longitude, management, month, month_gmt, net, O2, oceanography, office, oxygen, potemp, preliminary, press, profiler, sal, salinity, salinity-temperature-depth, satellite, sigma, sigma_0, station, station_std, std, temperature, time, time_gmt, tow, trans, trans_v, v, vol, vol_filt, vtvel, year, yrday, yrday_gmt";
    String license "https://www.bco-dmo.org/dataset/2388/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2388";
    Float64 Northernmost_Northing 33.064;
    String param_mapping "{'2388': {'lat': 'master - latitude', 'press': 'flag - depth', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2388/parameters";
    String people_0_affiliation "University of South Florida";
    String people_0_affiliation_acronym "USF";
    String people_0_person_name "Dr Joseph  J. Torres";
    String people_0_person_nid "50487";
    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";
    String people_1_person_name "Peter H. Wiebe";
    String people_1_person_nid "50454";
    String people_1_role "Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI";
    String people_2_person_name "Nancy Copley";
    String people_2_person_nid "50396";
    String people_2_role "Technician";
    String people_2_role_type "related";
    String people_3_affiliation "Woods Hole Oceanographic Institution";
    String people_3_affiliation_acronym "WHOI BCO-DMO";
    String people_3_person_name "Ms Dicky Allison";
    String people_3_person_nid "50382";
    String people_3_role "BCO-DMO Data Manager";
    String people_3_role_type "related";
    String project "SOGLOBEC";
    String projects_0_acronym "SOGLOBEC";
    String projects_0_description "The fundamental objectives of United States Global Ocean Ecosystems Dynamics (U.S. GLOBEC) Program are dependent upon the cooperation of scientists from several disciplines. Physicists, biologists, and chemists must make use of data collected during U.S. GLOBEC field programs to further our understanding of the interplay of physics, biology, and chemistry. Our objectives require quantitative analysis of interdisciplinary data sets and, therefore, data must be exchanged between researchers. To extract the full scientific value, data must be made available to the scientific community on a timely basis.";
    String projects_0_geolocation "Southern Ocean";
    String projects_0_name "U.S. GLOBEC Southern Ocean";
    String projects_0_project_nid "2039";
    String projects_0_project_website "http://www.ccpo.odu.edu/Research/globec_menu.html";
    String projects_0_start_date "2001-01";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -999.0;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "lite";
    String summary "CTD data collected during MOCNESS hauls from ARSV Laurence M. Gould and RVIB Nathaniel B. Palmer cruises LMG0203, NBP0104,and NBP0204 in the Southern Ocean from 2001-2002 (SOGLOBEC project)";
    String title "CTD data collected during MOCNESS hauls from ARSV Laurence M. Gould and RVIB Nathaniel B. Palmer cruises LMG0203, NBP0104,and NBP0204 in the Southern Ocean from 2001-2002 (SOGLOBEC project)";
    String version "1";
    Float64 Westernmost_Easting -999.0;
    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