Easier access to realtime and historic NERACOOS buoy observations.
Brought to you by NOAA IOOS NERACOOS    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  eMOLT Haul Bottom Temperature   RSS
Institution:  NOAA's Northeast Fisheries Science Center and the Gulf of Maine Lobster Foundation   (Dataset ID: nefsc_emolt_trawl_temp)
Range: longitude = -76.3783 to 44.67564°E, latitude = -31.52031 to 44.65695°N, depth = 0.0 to 960.0m, time = 2015-06-13T13:03:00Z to 2020-12-22T18:23:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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 {
  id {
    Int16 actual_range 0, 13338;
    String description "NEFSC database unique record id";
    String ioos_category "Identifier";
    String long_name "NEFSC Database Id";
  vessel {
    String description "Vessel Identifier";
    String ioos_category "Identifier";
    String long_name "Vessel Identifier";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.43420058e+9, 1.60866138e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datet";
    String source_name "datet";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -31.52031, 44.65695;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -76.3783, 44.67564;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.0, 960.0;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  depth_range {
    Float32 actual_range 0.0, 980.0;
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Other";
    String long_name "Depth";
    String standard_name "depth";
  hours {
    Float32 actual_range 0.0, 947.0;
    String ioos_category "Time";
    String long_name "Hours";
    String units "hours";
  mean_temp {
    Float32 actual_range 0.0, 29.8;
    String ioos_category "Temperature";
    String long_name "Mean Temperature";
    String units "celsius";
  std_temp {
    Float32 actual_range 0.0, 520.0;
    String ioos_category "Temperature";
    String long_name "Temperature Standard Deviation";
    String units "celsius";
  flag {
    Byte actual_range 0, 5;
    Float64 colorBarMaximum 150.0;
    Float64 colorBarMinimum 0.0;
    String description "flag = 0 good,flag = 1 near dock (ie test cast),flag=2 bad temperature outside [0 30] degC,flag=3 depth out of range [10 500] meters,flag=4 bottom depth not near (<15% different)  NGDC bottom depth";
    String ioos_category "Quality";
    String long_name "Flag";
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "";
    String creator_name "Jim Manning";
    String defaultGraphQuery "longitude,latitude,mean_temp&.draw=markers&.marker=5%7C5&.color=0x000000&.colorBar=%7C%7C%7C%7C%7C&.bgColor=0xffffffff";
    Float64 Easternmost_Easting 44.67564;
    String featureType "Point";
    Float64 geospatial_lat_max 44.65695;
    Float64 geospatial_lat_min -31.52031;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 44.67564;
    Float64 geospatial_lon_min -76.3783;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 960.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
    String infoUrl "";
    String institution "NOAA's Northeast Fisheries Science Center and the Gulf of Maine Lobster Foundation";
    String keywords "data, depth, depth_range, flag, hours, latitude, longitude, mean, mean_temp, salinity, salinity-temperature-depth, std, std_temp, temperature, time, vessel";
    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.";
    Float64 Northernmost_Northing 44.65695;
    String sourceUrl "";
    Float64 Southernmost_Northing -31.52031;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "vessel,flag";
    String summary "The Environmental Monitors on Lobster Traps and Large Trawlers (eMOLT) project is a collaboration of fishing industry, NOAA, and academics devoted to monitoring of the physical environment of the Gulf of Maine and the Southern New England shelf. In a series of NOAA-related funding beginning in 2001 including a) Northeast Consortium, b) NEFSC's Northeast Cooperative Research Program, and, most recently, c) IOOS-Ocean Technology Transition Program,  we developed low-cost strategies to measure bottom temperature, salinity, and current velocity with the help of over 100 fixed and mobile gear fishermen dispersed along the entire New England coast. The current system utilizes a wireless water temperature & depth sensor on the gear, a micro-computer with a screen in the wheelhouse, and deck-mounted satellite transmitter in order to get bottom temperatures in real-time as fishermen haul their gear. The objective in the long run is to routinely assimilate this data into numerical ocean models in both hindcast and forecast modes.";
    String testOutOfDate "now-1day";
    String time_coverage_end "2020-12-22T18:23:00Z";
    String time_coverage_start "2015-06-13T13:03:00Z";
    String title "eMOLT Haul Bottom Temperature";
    Float64 Westernmost_Easting -76.3783;


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{?query}
For example,,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