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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CTD profile data from 2014-2015 R/V C-HAWK MuLTI-2 project cruises in the Gulf
of Maine, Coastal eastern Maine, from Frenchman Bay to the Canadian border
  RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_614744)
Range: longitude = -68.27557 to -67.34469°E, latitude = 44.238716 to 44.661686°N, depth = 0.15 to 76.51m
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() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
  Deployment_Id {
    String description "MuLTI-2 Deployment Id";
    String ioos_category "Identifier";
    String long_name "Deployment Id";
    String units "text";
  }
  Transect_Id {
    String description "MuLTI-2 Transect Id";
    String ioos_category "Identifier";
    String long_name "Transect Id";
    String units "text";
  }
  Station_Id {
    String description "CTD Station Id";
    String ioos_category "Identifier";
    String long_name "Station Id";
    String units "text";
  }
  Date_UTC {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20140619, 20150828;
    String description "Date of CTD station (UTC) in the format�YYYYMMDD";
    String ioos_category "Time";
    String long_name "Date UTC";
    String units "unitless";
  }
  Time_UTC {
    Int32 _FillValue 2147483647;
    Int32 actual_range 101504, 230116;
    String description "Time of CTD station (UTC)";
    String ioos_category "Time";
    String long_name "Time UTC";
    String units "HHMMSS";
  }
  Date_Local {
    Int32 _FillValue 2147483647;
    Int32 actual_range 20140619, 20150828;
    String description "Date of CTD station (Local) in the format�YYYYMMDD.";
    String ioos_category "Time";
    String long_name "Date Local";
    String units "unitless";
  }
  Time_Local {
    String description "Time of CTD station (Local)";
    String ioos_category "Time";
    String long_name "Time Local";
    String units "HHMMSS";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 44.238717, 44.6616851;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "CTD Station start latitude (South is negative)";
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "Lat_Start";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -68.2755757, -67.3446914;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "CTD Station start longitude (West is negative)";
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "Lon_Start";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Lat_End {
    Float64 _FillValue NaN;
    Float64 actual_range 44.2384812, 44.6619048;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "CTD Station end latitude (South is negative)";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "decimal degrees";
  }
  Lon_End {
    Float64 _FillValue NaN;
    Float64 actual_range -68.2759392, -67.3443511;
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "CTD Station end longitude (West is negative)";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "decimal degrees";
  }
  Cast_Duration {
    Float32 _FillValue NaN;
    Float32 actual_range 29.0, 269.4;
    String description "CTD Cast duration";
    String ioos_category "Unknown";
    String long_name "Cast Duration";
    String units "seconds";
  }
  Pressure {
    Float32 _FillValue NaN;
    Float32 actual_range 0.15, 76.85;
    String description "Pressure";
    String ioos_category "Pressure";
    String long_name "Pressure";
    String units "decibars";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range 0.15, 76.51;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "Depth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Temperature {
    Float32 _FillValue NaN;
    Float32 actual_range 5.979, 24.0828;
    String description "Temperature";
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degrees Celsius";
  }
  Conductivity {
    Float64 _FillValue NaN;
    Float64 actual_range 27692.5156, 42532.7128;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum 30.0;
    String description "Conductivity";
    String ioos_category "Salinity";
    String long_name "Sea Water Electrical Conductivity";
    String units "MicroSiemens per Centimeter";
  }
  Specific_Conductance {
    Float64 _FillValue NaN;
    Float64 actual_range 30362.9758, 50852.37;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum 30.0;
    String description "Specific Conductance";
    String ioos_category "Salinity";
    String long_name "Sea Water Electrical Conductivity";
    String units "MicroSiemens per Centimeter";
  }
  Salinity {
    Float32 _FillValue NaN;
    Float32 actual_range 18.8091, 32.4152;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String description "Salinity";
    String ioos_category "Salinity";
    String long_name "Sea Water Practical Salinity";
    String units "PSU";
  }
  Sound_Velocity {
    Float32 _FillValue NaN;
    Float32 actual_range 1470.56, 1522.57;
    String description "Sound_Velocity";
    String ioos_category "Currents";
    String long_name "Sound Velocity";
    String units "meters/sec";
  }
  Density {
    Float64 _FillValue NaN;
    Float64 actual_range 1011.7008, 1025.2607;
    String description "Density";
    String ioos_category "Physical Oceanography";
    String long_name "Density";
    String units "kilograms/meter^3";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description 
"CTD casts at discrete stations located along transects.\\u00a0 Most transects
are oriented either across-shelf or along-shelf (one is a mixture).\\u00a0
Sampling was limited to 2 hrs. in the middle of the tidal cycle, on either
flood or ebb tides.\\u00a0 CTD was a YSI Castaway:
[www.sontek.com/productsdetail.php?CastAway-
CTD-11.\\u00a0](\\\\\"http://www.sontek.com/productsdetail.php?CastAway-
CTD-11.\\\\u00a0\\\\\") Calibration dates and additional information are supplied
in the headers of each data file.\\u00a0 Headers also contain coordinates of
the instrument at the start and stop of each cast.
 
Frenchman Bay is a long transect that had to broken into two with half run on
each cruise, in order to stay within our 2 hour tidal phase window.\\u00a0
Hence the renchman Bay cruises have an \\\"Upper\\\" vs. \\\"Lower\\\" designation,
but the station coordinates are continuous.\\u00a0 To accommodate weather
conditions and/or logistical delays, we did not consistently run the same set
of stations on each cruise designated \\\"Upper\\\" vs. \\\"Lower\\\" cruise, but the
designation indicates the general location of stations.";
    String awards_0_award_nid "527081";
    String awards_0_award_number "OCE-1334022";
    String awards_0_data_url "http://nsf.gov/awardsearch/showAward?AWD_ID=1334022";
    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 "Dr David  L. Garrison";
    String awards_0_program_manager_nid "50534";
    String awards_1_award_nid "527111";
    String awards_1_award_number "OCE-1333755";
    String awards_1_data_url "http://nsf.gov/awardsearch/showAward?AWD_ID=1333755";
    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 "Dr David  L. Garrison";
    String awards_1_program_manager_nid "50534";
    String awards_2_award_nid "527301";
    String awards_2_award_number "OCE-1333797";
    String awards_2_data_url "http://www.nsf.gov/awardsearch/showAward?AWD_ID=1333797&HistoricalAwards=false";
    String awards_2_funder_name "NSF Division of Ocean Sciences";
    String awards_2_funding_acronym "NSF OCE";
    String awards_2_funding_source_nid "355";
    String awards_2_program_manager "Dr David  L. Garrison";
    String awards_2_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"MuLTI-2 
  CTD - Downcasts 
  PIs: Yund, et al 
  Version: 29 October 2015 
 	 
  MuLTI-2 - Across Shelf";
    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.2d  13 Jun 2019";
    String date_created "2015-09-29T18:35:34Z";
    String date_modified "2019-06-13T17:54:58Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.614744.2";
    Float64 Easternmost_Easting -67.3446914;
    Float64 geospatial_lat_max 44.6616851;
    Float64 geospatial_lat_min 44.238717;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -67.3446914;
    Float64 geospatial_lon_min -68.2755757;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 76.51;
    Float64 geospatial_vertical_min 0.15;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2019-07-23T12:06:23Z (local files)
2019-07-23T12:06:23Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_614744.das";
    String infoUrl "https://www.bco-dmo.org/dataset/614744";
    String institution "BCO-DMO";
    String instruments_0_acronym "CTD";
    String instruments_0_dataset_instrument_description 
"YSI Castaway CTD
Device (2014 and 2015): CC1223007
2014 Calibration Information from headers in original .csv files:
Electronics calibration date,0001-01-01
Conductivity calibration date,2012-06-01
Temperature calibration date,2012-06-01
Pressure calibration date,2012-05-31
2015 Calibration Information from headers in original .csv files:
Electronics calibration date,0001-01-01
Conductivity calibration date,2015-02-19
Temperature calibration date,2015-02-19
Pressure calibration date,2015-02-16";
    String instruments_0_dataset_instrument_nid "614756";
    String instruments_0_description "The Conductivity, Temperature, Depth (CTD) unit is an integrated instrument package designed to measure the conductivity, temperature, and pressure (depth) of the water column.  The instrument is lowered via cable through the water column and permits scientists observe the physical properties in real time via a conducting cable connecting the CTD to a deck unit and computer on the ship. The CTD is often configured with additional optional sensors including fluorometers, transmissometers and/or  radiometers.  It is often combined with a Rosette of water sampling bottles (e.g. Niskin, GO-FLO) for collecting discrete water samples during the cast.  This instrument designation is used when specific make and model are not known.";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/130/";
    String instruments_0_instrument_name "CTD profiler";
    String instruments_0_instrument_nid "417";
    String instruments_0_supplied_name "YSI Castaway CTD";
    String instruments_1_acronym "GPS";
    String instruments_1_dataset_instrument_description "YSI Castaway CTD with internal GPS sensor";
    String instruments_1_dataset_instrument_nid "614755";
    String instruments_1_description "The Global Positioning System (GPS) is a U.S. space-based radionavigation system that provides reliable positioning, navigation, and timing services to civilian users on a continuous worldwide basis. The U.S. Air Force develops, maintains, and operates the space and control segments of the NAVSTAR GPS transmitter system. Ships use a variety of receivers (e.g. Trimble and Ashtech) to interpret the GPS signal and determine accurate latitude and longitude.";
    String instruments_1_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/POS03/";
    String instruments_1_instrument_name "Global Positioning System Receiver";
    String instruments_1_instrument_nid "560";
    String instruments_1_supplied_name "YSI Castaway CTD";
    String keywords "bco, bco-dmo, biological, cast, Cast_Duration, chemical, conductivity, currents, data, dataset, date, Date_Local, Date_UTC, density, deployment, Deployment_Id, depth, dmo, duration, earth, Earth Science > Oceans > Salinity/Density > Conductivity, Earth Science > Oceans > Salinity/Density > Salinity, electrical, erddap, identifier, Lat_End, latitude, local, Lon_End, longitude, management, ocean, oceanography, oceans, office, physical, physical oceanography, practical, preliminary, pressure, salinity, science, sea, sea_water_electrical_conductivity, sea_water_practical_salinity, seawater, sound, Sound_Velocity, Specific_Conductance, station, Station_Id, temperature, time, Time_Local, Time_UTC, transect, Transect_Id, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String metadata_source "https://www.bco-dmo.org/api/dataset/614744";
    Float64 Northernmost_Northing 44.6616851;
    String param_mapping "{'614744': {'Depth': 'flag - depth', 'Lon_Start': 'flag - longitude', 'Lat_Start': 'flag - latitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/614744/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 "Stephen R. Gegg";
    String people_2_person_nid "50910";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_role_type "related";
    String people_3_affiliation "Woods Hole Oceanographic Institution";
    String people_3_affiliation_acronym "WHOI BCO-DMO";
    String people_3_person_name "Amber York";
    String people_3_person_nid "643627";
    String people_3_role "BCO-DMO Data Manager";
    String people_3_role_type "related";
    String project "An integrated theoretical and empirical approach to across-shelf mixing and connectivity of mussel populations";
    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 "Stephen R. Gegg, Amber York";
    String publisher_role "BCO-DMO Data Manager(s)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.238717;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "CTD profile data from 2014-2015 R/V C-HAWK MuLTI-2 project cruises in the Gulf of Maine, Coastal eastern Maine, from Frenchman Bay to the Canadian border.";
    String title "CTD profile data from 2014-2015 R/V C-HAWK MuLTI-2 project cruises in the Gulf of Maine, Coastal eastern Maine, from Frenchman Bay to the Canadian border";
    String version "2";
    Float64 Westernmost_Easting -68.2755757;
    String xml_source "osprey2erddap.update_xml() v1.5-beta";
  }
}

 

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 1.82
Disclaimers | Privacy Policy | Contact