NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  RMI Eco-glider Telemetry Receiver Detections From MATOS Subscribe RSS
Institution:  Rutgers University   (Dataset ID: matos_rmiglider_receiverdetections)
Range: longitude = -74.48585 to -72.76539°E, latitude = 38.76555 to 40.37269°N, time = 2023-06-15T00:00:00Z to 2025-10-26T00:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | 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: 
Time range:    |<   -       
[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 {
  station {
    String description "combination of MATOS project name, MATOS deployment name, and MATOS detection ID";
    String ioos_category "Identifier";
    String long_name "Station";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6867872e+9, 1.7614368e+9;
    String axis "T";
    String calendar "gregorian";
    String description "date the detection information was last modified in the MATOS database";
    String ioos_category "Time";
    String long_name "Date Last Modified";
    String source_name "dateLastModified";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  dateCollectedUTC {
    Float64 actual_range 1.682008829e+9, 1.743175397e+9;
    String calendar "gregorian";
    String description "time the tag detection occurred";
    String ioos_category "Time";
    String long_name "Date Collected UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  tagName {
    String description "ID of tag that was detected by receiver";
    String ioos_category "Unknown";
    String long_name "Tag Name";
  }
  receiverSerial {
    Float64 _FillValue 9223372036854775807;
    Float64 actual_range 457137, 1564555;
    String description "serial number of receiver that had detection";
    String ioos_category "Unknown";
    String long_name "Receiver Serial";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -74.48585, -72.76539;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "decimalLongitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 38.76555, 40.37269;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "decimalLatitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  trackerCode {
    String description "MATOS project ID for tag detected";
    String ioos_category "Unknown";
    String long_name "Tracker Code";
  }
  contactPOC {
    String description "MATOS contact information for point of contact for tag detected";
    String ioos_category "Ocean Color";
    String long_name "Contact POC";
  }
  contactPI {
    String description "MATOS contact information for principal investigator for tag detected";
    String ioos_category "Identifier";
    String long_name "Contact PI";
  }
  receiverType {
    String description "type of receiver that made detection";
    String ioos_category "Unknown";
    String long_name "Receiver Type";
  }
  matosProject {
    String description "MATOS project ID for receiver";
    String ioos_category "Identifier";
    String long_name "Matos Project";
  }
  matosDeployment {
    String description "MATOS deployment ID for receiver";
    String ioos_category "Unknown";
    String long_name "Matos Deployment";
  }
  ruDeployment {
    String description "name of deployment in RUCOOL system; this name will match deployments shared in slocum-data.marine.rutgers.edu";
    String ioos_category "Unknown";
    String long_name "Ru Deployment";
  }
  ruContactPI {
    String description "name of contact PI in RUCOOL system; only included given permission to share publicly";
    String ioos_category "Identifier";
    String long_name "Ru Contact PI";
  }
  ruContactPOC {
    String description "name of contact POC in RUCOOL system; only included given permission to share publicly";
    String ioos_category "Ocean Color";
    String long_name "Ru Contact POC";
  }
  ruSpecies {
    String description "species information (or platform, if transmitter is on board glider, receiver array, etc) from RUCOOL system; only included given permission to share publicly";
    String ioos_category "Taxonomy";
    String long_name "Ru Species";
  }
  vmtTransmitter {
    String description "tag ID that this receiver is transmiting as";
    String ioos_category "Unknown";
    String long_name "Vmt Transmitter";
  }
 }
  NC_GLOBAL {
    String acknowledgement "These deployments are supported by the New Jersey Research and Monitoring Initiative (RMI) (New Jersey Department of Environmental Protection, New Jersey Board of Public Utilities)";
    String cdm_data_type "Point";
    String contributor_name "Grace Saba, Josh Kohut, Dave Aragon, Nicole Waite, Brian Buckingham, John Kerfoot, Lori Garzio, Laura Nazzaro";
    String contributor_role "Principal Investigator, Principal Investigator, Glider Pilot, Glider Pilot, Glider Pilot, Data Management, Data Management, Data Management";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "ecosystemdata at marine.rutgers.edu";
    String creator_institution "Rutgers University";
    String creator_name "Rutgers Center for Ocean Observing Leadership Ecosystem Data Team";
    String creator_type "group";
    String creator_url "https://rucool.marine.rutgers.edu";
    Float64 Easternmost_Easting -72.76539;
    String featureType "Point";
    String geospatial_bounds_crs "EPSG:4326";
    Float64 geospatial_lat_max 40.37269;
    Float64 geospatial_lat_min 38.76555;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -72.76539;
    Float64 geospatial_lon_min -74.48585;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-12-16T18:03:26Z (local files)
2025-12-16T18:03:26Z https://rowlrs-data.marine.rutgers.edu/tabledap/matos_rmiglider_receiverdetections.das";
    String id "matos_rmiglider_receiverdetections";
    String infoUrl "https://rucool.marine.rutgers.edu";
    String institution "Rutgers University";
    String instrument "Vemco Mobile Transceiver (VMT) and Innovasea Rx-LIVE";
    String keywords "code, collected, color, conductivity, contact, contactPI, contactPOC, ctd, data, date, dateCollectedUTC, deployment, depth, detections, eco, eco-glider, glider, identifier, latitude, longitude, matos, matosDeployment, matosProject, modified, name, ocean, ocean color, poc, project, receiver, receiverSerial, receiverType, rmi, ruContactPI, ruContactPOC, ruDeployment, ruSpecies, rutgers, serial, sonde, species, station, tag, tagName, taxonomy, telemetry, temperature, time, tracker, trackerCode, transmitter, type, university, vmt, vmtTransmitter";
    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 40.37269;
    String platform "Slocum glider";
    String program "An ecological and oceanographic monitoring program to inform offshore wind related research over the coastal continental shelf of New Jersey";
    String project "RMI Eco-gliders";
    String publisher_email "ecosystemdata at marine.rutgers.edu";
    String publisher_institution "Rutgers University";
    String references "https://rucool.marine.rutgers.edu, https://matos.asascience.com";
    String sea_name "Mid-Atlantic Bight";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 38.76555;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "station, matosProject";
    String summary "This project is conducting seasonal surveys with a pair of gliders deployed in each season with a full complement of available sensors to simultaneously map oceanographic and ecological variables. Gliders are equipped with some subset of a Conductivity, Temperature, Depth (CTD) sensor, a pH sensor, a WETLabs FLBBCD ECO puck configured for simultaneous chlorophyll fluorescence and optical backscatter measurements, an Acoustic Zooplankton Fish Profiler (AZFP) multi-frequency echo sounder for active acoustic detection of pelagic organisms (transducers configured for either fish or zooplankton), a DMON hydrophone for detection of marine mammals, and a Vemco VMT or Innovasea Rx-LIVE fish telemetry receiver to track tagged species moving through the region. This dataset includes VMT and Rx-LIVE detections returned by MATOS for this project, which has a new data merge 3-4 times annually. Oceanographic data is shared at https://slocum-data.marine.rutgers.edu, AZFP data is shared at https://rowlrs-data.marine.rutgers.edu, and real-time marine mammal detections are shared at https://robots4whales.whoi.edu/.";
    String testOutOfDate "now-101days";
    String time_coverage_end "2025-10-26T00:00:00Z";
    String time_coverage_start "2023-06-15T00:00:00Z";
    String title "RMI Eco-glider Telemetry Receiver Detections From MATOS";
    Float64 Westernmost_Easting -74.48585;
  }
}

 

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