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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Blue mussel (Mytilus edulis) size frequency data from surveys conducted in
coastal eastern Maine from 2014 to 2017 (MuLTI-2 project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_720223)
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | 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: 
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 ? )
    [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 {
  Sampling_Event {
    String bcodmo_name "event";
    String description "Identifier of sampling event";
    String long_name "Sampling Event";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/EVTAGFL/";
    String units "unitless";
  }
  Station_Code {
    String bcodmo_name "station";
    String description "Identifier of sampling station";
    String long_name "Station Code";
    String units "unitless";
  }
  Sample_Year {
    Int16 _FillValue 32767;
    Int16 actual_range 2014, 2017;
    String bcodmo_name "year";
    String description "Year of sampling event";
    String long_name "Sample Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "unitless";
  }
  Replicate_Plot {
    Byte _FillValue 127;
    Byte actual_range 1, 5;
    String bcodmo_name "replicate";
    String description "Replicate plot number";
    String long_name "Replicate Plot";
    String units "unitless";
  }
  Size_Class {
    String bcodmo_name "length";
    String description "Blue mussel (Mytilus edulis) size class.  Size class is described as a mm size range (e.g. \"10 - 15\"). Mussels were counted if the length was >= the minimum bounding size and < the maximum bounding size";
    String long_name "Size Class";
    String units "millimeters (mm)";
  }
  Mussel_Count {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 3516.0;
    String bcodmo_name "count";
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "Number of Blue mussels (Mytilus edulis) in size class within plot";
    String long_name "Mussel Count";
    String units "per individual";
  }
  Mussels_Sampled {
    Float64 _FillValue NaN;
    Float64 actual_range 10.0, 7680.0;
    String bcodmo_name "count";
    String description "Total mussels sampled within a plot";
    String long_name "Mussels Sampled";
    String units "per individual";
  }
  Size_Class_Freq {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 0.575502742;
    String bcodmo_name "unknown";
    String description "Size class frequency. The count of individual mussels within a particular size class divided by the total individual mussels sampled within a plot (Mussel_Count/Mussels_Sampled)";
    String long_name "Size Class Freq";
    String units "dimensionless";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"Location:\\u00a0\\u00a0Coastal waters of eastern Maine, from Frenchman Bay to
the Canadian border.\\u00a0Locations and descriptions for station codes used in
this dataset can be found in the dataset:\\u00a0[MuLTI-2 Mussel Station
List](\\\\\"https://www.bco-dmo.org/dataset/658755\\\\\")
 
Sampling and Analytical Methodology:\\u00a0
 
Size frequencies of blue mussels (Mytilus edulis) were measured at three
random sample locations at each of the major mussel beds (stations) along the
eastern Maine coast from Frenchman Bay to the Canadian border. At each sample
location, a 30 cm x 30 cm quadrat was laid down haphazardly in a relatively
dense patch of mussels, and the entirety of the quadrat contents harvested
(byssal thread matrix and soft-sediment included). If <30 individual mussels
were in the quadrat, further samples were taken immediately adjacent to the
original quadrat until 30+ mussels had been harvested. The contents of each
sample was returned to the lab for careful sorting into 5 mm size class bins.
The number of mussels within each size class bin were enumerated and the
frequency of each size class in each sample was calculated yielding three
frequencies per size class per year per mussel population.
 
Size Class Frequency was calculated as the Count of Individual Mussels within
a particular size class divided by the Total Individual Mussels Sampled within
a plot.";
    String awards_0_award_nid "527111";
    String awards_0_award_number "OCE-1333755";
    String awards_0_data_url "http://nsf.gov/awardsearch/showAward?AWD_ID=1333755";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "David L. Garrison";
    String awards_0_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"MuLTI-2 Mussel Size Frequency 
  PI: P. Yund 
  data version: 2017-12-28";
    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 "2017-11-30T22:13:23Z";
    String date_modified "2020-01-03T19:42:46Z";
    String defaultDataQuery "&amp;time&lt;now";
    String doi "10.1575/1912/bco-dmo.720223.1";
    String history 
"2020-07-11T11:48:44Z (local files)
2020-07-11T11:48:44Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_720223.das";
    String infoUrl "https://www.bco-dmo.org/dataset/720223";
    String institution "BCO-DMO";
    String keywords "array, array-data, bco, bco-dmo, biological, chemical, class, code, comprehensive, count, data, dataset, dmo, erddap, event, freq, large, management, mussel, Mussel_Count, mussels, Mussels_Sampled, oceanography, office, plot, preliminary, replicate, Replicate_Plot, sample, Sample_Year, sampled, sampling, Sampling_Event, size, Size_Class, Size_Class_Freq, station, Station_Code, stewardship, system, year";
    String license "https://www.bco-dmo.org/dataset/720223/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/720223";
    String param_mapping "{'720223': {}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/720223/parameters";
    String people_0_affiliation "Downeast Institute for Applied Marine Research and Education";
    String people_0_affiliation_acronym "DEI";
    String people_0_person_name "Dr Philip O. Yund";
    String people_0_person_nid "51154";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Downeast Institute for Applied Marine Research and Education";
    String people_1_affiliation_acronym "DEI";
    String people_1_person_name "Dr Philip O. Yund";
    String people_1_person_nid "51154";
    String people_1_role "Contact";
    String people_1_role_type "related";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Amber York";
    String people_2_person_nid "643627";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_role_type "related";
    String project "MuLTI-2";
    String projects_0_acronym "MuLTI-2";
    String projects_0_description 
"Acronym \"MuLTI-2\" (Mussel Larval Transport Initiative-2)
Extracted from the NSF award abstract:
Existing larval transport models focus mainly on along-shelf transport and have done little to explicitly incorporate the effects of cross-shelf mixing and transport processes. Yet cross-shelf transits (both outgoing and incoming legs) are critical components of the dispersal paths of coastal invertebrates. This project will explore the role of cross-shelf mixing in the connectivity of blue mussel populations in eastern Maine. Previous work has shown that the Eastern Maine Coastal Current (EMCC) begins to diverge from shore southwest of the Grand Manan Channel and creates a gradient in cross-shelf mixing and larval transport, with cross-shelf mixing being more common on the northeastern end, episodic in the transitional middle area, and then becoming rare in the southwestern half of the region of the Gulf of Maine. As a result, the investigators predict that northeastern populations of mussels are seeded mostly from up-stream sources, while a significant component of self-seeding (local retention) exists in southwestern populations. Larvae settling in the intervening bays are expected to be derived from a mixture of local and up-stream sources. Using a combined empirical and theoretical approach hydrographic, current profile, and larval vertical migration data will be collected and used to develop and validate a high-resolution coastal circulation model coupled to a model of larval behavior. The investigators will model simulations in different years using the empirical data from mussel reproductive output and spawning times. Connectivity predicted from this model will be then tested against independent empirical estimates of connectivity based on trace element fingerprinting for larvae which can be connected to specific natal habitats. Regions of agreement and discrepancy in the model will be identified to guide additional data collection and model refinement. This iterative process will ensure an understanding of both larval transport patterns and processes, and provide estimates of inter-annual variability in connectivity for blue mussel populations in the Gulf of Maine.";
    String projects_0_end_date "2017-08";
    String projects_0_geolocation "Gulf of Maine: Frenchmen Bay (44 28.239 N -68 15.927 W) to Machais Bay (44 39.350 N -67 21.320 W)";
    String projects_0_name "An integrated theoretical and empirical approach to across-shelf mixing and connectivity of mussel populations";
    String projects_0_project_nid "527082";
    String projects_0_start_date "2013-09";
    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 "Blue mussel (Mytilus edulis) size frequency data from surveys conducted in coastal eastern Maine from 2014 to 2017.";
    String title "Blue mussel (Mytilus edulis) size frequency data from surveys conducted in coastal eastern Maine from 2014 to 2017 (MuLTI-2 project)";
    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.

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