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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Project Attributes Subscribe RSS
Institution:  OTN   (Dataset ID: nodename_aat_project_attributes)
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 {
  project_reference {
    String ioos_category "Identifier";
    String long_name "Project Reference";
  }
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  project_name {
    String ioos_category "Identifier";
    String long_name "Project Name";
  }
  project_abstract {
    String ioos_category "Unknown";
    String long_name "Project Abstract";
  }
  project_citation {
    String ioos_category "Unknown";
    String long_name "Project Citation";
  }
  project_pi {
    String ioos_category "Unknown";
    String long_name "Project PI";
  }
  project_pi_organization {
    String ioos_category "Unknown";
    String long_name "Project PI Organization";
  }
  project_pi_contact {
    String ioos_category "Unknown";
    String long_name "Project PI Contact";
  }
  project_infourl {
    String ioos_category "Unknown";
    String long_name "Project Info URL";
  }
  project_keywords {
    String ioos_category "Unknown";
    String long_name "Project Keywords";
  }
  project_keywords_vocabulary {
    String ioos_category "Unknown";
    String long_name "Project Keywords Vocabulary";
  }
  project_references {
    String ioos_category "Unknown";
    String long_name "Project References";
  }
  project_doi {
    String ioos_category "Unknown";
    String long_name "Project Digital Object Identifier";
  }
  project_license {
    String ioos_category "Unknown";
    String long_name "Project License";
  }
  project_distribution_statement {
    String ioos_category "Unknown";
    String long_name "Project Distribution Statement";
  }
  project_date_modified {
    String ioos_category "Unknown";
    String long_name "Project Date Modified";
  }
  project_datum {
    String ioos_category "Unknown";
    String long_name "Project Datum";
  }
  project_geospatial_lon_min {
    String ioos_category "Location";
    String long_name "Project Geospatial Longitude Minimum";
  }
  project_geospatial_lon_max {
    String ioos_category "Location";
    String long_name "Project Geospatial Longitude Maximum";
  }
  project_geospatial_lat_min {
    String ioos_category "Location";
    String long_name "Project Geospatial Latitude Minimum";
  }
  project_geospatial_lat_max {
    String ioos_category "Location";
    String long_name "Project Geospatial Latitude Maximum";
  }
  project_linestring {
    String ioos_category "Unknown";
    String long_name "Project Linestring";
  }
  geospatial_vertical_min {
    String ioos_category "Unknown";
    String long_name "Geospatial Vertical Minimum";
  }
  geospatial_vertical_max {
    String ioos_category "Unknown";
    String long_name "Geospatial Vertical Maximum";
  }
  geospatial_vertical_positive {
    String ioos_category "Unknown";
    String long_name "Geospatial Vertical Positive";
  }
  project_time_coverage_start {
    String ioos_category "Unknown";
    String long_name "Project Time Coverage Start";
  }
  project_time_coverage_end {
    String ioos_category "Unknown";
    String long_name "Project Time Coverage End";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "???";
    String history 
"2024-11-14T19:39:36Z (source database)
2024-11-14T19:39:36Z http://erddap.factnetwork.secoora.org:80/tabledap/nodename_aat_project_attributes.das";
    String infoUrl "http://www.oceantrackingnetwork.org/";
    String institution "OTN";
    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 sourceUrl "(source database)";
    String summary "Project Attributes.";
    String title "Project Attributes";
  }
}

 

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