NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Receivers Subscribe RSS
Institution:  Ocean Tracking Network   (Dataset ID: otn_aat_receivers)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 deployment_project_reference ?              
 datacenter_reference ?              
 deployment_id ?              
 deployment_guid ?              
 receiver_manufacturer ?              
 receiver_model ?              
 frequencies_monitored ?              
 receiver_coding_scheme ?              
 receiver_serial_number ?              
 latitude (degrees_north) ?          -49.36753    74.75011
  < slider >
 longitude (degrees_east) ?          -175.85747    148.82
  < slider >
 time (Deployment Datetime UTC, UTC) ?          2003-04-26T00:00:00Z    2017-05-17T00:00:00Z
  < slider >
 recovery_datetime_utc (UTC) ?              
 array_name ?              
 receiver_reference_type ?              
 receiver_reference_id ?              
 bottom_depth (m) ?              
 depth (Receiver Depth, m) ?              
 deployment_comments ?              
 deployed_by ?              
 expected_receiver_life ?              
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  deployment_project_reference {
    String ioos_category "Identifier";
    String long_name "Deployment Project Reference Code";
  }
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  deployment_id {
    String ioos_category "Identifier";
    String long_name "Deployment ID";
  }
  deployment_guid {
    String ioos_category "Identifier";
    String long_name "Deployment GUID";
  }
  receiver_manufacturer {
    String ioos_category "Unknown";
    String long_name "Receiver Manufacturer";
  }
  receiver_model {
    String ioos_category "Identifier";
    String long_name "Receiver Model";
  }
  frequencies_monitored {
    String ioos_category "Unknown";
    String long_name "Frequencies Monitored";
  }
  receiver_coding_scheme {
    String ioos_category "Unknown";
    String long_name "Receiver Coding Scheme";
  }
  receiver_serial_number {
    String ioos_category "Identifier";
    String long_name "Receiver Serial Number";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -49.36753, 74.75011;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Deployment Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -175.85747, 148.82;
    String axis "X";
    String ioos_category "Location";
    String long_name "Deployment Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0513152e+9, 1.4949792e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Deployment Datetime UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  recovery_datetime_utc {
    String ioos_category "Time";
    String long_name "Recovery Datetime UTC";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  array_name {
    String ioos_category "Identifier";
    String long_name "Array Name";
  }
  receiver_reference_type {
    String ioos_category "Identifier";
    String long_name "Receiver Reference Type";
  }
  receiver_reference_id {
    String ioos_category "Identifier";
    String long_name "Receiver Reference ID";
  }
  bottom_depth {
    String ioos_category "Location";
    String long_name "Bottom Depth";
    String units "m";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String axis "Z";
    String ioos_category "Location";
    String long_name "Receiver Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  deployment_comments {
    String ioos_category "Unknown";
    String long_name "Deployment Comments";
  }
  deployed_by {
    String ioos_category "Unknown";
    String long_name "Deployed By";
  }
  expected_receiver_life {
    String ioos_category "Unknown";
    String long_name "Expected Receiver Life";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "AAT, COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 148.82;
    Float64 geospatial_lat_max 74.75011;
    Float64 geospatial_lat_min -49.36753;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 148.82;
    Float64 geospatial_lon_min -175.85747;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-04-30T02:41:44Z (source database)
2024-04-30T02:41:44Z https://members.oceantrack.org/erddap/tabledap/otn_aat_receivers.html";
    String infoUrl "http://oceantrackingnetwork.org/";
    String institution "Ocean Tracking Network";
    String keywords "ACOUSTIC RECEIVERS, ACOUSTIC TAGS, Earth Science > Biological Classification > Animals/Vertebrates > Fish";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "By accessing or using OTN Data you agree to: a) give proper attribution to all Data Providers and to OTN by using the preformed citations contained in OTN metadata reports and in the data records, b) inform OTN of publications, products or commercial applications using the data, c) acknowledge that neither the OTN nor the provider is liable for inaccuracies in the data, d) assume responsibility for investigating and understanding the limitations of the data, e) report all problems with respect to data to otndc@dal.ca. For full policy, see: https://members.oceantrack.org/data/policies.";
    Float64 Northernmost_Northing 74.75011;
    String publisher_email "otndc@dal.ca";
    String publisher_name "OTN Data Centre";
    String publisher_url "http://members.oceantrack.org";
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing -49.36753;
    String standard_name_vocabulary "CF-11";
    String summary "Receivers.";
    String time_coverage_end "2017-05-17T00:00:00Z";
    String time_coverage_start "2003-04-26T00:00:00Z";
    String title "Receivers";
    Float64 Westernmost_Easting -175.85747;
  }
}

 

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