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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [MOC10data_lengths] - Zooplankton length data from the 10m2 MOCNESS from R/V
Endeavor, R/V Albatross IV,and R/V Oceanusbroadscale cruises in the Gulf of
Maine and Georges Bank from 1995-1999 (GB project) (U.S. GLOBEC Georges Bank)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2327)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 cruiseid ?          "AL9505"    "OC341"
 year ?          1995    1999
 month_local ?          "April"    "May"
 station_std ?          1    40
 latitude (degrees_north) ?          40.45    42.3
  < slider >
 longitude (degrees_east) ?          -68.99    -65.848
  < slider >
 net ?          1    4
 species ?          "Acanthephyra_haeck..."    "Vinciguerria_nimba..."
 phylum ?          "Annelida"    "Urochordata"
 length (mm) ?          0    915
 
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 information)

(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 {
  cruiseid {
    String bcodmo_name "cruiseid";
    String description "cruise identification";
    String long_name "Cruiseid";
  }
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 1995, 1999;
    String bcodmo_name "year";
    String description "year, 4 digit year";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
  }
  month_local {
    String bcodmo_name "month_local";
    String description "month of year, local time, (01-12)";
    String long_name "Month Local";
  }
  station_std {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 40;
    String bcodmo_name "station_std";
    String description "standard station number";
    String long_name "Station Std";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 40.45, 42.3;
    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 -68.99, -65.848;
    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";
  }
  net {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 4;
    String bcodmo_name "net";
    String description "net number, one of 4 nets (1-4)";
    String long_name "Net";
  }
  species {
    String bcodmo_name "species";
    String description "species name";
    String long_name "Species";
  }
  phylum {
    String bcodmo_name "phylum";
    String description "classification by phylum";
    String long_name "Phylum";
  }
  length {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 915;
    String bcodmo_name "unknown";
    String description "length (longest dimension) of individual animal";
    String long_name "Length";
    String units "mm";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description "Moc 10 zooplankton length data,";
    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 "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 
"Moc 10 zooplankton length data 
  E. Horgan and L. Madin, PIs";
    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-25T13:50:34Z";
    String date_modified "2020-01-29T18:10:36Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.2327.1";
    Float64 Easternmost_Easting -65.848;
    Float64 geospatial_lat_max 42.3;
    Float64 geospatial_lat_min 40.45;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -65.848;
    Float64 geospatial_lon_min -68.99;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-18T10:43:49Z (local files)
2024-12-18T10:43:49Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_2327.html";
    String infoUrl "https://www.bco-dmo.org/dataset/2327";
    String institution "BCO-DMO";
    String instruments_0_acronym "MOC10";
    String instruments_0_dataset_instrument_description "MOCNESS 10 meter square nets (3 millimeter mesh).";
    String instruments_0_dataset_instrument_nid "4093";
    String instruments_0_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_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/NETT0097/";
    String instruments_0_instrument_name "MOCNESS10";
    String instruments_0_instrument_nid "438";
    String instruments_0_supplied_name "MOCNESS10";
    String keywords "bco, bco-dmo, biological, chemical, cruiseid, data, dataset, depth, dmo, erddap, latitude, length, local, longitude, management, month, month_local, net, oceanography, office, phylum, preliminary, profiler, salinity, salinity-temperature-depth, species, station, station_std, std, temperature, year";
    String license "https://www.bco-dmo.org/dataset/2327/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2327";
    Float64 Northernmost_Northing 42.3;
    String param_mapping "{'2327': {'lat': 'flag - latitude', 'lon': 'flag - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2327/parameters";
    String people_0_affiliation "Woods Hole Oceanographic Institution";
    String people_0_affiliation_acronym "WHOI";
    String people_0_person_name "Mr Erich Horgan";
    String people_0_person_nid "50411";
    String people_0_role "Co-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 Laurence P. Madin";
    String people_1_person_nid "50426";
    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 "GB";
    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 "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.45;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Zooplankton length data from the 10m2 MOCNESS from R/V Endeavor, R/V Albatross IV,and R/V Oceanusbroadscale cruises in the Gulf of Maine and Georges Bank from 1995-1999";
    String title "[MOC10data_lengths] - Zooplankton length data from the 10m2 MOCNESS from R/V Endeavor, R/V Albatross IV,and R/V Oceanusbroadscale cruises in the Gulf of Maine and Georges Bank from 1995-1999 (GB project) (U.S. GLOBEC Georges Bank)";
    String version "1";
    Float64 Westernmost_Easting -68.99;
    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