Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Liquid Robotics Wave Glider, Honey Badger (G3), 2015, Telemetry Subscribe RSS
Institution:  Liquid Robotics, UT Austin, NOAA NMFS SWFSC ERD   (Dataset ID: LiquidR_HBG3_2015_telemetry)
Range: longitude = -156.054 to -144.8268°E, latitude = 19.996687 to 29.479773°N, time = 1999-11-30T00:00:00Z to 2015-11-04T18:50:05Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
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. ?
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 {
  vehicleName {
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "Vehicle Name";
  telemetry {
    String ioos_category "Location";
    String long_name "Telemetry";
  feed_version {
    Float32 actual_range 1.0, 1.0;
    String ioos_category "Other";
    String long_name "Feed Version";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.4392e+8, 1.446663005e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime";
    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";
    Float64 actual_range 19.996686666666665, 29.479771666666668;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 missing_value 0.0;
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -156.05400666666668, -144.82679166666668;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 missing_value 0.0;
    String standard_name "longitude";
    String units "degrees_east";
  distance_over_ground {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 32186;
    String ioos_category "Location";
    String long_name "Distance Over Ground";
    String units "m";
  desired_heading {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 999;
    String ioos_category "Location";
    String long_name "Desired Heading";
    String units "degrees";
  sub_heading {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 359;
    String ioos_category "Location";
    String long_name "Sub Heading";
    String units "degrees";
  target_waypoint {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 77;
    String ioos_category "Location";
    String long_name "Target Waypoint";
  sub_temperature {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 23, 48;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Sub Temperature";
    String units "degree_C";
  total_power {
    Int32 _FillValue 2147483647;
    Int32 actual_range 303050, 655350;
    String ioos_category "Other";
    String long_name "Total Power";
    String units "mWh";
  water_speed {
    Float32 actual_range 0.0, 1.858;
    Float64 colorBarMaximum 5.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Currents";
    String long_name "Water Speed";
    String units "knots";
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "vehicleName, telemetry, feed_version";
    String contributor_email "";
    String contributor_name "Liquid Robotics";
    String contributor_role "provided the glider time and all operational support";
    String contributor_url "";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "";
    String creator_name "Tracy Villareal";
    String creator_type "person";
    String creator_url "";
    String defaultGraphQuery "longitude,latitude,water_speed&time>=now-7days&time<=now&.draw=markers&.marker=1|5";
    Float64 Easternmost_Easting -144.82679166666668;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 29.479771666666668;
    Float64 geospatial_lat_min 19.996686666666665;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -144.82679166666668;
    Float64 geospatial_lon_min -156.05400666666668;
    String geospatial_lon_units "degrees_east";
    String history 
"A script frequently retrieves new data from Liquid Robotics' Data Portal and stores it in a file at NOAA NMFS SWFSC ERD. ( at
2020-12-04T02:53:12Z (local files)
    String infoUrl "";
    String institution "Liquid Robotics, UT Austin, NOAA NMFS SWFSC ERD";
    String keywords "2015, bloom, chlorophyll, currents, data, datetime, degrees, desired, desired_heading, diatom, distance, distance_over_ground, feed, feed_version, glider, ground, heading, Honey Badger, latitude, liquid, liquid robotics, local, longitude, MAGI, name, nitrogen-fixing, over, phytoplankton, power, robotics, source, speed, sub, sub_heading, sub_temperature, target, target_waypoint, telemetry, temperature, time, total, total_power, vehicle, vehicleName, version, water, water_speed, wave, wave glider, waypoint";
    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 29.479771666666668;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 19.996686666666665;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "vehicleName, telemetry, feed_version";
    String summary "Liquid Robotics Wave Glider, Honey Badger (G3), 2015, Telemetry. The MAGI mission is to use the Wave Glider to sample the late summer chlorophyll bloom that develops near 30°N, with the goal of using the camera and LISST-Holo to try to identify species in the blooms and then follow the development of phytoplankton aggregates. These aggregates have recently been shown to be a significant part of the total amount of carbon that sinks to the deep sea. Karl et al (2012) found that in each of the past 13 years, there was a flux of material to 4,000 m (the summer export pulse) that represented ~20% of the total annual flux. Work based on satellite ocean color data over the past decade has revealed the existence of large phytoplankton blooms in the Pacific Ocean that cover thousands of km2, persist for weeks or longer, and are often dominated by nitrogen-fixing diatom symbioses (Wilson et al. 2008). We hope to be able to examine whether this aggregation is occurring in the vast oceanic regions north and east of Hawai'i and provide a basin-scale context for the ALOHA observations. These events have proven difficult to study outside of the time series station ALOHA at Hawai'i.";
    String time_coverage_end "2015-11-04T18:50:05Z";
    String time_coverage_start "1999-11-30T00:00:00Z";
    String title "Liquid Robotics Wave Glider, Honey Badger (G3), 2015, Telemetry";
    Float64 Westernmost_Easting -156.05400666666668;


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