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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Bigelow Bight_sm invertebrates] - Benthic habitat correlates of juvenile fish
and invertebrates from the F/V North Star NEC-MD2001-1 from the the Western GoM
Closed Area (NEC-CoopRes project) (Northeast Consortium: Cooperative Research)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2783)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 year ?          2002    2003
 site ?          "BB"    "WR"
 date_local ?          "08/4/2002?"    "8/8/2003"
 taxon ?          "Acanthohaustorius_..."    "shell-less_bivalves"
 length ?          0.0    107.01
 width ?          0.0    52.2
 number ?          1    924
 abundance ?          0.0    24060.96
 latitude (degrees_north) ?          43.02813    43.48435
  < slider >
 longitude (degrees_east) ?          -70.6852    -70.02152
  < slider >
 comments ?          "(date_is_8/1/02)"    "ziggy"
 
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 {
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 2002, 2003;
    String bcodmo_name "year";
    String description "year, reported as YYYY";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
  }
  site {
    String bcodmo_name "unknown";
    String description "The site each sample was taken, including all replicates. Site Codes: BB = Bigelow Bight, CN = Cape Neddick, JL = Jeffery's Ledge, KB and KR = Kennebunk River, PR = Piscataqua River, PRE = Piscataqua River Estuary, SR =  Saco River, SRE =  Saco River estuary, WH and WR = Webhanet River, WI = Wood Island, near the mouth of the Saco River.";
    String long_name "Site";
  }
  date_local {
    String bcodmo_name "date_local";
    String description "Date sample was collected, local time";
    String long_name "Date Local";
  }
  taxon {
    String bcodmo_name "taxon";
    String description "Taxa or scientific name of the individual organism (lowest \t\ttaxonomic classification possible)";
    String long_name "Taxon";
  }
  length {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 107.01;
    String bcodmo_name "unknown";
    String description "length of organism based on criteria set above,  as millimeters";
    String long_name "Length";
  }
  width {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 52.2;
    String bcodmo_name "unknown";
    String description "width  of organism based on criteria set above,  as millimeters";
    String long_name "Width";
  }
  number {
    Int16 _FillValue 32767;
    Int16 actual_range 1, 924;
    String bcodmo_name "number";
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "number of organisms of a particular size and species found";
    String long_name "Number";
  }
  abundance {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 24060.96;
    String bcodmo_name "abundance";
    String description "number of organisms per meter squared. This is the corrected number of organisms of a given size class that are in a one meter square area of habitat. This number is derived by multiplying the number from the \"number\" column by the number of quadrates taken from the original sample and then dividing by the area sampled.   Example:  If you took a grab sample, split it into four parts and only possessed one of the four sub-samples then you would have to multiply your results by four to see the number for your entire sample.";
    String long_name "Abundance";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P03/current/B070/";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 43.02813, 43.48435;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "The latitude where the sample was collected in decimal degrees. \tNorth is Positive.";
    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 -70.6852, -70.02152;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "The longitude where the sample was collected in decimal degrees.  \t\tWest is Negative.";
    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";
  }
  comments {
    String bcodmo_name "comment";
    String description "This column contains useful information on given samples or organisms such as problems with measurements or identification or notes about possible mislabeling of samples, etc.20 individuals were measured for each species and the remaining were counted for biomass purposes. This accounts for the \"no measure\" seen in the notes column.";
    String long_name "Comments";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"Results thus far are based on analysis of video data taken via ROV in sites
both inside and outside the WGOMC. Five sites were investigated in the two
year portion of the WGOMC, with three to five ROV stations/site, and four
sites in the actively trawled Kettle, with three ROV stations/site. All
sessile, or weakly mobile, invertebrates were identified and quantified in
each ROV transect in frames where the ROV was positioned on the bottom. Due to
unequal numbers of frames in some transects, numbers were standardized to 50
frames. Non-parametric multi-dimensional scaling (NMDS) was used to
investigate similarities in epifaunal species diversity and abundances. ANOSIM
analysis found a p-value of 0.08, thus our plot suggests a weakly significant
partitioning between closed and open stations.";
    String awards_0_award_nid "55021";
    String awards_0_award_number "unknown NEC-CoopRes NEC";
    String awards_0_funder_name "NorthEast Consortium";
    String awards_0_funding_acronym "NEC";
    String awards_0_funding_source_nid "383";
    String cdm_data_type "Other";
    String comment 
"Benthic Habitat correlates of Juvenile Fish (invertebrates) 
  PIs - Michele Dionne and Jeremy Miller";
    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-17T12:46:10Z";
    String date_modified "2019-02-18T20:02:59Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.2783.1";
    Float64 Easternmost_Easting -70.02152;
    Float64 geospatial_lat_max 43.48435;
    Float64 geospatial_lat_min 43.02813;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -70.02152;
    Float64 geospatial_lon_min -70.6852;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-23T17:24:28Z (local files)
2024-11-23T17:24:28Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_2783.html";
    String infoUrl "https://www.bco-dmo.org/dataset/2783";
    String institution "BCO-DMO";
    String instruments_0_acronym "ROV";
    String instruments_0_dataset_instrument_description "sediment profile camera imager (SPI camera)";
    String instruments_0_dataset_instrument_nid "4753";
    String instruments_0_description "Remotely operated underwater vehicles (ROVs) are unoccupied, highly maneuverable underwater robots operated by a person aboard a surface vessel. They are linked to the ship by a group of cables that carry electrical signals back and forth between the operator and the vehicle. Most are equipped with at least a video camera and lights. Additional equipment is commonly added to expand the vehicle’s capabilities. These may include a still camera, a manipulator or cutting arm, water samplers, and instruments that measure water clarity, light penetration, and temperature. More information.";
    String instruments_0_instrument_name "Remotely Operated Vehicle";
    String instruments_0_instrument_nid "445";
    String instruments_0_supplied_name "Remotely Operated Vehicle";
    String instruments_1_acronym "SPI Camera";
    String instruments_1_dataset_instrument_nid "5245";
    String instruments_1_description "The sediment profile imaging (SPI) system is designed to photograph the sediment-water interface without creating disturbance. A sharp-edged prism cuts cleanly into the sediment to a depth of 15 to 20 cm. The camera is mounted in the top of the prism, and a mirror is used to reflect the sediment image to the camera from the vertical faceplate. Since the sediment is right up against the faceplate, lack of water clarity is never a limitation on this optical method. (from https://www.coast.noaa.gov/benthic/mapping/techniques/sensors/spi.htm)";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/378/";
    String instruments_1_instrument_name "Camera -  Sediment Profile Imaging";
    String instruments_1_instrument_nid "590";
    String instruments_1_supplied_name "Camera -  Sediment Profile Imaging";
    String keywords "abundance, bco, bco-dmo, biological, chemical, comments, data, dataset, date, date_local, dmo, erddap, latitude, length, local, longitude, management, number, oceanography, office, preliminary, site, taxon, width, year";
    String license "https://www.bco-dmo.org/dataset/2783/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2783";
    Float64 Northernmost_Northing 43.48435;
    String param_mapping "{'2783': {'lat': 'master - latitude', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2783/parameters";
    String people_0_person_name "Michele Dionne";
    String people_0_person_nid "50899";
    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 "Nancy Copley";
    String people_1_person_nid "50396";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "NEC-CoopRes";
    String projects_0_acronym "NEC-CoopRes";
    String projects_0_description 
"The Northeast Consortium encourages and funds cooperative research and monitoring projects in the Gulf of Maine and Georges Bank that have effective, equal partnerships among fishermen, scientists, educators, and marine resource managers.
The Northeast Consortium seeks to fund projects that will be conducted in a responsible manner. Cooperative research projects are designed to minimize any negative impacts to ecosystems or marine organisms, and be consistent with accepted ethical research practices, including the use of animals and human subjects in research, scrutiny of research protocols by an institutional board of review, etc.";
    String projects_0_geolocation "Georges Bank, Gulf of Maine";
    String projects_0_name "Northeast Consortium: Cooperative Research";
    String projects_0_project_nid "2045";
    String projects_0_project_website "http://northeastconsortium.org/";
    String projects_0_start_date "1999-01";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.02813;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Benthic habitat correlates of juvenile fish and invertebrates from the F/V North Star NEC-MD2001-1 from the the Western GoM Closed Area (NEC-CoopRes project)";
    String title "[Bigelow Bight_sm invertebrates] - Benthic habitat correlates of juvenile fish and invertebrates from the F/V North Star NEC-MD2001-1 from the the Western GoM Closed Area (NEC-CoopRes project) (Northeast Consortium: Cooperative Research)";
    String version "1";
    Float64 Westernmost_Easting -70.6852;
    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