ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD

Make A Graph

Dataset Title:	Telemetry Receiver Detections (MATOS) OW1
Institution:	Rutgers University (Dataset ID: matos_ow1_receiverdetections)
Range:	longitude = -74.24731 to -74.06984°E, latitude = 39.09081 to 39.25705°N, time = 2022-07-11T12:02:31Z to 2023-10-12T17:32:37Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  index {
    Float64 _FillValue 9223372036854775807;
    Float64 actual_range 0, 443;
    String ioos_category "Unknown";
    String long_name "Index";
  }
  dateLastModified {
    Float64 actual_range 1.6765056e+9, 1.7086464e+9;
    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 standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.657540951e+9, 1.697131957e+9;
    String axis "T";
    String calendar "gregorian";
    String description "time the tag detection occurred";
    String ioos_category "Time";
    String long_name "Time";
    String source_name "dateCollectedUTC";
    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 138718, 487699;
    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.24731, -74.06984;
    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 39.09081, 39.25705;
    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";
  }
  collectionCode {
    String description "combination of regional network and MATOS project code";
    String ioos_category "Unknown";
    String long_name "Collection Code";
  }
  institutionCode {
    String description "institution of receiver owner";
    String ioos_category "Unknown";
    String long_name "Institution Code";
  }
 }
  NC_GLOBAL {
    String acknowledgement "Funding provided by Orsted.";
    String cdm_data_type "Point";
    String contributor_name "Thomas Grothues, Douglas Zemeckis, Chase Wunder, Kaycee Coleman, Laura Nazzaro";
    String contributor_role "Principal Investigator, Principal Investigator, Technician and Student, Project Manager, 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, rowlrs.marine.rutgers.edu";
    Float64 Easternmost_Easting -74.06984;
    String featureType "Point";
    String geospatial_bounds_crs "EPSG:4326";
    Float64 geospatial_lat_max 39.25705;
    Float64 geospatial_lat_min 39.09081;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -74.06984;
    Float64 geospatial_lon_min -74.24731;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-12-23T04:06:15Z (local files)
2025-12-23T04:06:15Z https://rowlrs-data.marine.rutgers.edu/tabledap/matos_ow1_receiverdetections.das";
    String id "matos_ow1_receiverdetections";
    String infoUrl "https://rucool.marine.rutgers.edu";
    String institution "Rutgers University";
    String instrument "VR2W, VR2Tx";
    String keywords "code, collection, collectionCode, color, contact, contactPI, contactPOC, data, date, dateLastModified, detections, identifier, index, institution, institutionCode, latitude, longitude, matos, modified, name, ocean, ocean color, ow1, poc, receiver, receiverSerial, rutgers, serial, tag, tagName, telemetry, time, tracker, trackerCode, university";
    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 39.25705;
    String program "Ocean Wind 01 Fisheries Monitoring Plan";
    String project "Ocean Wind 01 Fisheries Monitoring Plan, Telemetry Network";
    String publisher_email "ecosystemdata at marine.rutgers.edu";
    String publisher_institution "Rutgers University";
    String references "https://rucool.marine.rutgers.edu, rowlrs.marine.rutgers.edu, https://matos.asascience.com";
    String sea_name "Mid-Atlantic Bight";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.09081;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "trackerCode, contactPOC, contactPI, collectionCode, institutionCode";
    String summary "Fisheries Monitoring in Ocean Wind 01. The objectives of this study are to use passive acoustic telemetry to provide measures of behavior related to fish passage, residence, habitat use, and connectivity between Ocean Wind leasing area and coastal estuaries. Tagging efforts focused on smooth dogfish and skates, summer flounder, windowpane, and black sea bass. Specimens were tagged within the study area using V13 tags. Black sea bass were externally tagged while all other species had transmitters surgically implanted. Receivers included VR2W and VR2Tx and were deployed both as a static array (collectionCode ACT.RUMFSWIND) and during brief periods of sampling at stations during the Structured Habitat Survey portion of this Fisheries Management Plan (collectionCode ACT.SHS3974). This dataset includes detections by receivers funded by the Orsted OW01 of tags/transmitters funded as part of the same project. Tag info is shared in a separate dataset on rowlrs-data.marine.rutgers.edu/erddap.";
    String time_coverage_end "2023-10-12T17:32:37Z";
    String time_coverage_start "2022-07-11T12:02:31Z";
    String title "Telemetry Receiver Detections (MATOS) OW1";
    Float64 Westernmost_Easting -74.24731;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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