Data Access Form

Dataset Title:	[cp_depths] - Acoustic backscatter depth data in meters (one of three related datasets) from the AL9801 cruise on the R/V Albatross IV in the Gulf of Maine and Georges Bank in 1998 (GB project (U.S. GLOBEC Georges Bank)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_2393)
Information:	Summary \| License \| ISO 19115 \| Metadata \| Background \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable	Optional Constraint #1		Optional Constraint #2		Minimum	Maximum
depth (m)					0.5	200.0

Server-side Functions

distinct()

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 {
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range 0.5, 200.0;
    String axis "Z";
    String bcodmo_name "depth";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "depth values used for processing acoustic data.";
    String ioos_category "Location";
    String long_name "Depth";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/DEPH/";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description "\"\"";
    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 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 "2010-08-05T21:57:14Z";
    String date_modified "2020-01-27T20:59:48Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.2393.1";
    Float64 geospatial_vertical_max 200.0;
    Float64 geospatial_vertical_min 0.5;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-23T16:51:51Z (local files)
2024-11-23T16:51:51Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_2393.html";
    String infoUrl "https://www.bco-dmo.org/dataset/2393";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, depth, dmo, erddap, management, oceanography, office, preliminary";
    String license "https://www.bco-dmo.org/dataset/2393/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2393";
    String param_mapping "{'2393': {'depth': 'master - depth'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2393/parameters";
    String people_0_affiliation "Woods Hole Oceanographic Institution";
    String people_0_affiliation_acronym "WHOI";
    String people_0_person_name "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 BCO-DMO";
    String people_1_person_name "Ms Dicky Allison";
    String people_1_person_nid "50382";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_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)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Acoustic backscatter depth data in meters (one of three related datasets) from the AL9801 cruise on the R/V Albatross IV in the Gulf of Maine and Georges Bank in 1998 (GLOBEC-Georges Bank project).";
    String title "[cp_depths] - Acoustic backscatter depth data in meters (one of three related datasets) from the AL9801 cruise on the R/V Albatross IV in the Gulf of Maine and Georges Bank in 1998 (GB project (U.S. GLOBEC Georges Bank)";
    String version "1";
    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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.