Make A Graph

Dataset Title:	Tag Releases
Institution:	Ocean Tracking Network (Dataset ID: otn_aat_tag_releases)
Range:	longitude = -123.75632 to -61.96656°E, latitude = 38.21098 to 63.73828°N, time = 2006-05-04T23:00:00Z to 2016-09-19T00:00:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form

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 {
  release_project_reference {
    String ioos_category "Identifier";
    String long_name "Release Project Reference Code";
  }
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  tag_device_id {
    String ioos_category "Identifier";
    String long_name "Tag Device ID";
  }
  release_guid {
    String ioos_category "Identifier";
    String long_name "Release GUID";
  }
  release_reference_id {
    String ioos_category "Identifier";
    String long_name "Release Reference ID";
  }
  release_reference_type {
    String ioos_category "Unknown";
    String long_name "Release Reference Type";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 38.210979, 63.73828;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Release Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -123.756319284439, -61.96656;
    String axis "X";
    String ioos_category "Location";
    String long_name "Release Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.1467836e+9, 1.4742432e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Release Datetime UTC";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  expected_enddate {
    String ioos_category "Time";
    String long_name "Expected Enddate";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  manufacturer {
    String ioos_category "Unknown";
    String long_name "Manufacturer";
  }
  tag_model {
    String ioos_category "Identifier";
    String long_name "Tag Model";
  }
  tag_serial_number {
    String ioos_category "Identifier";
    String long_name "Tag Serial Number";
  }
  tag_frequency {
    String ioos_category "Unknown";
    String long_name "Tag Frequency";
  }
  tag_coding_system {
    String ioos_category "Unknown";
    String long_name "Tag Coding System";
  }
  transmitted_id {
    String ioos_category "Identifier";
    String long_name "Transmitted ID";
  }
  transmittername {
    String ioos_category "Identifier";
    String long_name "Transmittername";
  }
  transmitter_type {
    String ioos_category "Unknown";
    String long_name "Transmitter Type";
  }
  tag_programming_id {
    String ioos_category "Identifier";
    String long_name "Tag Programming ID";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "AAT, COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting -61.96656;
    Float64 geospatial_lat_max 63.73828;
    Float64 geospatial_lat_min 38.210979;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -61.96656;
    Float64 geospatial_lon_min -123.756319284439;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-30T02:54:58Z (source database)
2024-04-30T02:54:58Z https://members.oceantrack.org/tabledap/otn_aat_tag_releases.das";
    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 63.73828;
    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 38.210979;
    String standard_name_vocabulary "CF-11";
    String summary "Tag Releases.";
    String time_coverage_end "2016-09-19T00:00:00Z";
    String time_coverage_start "2006-05-04T23:00:00Z";
    String title "Tag Releases";
    Float64 Westernmost_Easting -123.756319284439;
  }
}

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