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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Animal Telemetry Network (ATN) Subscribe RSS
Institution:  Animal Telemetry Network   (Dataset ID: gtoppAT)
Range: longitude = 0.01 to 359.971°E, latitude = -77.868 to 77.193°N, time = 2002-06-30T13:53:16Z to 2018-02-21T07:18: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 {
  commonName {
    String ioos_category "Taxonomy";
    String long_name "Common Name";
  }
  yearDeployed {
    Int32 actual_range 1995, 9999;
    String ioos_category "Time";
    String long_name "Year Deployed";
  }
  project {
    Int32 actual_range 0, 1;
    String description 
"Project:
0=TOPPP - 'TOPP Partner' species
1=GTOPP - 'TOPP' designated species
2=TAGAG - 'TagAGiant'
5=CMRCL - commercial species";
    String ioos_category "Identifier";
    String long_name "Project";
  }
  toppID {
    String cf_role "trajectory_id";
    String comment "This ID is unique to a given tagged animal.";
    String ioos_category "Identifier";
    String long_name "TOPP ID (unique)";
  }
  serialNumber {
    String comment "Tags were reused, so this is not a unique identifier.";
    String ioos_category "Identifier";
    String long_name "The Tag's Serial Number (not unique)";
  }
  isDrifter {
    Int32 actual_range 0, 1;
    String comment "0=no, 1=yes=tag popped off animal then drifted";
    String ioos_category "Other";
    String long_name "Is Drifter?";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0254451968e+9, 1.51919748e+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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue -1.0e+34;
    Float32 actual_range 0.01, 359.971;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    Float32 missing_value -1.0e+34;
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 _FillValue -1.0e+34;
    Float32 actual_range -77.868, 77.193;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Float32 missing_value -1.0e+34;
    String standard_name "latitude";
    String units "degrees_north";
  }
  LC {
    String comment "Quality codes from the ARGOS satellite (in meters): 0,A,B,Z=no claim, 1=1000m, 2=350m, 3=150m. See http://www.aoml.noaa.gov/phod/dac/loc-rep.html";
    String ioos_category "Quality";
    String long_name "Location Quality Code";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "commonName, yearDeployed, project, toppID, serialNumber, isDrifter";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    String creator_email "Lynn.Dewitt@noaa.gov";
    Float64 Easternmost_Easting 359.971;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 77.193;
    Float64 geospatial_lat_min -77.868;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 359.971;
    Float64 geospatial_lon_min 0.01;
    String geospatial_lon_units "degrees_east";
    String history 
"Provided daily by ATN to Pacific Fisheries Environmental Lab Reformatted by Lynn Dewitt (Lynn.Dewitt@noaa.gov)
2018-02-22T04:13:14Z (local files)
2018-02-22T04:13:14Z https://oceanview.pfeg.noaa.gov/erddap/tabledap/gtoppAT.das
2018-02-26T03:34:02Z (local files)
2018-02-26T03:34:02Z http://coastwatch.pfeg.noaa.gov/tabledap/gtoppAT.das";
    String infoUrl "http://gtopp.org/";
    String institution "Animal Telemetry Network";
    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.";
    String Metadata_Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    Float64 Northernmost_Northing 77.193;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -77.868;
    String standard_name_vocabulary "CF-12";
    String subsetVariables "commonName, yearDeployed, project, toppID, serialNumber, isDrifter";
    String summary "These data (updated daily) are from the Animal Telemetry Network (ATN) program.  Begun as one of the field projects in the international Census of Marine Life, the Pacific-focused TOPP (Tagging of Pacific Predators) program was an international multidisciplinary collaboration of more than 75 scientists from 7 nations.  Over the decade beginning in 2000, TOPP researchers deployed more than 4,300 electronic tags on 23 different species of marine animals - yielding a dataset of more than 335,000 tracking days. To learn more please visit https://oceanview.pfeg.noaa.gov/ATN.";
    String time_coverage_end "2018-02-21T07:18:00Z";
    String time_coverage_start "2002-06-30T13:53:16Z";
    String title "Animal Telemetry Network (ATN)";
    Float64 Westernmost_Easting 0.01;
  }
}

 

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