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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  MARES Marine Mammal Tagging and Tracking - eb03-057-15 - Moves Subscribe RSS
Institution:  University of Alaska Fairbanks, North Carolina State University, University of Nebraska-Lincoln   (Dataset ID: mares_2015_move_eb03-057-15)
Range: longitude = -168.924 to -155.342°E, latitude = 62.971 to 71.494°N, time = 2015-09-18T15:35:00Z to 2016-02-24T18:19:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
  trajectory {
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "trajectory identifier";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.4425905e+9, 1.45633794e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  z {
    Float64 _FillValue -9999.9;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum 0.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -9999.9;
    Float64 actual_range 62.971000000000004, 71.494;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -9999.9;
    Float64 actual_range -168.924, -155.342;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  ptt {
    Int32 _FillValue -9999;
    Int32 actual_range 150995, 150995;
    String ioos_category "Unknown";
    String long_name "PTT";
  }
  lq {
    Byte _FillValue -15;
    Byte actual_range -2, 3;
    String ioos_category "Unknown";
    String long_name "LQ";
  }
  alt_lat {
    Float64 _FillValue -9999.9;
    Float64 actual_range 62.971000000000004, 71.494;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Alternative latitude solution to position solution";
    String standard_name "latitude";
    String units "degrees_north";
  }
  alt_lon {
    Float64 _FillValue -9999.9;
    Float64 actual_range -176.576, -155.342;
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Alternative longitude solution to position solution";
    String standard_name "longitude";
    String units "degrees_east";
  }
  number_uplinks {
    Byte _FillValue -15;
    Byte actual_range 1, 13;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Number of uplinks received during satellite pass";
    String standard_name "number_uplinks";
  }
  number_uplinks_120 {
    Byte _FillValue -15;
    Byte actual_range 0, 4;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Number of uplinks received with signal strength > -120db";
    String standard_name "number_uplinks_signal_stength";
  }
  strongest_signal {
    Int16 _FillValue -9999;
    Int16 actual_range -140, -113;
    String ioos_category "Unknown";
    String long_name "Signal strength of strongest uplink";
    String standard_name "strongest_uplink_strength";
    String units "dB";
  }
  pass_duration {
    Int16 _FillValue -9999;
    Int16 actual_range 0, 776;
    String ioos_category "Unknown";
    String long_name "Duration of satellite overpass";
    String standard_name "satellite_pass_duration";
    String units "s";
  }
  frequency {
    Float64 _FillValue -9999.9;
    Float64 actual_range 4.016773325e+8, 4.016774444e+8;
    String ioos_category "Unknown";
    String long_name "Frequency of SRDL signal at the satellite";
    String standard_name "measured_frequency_signal";
    String units "Hz";
  }
  v_mask {
    Float64 _FillValue -9999.9;
    Float64 actual_range -1.0, 20.0;
    Float64 colorBarMaximum 150.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Identifier";
    String long_name "V Mask";
  }
  estimated_speed {
    Float64 _FillValue -9999.9;
    Float64 actual_range -1.0, 7.22;
    String ioos_category "Currents";
    String long_name "Speed across the surface";
    String standard_name "estimated_speed";
    String units "m.s-1";
  }
  iq {
    Byte _FillValue -15;
    Byte actual_range 0, 68;
    Float64 colorBarMaximum 150.0;
    Float64 colorBarMinimum 0.0;
    String comment "see Argos documentation for a complete explanation";
    String ioos_category "Quality";
    String long_name "A two-digit code which gives further information about the location calculation";
    String standard_name "iq";
  }
  deleted {
    String comment "Normally used to remove a very poor position occurring at the beginning of the track";
    String ioos_category "Location";
    String long_name "'Y' causes this position to be ignored in location filtering";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "trajectory";
    String contributor "Rowenna Gryba";
    String Conventions "CF-1.6, ACDD-1.3, COARDS";
    String creator_email "jordan@axiomdatascience.com";
    String creator_name "Jordan Jenckes - Axiom Data Science";
    String creator_url "http://www.axiomdatascience.com/";
    String date_created "2017-06-06T13:44:05Z";
    Float64 Easternmost_Easting -155.342;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 71.494;
    Float64 geospatial_lat_min 62.971000000000004;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -155.342;
    Float64 geospatial_lon_min -168.924;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String history 
"NetCDF generated by Axiom from Move CSV files on MARES Research Workspace
2018-02-25T11:49:00Z (local files)
2018-02-25T11:49:00Z http://erddap.aoos.org/tabledap/mares_2015_move_eb03-057-15.das";
    String id "move_eb03-057-15";
    String infoUrl "http://www.smru.st-and.ac.uk/protected/eb03/eb03.html";
    String institution "University of Alaska Fairbanks,  North Carolina State University, University of Nebraska-Lincoln";
    String keywords "-120, about, across, algorithm, along, alt_lat, alt_lon, alternative, argos, axiomdatascience, beginning, calculation, causes, code, complete, crs, currents, data, deleted, depth, diagno, digit, documentation, duration, during, estimated, estimated_speed, explanation, filtering, frequency, further, gives, greater, here, identifier, ignored, information, latitude, locations, longitude, mask, measured, measured_frequency_signal, normally, number, number_uplinks, number_uplinks_120, number_uplinks_signal_stength, obs, observations, occurring, ongitude, overpass, pass, pass_duration, poor, position, ptt, quality, received, record, remove, satellite, satellite_pass_duration, see, signal, solution, speed, srdl, statistics, stength, strength, strongest, strongest_signal, strongest_uplink_strength, surface, than, time, track, trajectory, two, two-digit, uplink, uplinks, used, v, v_mask, value, very, which, with";
    String license "Data available for public use. All data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness, no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.";
    String metadata_link "http://www.smru.st-and.ac.uk/protected/eb03/eb03.html";
    String naming_authority "uk.ac.st-andrews.smru";
    Float64 Northernmost_Northing 71.494;
    String project "MARES";
    String references "Gryba, R. D., F. K. Wiese, B. P. Kelly. 2017. MARES Pilot Program Marine Mammal Tagging and Tracking: Satellite data from CTD-fluorometry tags deployed on spotted and bearded seals, Beaufort and Chukchi Seas, August 2015 - February 2016. OCS Study BOEM 2017-017.";
    String sea_name "Beaufort Sea, Chukchi Sea";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 62.971000000000004;
    String standard_name_vocabulary "CF Standard Name Table v27";
    String subsetVariables "trajectory, number_uplinks, number_uplinks_120, iq, deleted";
    String summary "MARES Pilot Program: Marine Mammal Tagging and Tracking; Satellite data from CTD-fluorometry tags deployed on spotted and bearded seals, Beaufort and Chukchi Seas, August 2015 - February 2016";
    String time_coverage_end "2016-02-24T18:19:00Z";
    String time_coverage_start "2015-09-18T15:35:00Z";
    String title "MARES Marine Mammal Tagging and Tracking - eb03-057-15 - Moves";
    Float64 Westernmost_Easting -168.924;
  }
}

 

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 1.82_axiom-r1
Disclaimers | Privacy Policy | Contact