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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Animals Subscribe RSS
Institution:  Ocean Tracking Network   (Dataset ID: otn_aat_animals)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.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: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
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 ? )
    [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 {
  animal_project_reference {
    String ioos_category "Identifier";
    String long_name "Animal Project Reference Code";
  }
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  animal_reference_id {
    String ioos_category "Identifier";
    String long_name "Animal Reference ID";
  }
  animal_guid {
    String ioos_category "Identifier";
    String long_name "Animal GUID";
  }
  vernacularname {
    String ioos_category "Taxonomy";
    String long_name "Vernacular Name";
  }
  scientificname {
    String ioos_category "Taxonomy";
    String long_name "Scientific Name";
  }
  taxonrank {
    String ioos_category "Taxonomy";
    String long_name "Taxonomic Rank";
  }
  aphiaid {
    String ioos_category "Identifier";
    String long_name "Aphia ID";
  }
  tsn {
    String ioos_category "Identifier";
    String long_name "TSN";
  }
  animal_origin {
    String ioos_category "Biology";
    String long_name "Animal Origin";
  }
  stock {
    String ioos_category "Biology";
    String long_name "Stock";
  }
  length {
    String ioos_category "Biology";
    String long_name "Length";
  }
  length_type {
    String ioos_category "Biology";
    String long_name "Length Type";
  }
  weight {
    String ioos_category "Biology";
    String long_name "Weight";
  }
  life_stage {
    String ioos_category "Biology";
    String long_name "Life Stage";
  }
  age {
    String ioos_category "Biology";
    String long_name "Age";
  }
  sex {
    String ioos_category "Biology";
    String long_name "Sex";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "AAT, Darwin Core, COARDS, CF-1.6, ACDD-1.3";
    String history 
"2024-11-06T01:19:37Z (source database)
2024-11-06T01:19:37Z https://members.oceantrack.org/tabledap/otn_aat_animals.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";
    String publisher_email "otndc@dal.ca";
    String publisher_name "OTN Data Centre";
    String publisher_url "http://members.oceantrack.org";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF-11";
    String summary "Animal morphology information for animals tracked via acoustic tag or other mechanism, for all publishable animals.";
    String title "Animals";
  }
}

 

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