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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Biomaper-II environmental data from R/V Endeavor and R/V Oceanus cruises
EN307, EN330, EN331, OC332 and OC334 to Georges Bank and the Gulf of Maine in
1997-1999 (GB project)
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2295)
Range: longitude = -8401.15 to 68.84333°E, latitude = 0.0 to 43.83473°N
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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 {
  cruiseid {
    String description "cruise identification, e.g.  EN330, for Endeavor cruise 330";
    String ioos_category "Unknown";
    String long_name "Cruiseid";
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 1997, 1999;
    String description "year, four digit";
    String ioos_category "Time";
    String long_name "Year";
  brief_desc {
    String description "Brief cruise description, suchas broad-scale, process, mooring";
    String ioos_category "Unknown";
    String long_name "Brief Desc";
  tow {
    String description "Tow number";
    String ioos_category "Unknown";
    String long_name "Tow";
  day_local {
    Byte _FillValue 127;
    Byte actual_range 4, 26;
    String description "day of month, local time (1 - 31)";
    String ioos_category "Time";
    String long_name "Day Local";
  month_local {
    Byte _FillValue 127;
    Byte actual_range 10, 12;
    String description "month of year, local time (1 - 12)";
    String ioos_category "Time";
    String long_name "Month Local";
  station {
    Byte _FillValue 127;
    Byte actual_range 1, 1;
    String description "station number, from event log";
    String ioos_category "Identifier";
    String long_name "Station";
  station_std {
    Float64 _FillValue NaN;
    String description "standard station number, from eventlog";
    String ioos_category "Unknown";
    String long_name "Station Std";
  yrday_local {
    Float64 _FillValue NaN;
    Float64 actual_range 282.666019, 346.978183;
    String description "year day, (i.e.  Jan 1 at noon equals year day 1.5), local time";
    String ioos_category "Unknown";
    String long_name "Yrday Local";
    String units "decimal year";
  time_local {
    String description "local time using 24 hour clock";
    String ioos_category "Time";
    String long_name "Time Local";
    String units "decimal hour";
  press {
    Float64 _FillValue NaN;
    Float64 actual_range -188.83, 2009.74;
    String description "depth of sample";
    String ioos_category "Unknown";
    String long_name "Press";
    String units "decibars";
  temp {
    String description "temperature";
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degrees C";
  potemp {
    String description "potential temperature�";
    String ioos_category "Unknown";
    String long_name "Potemp";
    String units "degrees C";
  sal {
    String description "salinity";
    String ioos_category "Unknown";
    String long_name "Sal";
    String units "PSU";
  sigma_0 {
    String description "potential density�";
    String ioos_category "Unknown";
    String long_name "Sigma 0";
  flvolt {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 6.528;
    String description "fluorescence (0-5 volts)";
    String ioos_category "Unknown";
    String long_name "Flvolt";
    String units "volts";
  angle {
    String description "angle of towbody relative to vertical (0-89 degrees)";
    String ioos_category "Unknown";
    String long_name "Angle";
  vtvel {
    String description "vertical tow velocity";
    String ioos_category "Unknown";
    String long_name "Vtvel";
    String units "meters/minute";
  trans_v {
    String description "transmissometry or light transmission (0-5 volts)";
    String ioos_category "Unknown";
    String long_name "Trans V";
    String units "volts";
  oxycurrent {
    String description "oxygen sensor current (0-5 volts)";
    String ioos_category "Currents";
    String long_name "Oxycurrent";
    String units "volts";
  oxytemp {
    String description "oxygen sensor internal temperature (0-5 volts)";
    String ioos_category "Unknown";
    String long_name "Oxytemp";
    String units "volts";
  o2 {
    String description "dissolved oxygen";
    String ioos_category "Dissolved O2";
    String long_name "O2";
    String units "milliliter/liter";
  lite {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 4.3614;
    String description "downwelling light";
    String ioos_category "Unknown";
    String long_name "Lite";
    String units "volts";
  tempco {
    String description "light sensor thermistor";
    String ioos_category "Unknown";
    String long_name "Tempco";
    String units "vo lts";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 43.834728;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude, negative = South";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value -999.0;
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -8401.15, 68.843333;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude, negative = West";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"These data are from the Enviromental Sensing System (ESS) part of theBIO-
Optical Multi-frequency Acoustical and Physical Environmental Recorder or
    String awards_0_award_nid "54610";
    String awards_0_award_number "unknown GB NSF";
    String awards_0_funder_name "National Science Foundation";
    String awards_0_funding_acronym "NSF";
    String awards_0_funding_source_nid "350";
    String awards_0_program_manager "Dr David  L. Garrison";
    String awards_0_program_manager_nid "50534";
    String awards_1_award_nid "54626";
    String awards_1_award_number "unknown GB NOAA";
    String awards_1_funder_name "National Oceanic and Atmospheric Administration";
    String awards_1_funding_acronym "NOAA";
    String awards_1_funding_source_nid "352";
    String cdm_data_type "Other";
    String comment 
"Displayed by /data/dallison/bmp_ess/mocpro_level1.pl, V1.12/February 7, 2011 
   For /data7/gbdata/en307/bmp_ess, BiomaperII, PRO, EN307, 1997 
 Displayed by /data/dallison/bmp_ess/mocpro_level2.pl, V1.00so/May 9, 2003 
    Using data file /data7/gbdata/en307/bmp_ess/BM2_001.PRO 
  Tow: M-01-003   EN307  
  Date: 9 October 1997  
  Temperature Probe #  2072  Conductivity Probe #  1855  
  Pressure Probe #  124 Oxygen Probe #  130349  
  Transmissometer #   1 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.2d  13 Jun 2019";
    String date_created "2009-11-24T18:35:30Z";
    String date_modified "2019-02-22T20:22:13Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.2295.1";
    Float64 Easternmost_Easting 68.843333;
    Float64 geospatial_lat_max 43.834728;
    Float64 geospatial_lat_min 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 68.843333;
    Float64 geospatial_lon_min -8401.15;
    String geospatial_lon_units "degrees_east";
    String history 
"2019-08-24T14:10:49Z (local files)
2019-08-24T14:10:49Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2295.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2295";
    String institution "BCO-DMO";
    String instruments_0_acronym "BIOMAPERII";
    String instruments_0_dataset_instrument_description "BIO-optical Multi-frequency Acoustical and Physical Environmental Recorder version 2, see also ESS_BiomaperII. The system consists of a multi-frequency sonar (up-looking and down-looking pairs of transducers operating at five frequencies: 43,120,200,420, and 1000kHz), a video plankton recorder system (VPR), an environmental sensor system (CTD, fluorometer, transmissometer), and several other bio-optical sensors (down- and upwelling spectral radiometers, spectral attenuation, and backscattering, and absorption meters).";
    String instruments_0_dataset_instrument_nid "4205";
    String instruments_0_description "BIOMAPER II is a set of sensors on a long aluminum frame that resembles the tail of a World War II airplane. A research vessel tows the instrument through the water on a specialized tow cable that sends power to the sensors and brings data back to the ship. People use BIOMAPER II to learn about phytoplankton and zooplankton over areas that are too large to study with the traditional net-and-microscope method. Whereas nets can sample areas up to about 5 meters (16 feet) on a side, BIOMAPER II can record data from 500 meters (1,640 feet) or more of the water column at a time. The instrument's standard suite of sensors were chosen for studying plankton: a five-frequency sonar system, a video plankton recorder and an environmental sensor system (ESS, like the one on MOCNESS). The ESS measures water temperature, salinity, oxygen, chlorophyll and light levels. BIOMAPER II also has room for attaching other instruments for specific uses. The instrument's official name is BIOMAPER-II: the BIo-Optical Multi-frequency Acoustical and Physical Environmental Recorder. The Roman numeral II indicates that it's a redesign of the original BIOMAPER, a prototype that was invented and tested in the mid 1990s. (more information).";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/NETT0007/";
    String instruments_0_instrument_name "BIo-Optical Multi-frequency Acoustical and Physical Environmental Recorder II";
    String instruments_0_instrument_nid "409";
    String instruments_0_supplied_name "BIo-Optical Multi-frequency Acoustical and Physical Environmental Recorder II";
    String keywords "altimetry, angle, bco, bco-dmo, biological, brief, brief_desc, chemical, cruiseid, currents, data, dataset, day, day_local, depth, desc, dissolved, dissolved o2, dmo, erddap, flvolt, identifier, laboratory, latitude, lite, local, longitude, management, month, month_local, O2, oceanography, office, oxycurrent, oxygen, oxytemp, potemp, preliminary, press, profiler, sal, salinity, salinity-temperature-depth, satellite, sigma, sigma_0, station, station_std, std, tempco, temperature, time, time_local, tow, trans, trans_v, v, vtvel, year, yrday, yrday_local";
    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/2295";
    Float64 Northernmost_Northing 43.834728;
    String param_mapping "{'2295': {'lat': 'master - latitude', 'press': 'flag - depth', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2295/parameters";
    String people_0_affiliation "Woods Hole Oceanographic Institution";
    String people_0_affiliation_acronym "WHOI";
    String people_0_person_name "Dr Peter H. Wiebe";
    String people_0_person_nid "50454";
    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 "Dr Peter H. Wiebe";
    String people_1_person_nid "50454";
    String people_1_role "Scientist";
    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 "U.S. GLOBEC Georges Bank";
    String projects_0_acronym "GB";
    String projects_0_description 
"The U.S. GLOBEC Georges Bank Program is a large multi- disciplinary multi-year oceanographic effort. The proximate goal is to understand the population dynamics of key species on the Bank - Cod, Haddock, and two species of zooplankton (Calanus finmarchicus and Pseudocalanus) - in terms of their coupling to the physical environment and in terms of their predators and prey. The ultimate goal is to be able to predict changes in the distribution and abundance of these species as a result of changes in their physical and biotic environment as well as to anticipate how their populations might respond to climate change.
The effort is substantial, requiring broad-scale surveys of the entire Bank, and process studies which focus both on the links between the target species and their physical environment, and the determination of fundamental aspects of these species' life history (birth rates, growth rates, death rates, etc).
Equally important are the modelling efforts that are ongoing which seek to provide realistic predictions of the flow field and which utilize the life history information to produce an integrated view of the dynamics of the populations.
The U.S. GLOBEC Georges Bank Executive Committee (EXCO) provides program leadership and effective communication with the funding agencies.";
    String projects_0_geolocation "Georges Bank, Gulf of Maine, Northwest Atlantic Ocean";
    String projects_0_name "U.S. GLOBEC Georges Bank";
    String projects_0_project_nid "2037";
    String projects_0_project_website "http://globec.whoi.edu/globec_program.html";
    String projects_0_start_date "1991-01";
    String publisher_name "Ms Dicky Allison";
    String publisher_role "BCO-DMO Data Manager(s)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "brief_desc, station_std";
    String summary "Biomaper-II environmental data from R/V Endeavor and R/V Oceanus cruises EN307, EN330, EN331, OC332 and OC334 to Georges Bank and the Gulf of Maine in 1997-1999";
    String title "Biomaper-II environmental data from R/V Endeavor and R/V Oceanus cruises EN307, EN330, EN331, OC332 and OC334 to Georges Bank and the Gulf of Maine in 1997-1999 (GB project)";
    String version "1";
    Float64 Westernmost_Easting -8401.15;
    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
For example,
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