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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD station locations for 2010 and 2011 R/V Llyr cruises, Downeast Maine (44.
1N 68.1W 44.9N. 66.9W), Saco Bay, Maine (43.45N 70.33W, 43.47N 70.28W) (MuLTI
project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_3419)
Range: longitude = -70.33037 to -66.92126°E, latitude = 43.45326 to 44.98148°N
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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
[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 {
  Year {
    Int16 _FillValue 32767;
    Int16 actual_range 2010, 2011;
    String bcodmo_name "year";
    String description "Year of data collection in the format YYYY";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "unitless";
  }
  deployment {
    String bcodmo_name "cruise_id";
    String description "Deployment Id";
    String long_name "Deployment";
    String units "text";
  }
  dataset_name {
    String bcodmo_name "dataset_id";
    String description "Dataset Name";
    String long_name "Dataset Name";
    String units "text";
  }
  sta_id {
    String bcodmo_name "sta_id";
    String description "Station Id";
    String long_name "Sta Id";
    String units "text";
  }
  location {
    String bcodmo_name "sample_descrip";
    String description "General Station Location";
    String long_name "Location";
    String units "text";
  }
  date {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20100606, 20110830;
    String bcodmo_name "date";
    String description "date (GMT) in the format yyyymmdd";
    String long_name "Date";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/ADATAA01/";
    String units "unitless";
  }
  time2 {
    String bcodmo_name "time";
    String description "time(GMT)";
    String long_name "Time";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/AHMSAA01/";
    String units "hhmmss";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -70.33037, -66.92126;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "longitude (West 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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 43.45326, 44.98148;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "latitude (South is negative)";
    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";
  }
  dataset_description {
    String bcodmo_name "sample_descrip";
    String description "General Description of Dataset";
    String long_name "Dataset Description";
    String units "text";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description "Generated from dataset metadata forms submitted by Charles Tilburg";
    String awards_0_award_nid "54750";
    String awards_0_award_number "OCE-0961157";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0961157";
    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 awards_1_award_nid "517490";
    String awards_1_award_number "OCE-1233868";
    String awards_1_data_url "http://www.nsf.gov/awardsearch/showAward?AWD_ID=1233868&HistoricalAwards=false";
    String awards_1_funder_name "NSF Division of Ocean Sciences";
    String awards_1_funding_acronym "NSF OCE";
    String awards_1_funding_source_nid "355";
    String awards_1_program_manager "David L. Garrison";
    String awards_1_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"MuLTI 
  Multiple year CTD Station Locations 
  version: 08 December 2011 
  PIs: Yund, Tilburg 
  
  
  MuLTI 2010 - CTD Station Locations";
    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 "2011-02-08T17:49:22Z";
    String date_modified "2020-01-03T17:18:58Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.3419.1";
    Float64 Easternmost_Easting -66.92126;
    Float64 geospatial_lat_max 44.98148;
    Float64 geospatial_lat_min 43.45326;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -66.92126;
    Float64 geospatial_lon_min -70.33037;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-28T16:47:52Z (local files)
2024-03-28T16:47:52Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_3419.das";
    String infoUrl "https://www.bco-dmo.org/dataset/3419";
    String institution "BCO-DMO";
    String instruments_0_acronym "CTD SBE 19";
    String instruments_0_dataset_instrument_description 
"HardwareData DeviceType='SBE19plus' SerialNumber='01906084'
Manufacturer Sea-Bird Electronics, Inc.
FirmwareVersion 2.0c
FirmwareDate 20 February 2008 14:10
PCBAssembly PCBSerialNum='not assigned' AssemblyNum='41054F'
PCBAssembly PCBSerialNum='not assigned' AssemblyNum='41580A'
PCBAssembly PCBSerialNum='not assigned' AssemblyNum='41056F'
PCBAssembly PCBSerialNum='not assigned' AssemblyNum='41059D'
MfgDate 11 JUN 2008";
    String instruments_0_dataset_instrument_nid "5346";
    String instruments_0_description "The Sea-Bird SBE 19 SEACAT Recorder measures conductivity, temperature, and pressure (depth).  The SEACAT is self-powered and self-contained and can be deployed in profiling or moored mode. The SBE 19 SEACAT was replaced in 2001 by the 19plus. more information from Sea-Bird Electronics";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L22/current/TOOL0042/";
    String instruments_0_instrument_name "CTD Sea-Bird SEACAT 19";
    String instruments_0_instrument_nid "420";
    String instruments_0_supplied_name "CTD Sea-Bird SEACAT 19";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, dataset_description, dataset_name, date, deployment, description, dmo, erddap, latitude, longitude, management, name, oceanography, office, preliminary, sta, sta_id, time, time2, year";
    String license "https://www.bco-dmo.org/dataset/3419/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/3419";
    Float64 Northernmost_Northing 44.98148;
    String param_mapping "{'3419': {'lat': 'master - latitude', 'lon': 'master - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/3419/parameters";
    String people_0_affiliation "University of New England - Marine Science Center";
    String people_0_affiliation_acronym "UNE-MSC";
    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 "University of New England - Marine Science Center";
    String people_1_affiliation_acronym "UNE-MSC";
    String people_1_person_name "Dr Charles  E. Tilburg";
    String people_1_person_nid "51155";
    String people_1_role "Co-Principal Investigator";
    String people_1_role_type "originator";
    String people_2_affiliation "University of New England - Marine Science Center";
    String people_2_affiliation_acronym "UNE-MSC";
    String people_2_person_name "Dr Charles  E. Tilburg";
    String people_2_person_nid "51155";
    String people_2_role "Contact";
    String people_2_role_type "related";
    String people_3_affiliation "University of New England - Marine Science Center";
    String people_3_affiliation_acronym "UNE-MSC";
    String people_3_person_name "Dr Philip O. Yund";
    String people_3_person_nid "51154";
    String people_3_role "Contact";
    String people_3_role_type "related";
    String people_4_affiliation "Woods Hole Oceanographic Institution";
    String people_4_affiliation_acronym "WHOI BCO-DMO";
    String people_4_person_name "Stephen R. Gegg";
    String people_4_person_nid "50910";
    String people_4_role "BCO-DMO Data Manager";
    String people_4_role_type "related";
    String project "MuLTI";
    String projects_0_acronym "MuLTI";
    String projects_0_description 
"Collaborative Research: Does larval transport or physiological tolerance set the southern range boundary of a northern blue mussel?
Acronym \"MuLTI\" (Mussel Larval Transport Initiative)
This project will test whether the southern range boundary of a northern blue mussel, Mytilus trossulus, is determined by limitations on the dispersal of larvae, or the physiological tolerance of larvae and/or juveniles. Mytilus trossulus and its sister species, M. edulis, co-occur throughout the Canadian maritime provinces and the northern Gulf of Maine. While the abundance of M. trossulus decreases abruptly south of the Canadian border, M. edulis ranges south to North Carolina. Work to date has demonstrated that:
1) Adult M. trossulus in northeastern Maine inhabit coastal sites, islands, and man-made structures that are within the colder water of the Eastern Maine Coastal Current (EMCC).
2) Drifters released in the EMCC rarely enter nearshore waters to the south, suggesting that across-shelf transport is extremely limited.
3) Larvae of the two species may differ slightly in thermal tolerance, and some evidence suggests that tolerance may also be affected by nutritional status.
4) Mytilus trossulus juveniles transplanted within the northeastern Maine region, but outside of the EMCC, have high survivorship, while transplants further to the southwest suffer high mortality.
In combination, these results suggest that larval transport sets the proximate range boundary within northeastern Maine (on a scale of 10 km), but thermal tolerance would ultimately limit the distribution on a larger spatial scale (200 km).
We will test this pair of hypotheses via a combination of field and lab experiments. Satellite drifters equipped with temperature loggers deployed in and out of the EMCC during the season of M. trossulus larval dispersal (mid-June to mid-August) will be used to quantify the physical flow fields and temperature regimes during larval dispersal. Drogues will allow us to assess whether larvae at different depths may experience different flow fields. Data from hydrographic surveys, combined with regular spatial and temporal sampling of mussel larvae and new settlers, will be used to assess possible associations between larval and post-settlement stages and different water masses. The physiological tolerance of new settlers will be assayed via transplants to sites in and out of the EMCC. Finally, laboratory growth and survival experiments will assay larval performance in different thermal and feeding regimes. We will use molecular markers to identify the morphologically indistinguishable larvae and settlers of these sibling species.";
    String projects_0_end_date "2012-12";
    String projects_0_geolocation "Downeast Maine, 44.1°N, 68.1°W – 44.9°N. 66.9°W and Saco Bay, Maine, 43.45°N, 70.33°W – 43.47°N. 70.28°W";
    String projects_0_name "Does larval transport or physiological tolerance set the southern range boundary of a northern blue mussel?";
    String projects_0_project_nid "2138";
    String projects_0_start_date "2010-06";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.45326;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "CTD station locations for 2010 and 2011 R/V Llyr cruises, Downeast Maine (44.1N 68.1W 44.9N. 66.9W), Saco Bay, Maine (43.45N 70.33W, 43.47N 70.28W).";
    String title "CTD station locations for 2010 and 2011 R/V Llyr cruises, Downeast Maine (44.1N 68.1W 44.9N. 66.9W), Saco Bay, Maine (43.45N 70.33W, 43.47N 70.28W) (MuLTI project)";
    String version "1";
    Float64 Westernmost_Easting -70.33037;
    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