GLERL ERDDAP
Easier access to scientific data
   
Brought to you by NOAA GLERL CoastWatch Great Lakes Node    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Great Lakes Long Term Average Surface Water Temperature, Daily Subscribe RSS
Institution:  NOAA GLERL   (Dataset ID: glerlLTAvgTemp)
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
   
- +
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Color: 
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 ? )
    [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 {
  lake {
    String comment "h=Huron, o=Ontario, m=Michigan, e=Erie, s=Superior";
    String ioos_category "Location";
    String long_name "Lake";
  }
  dayOfYear {
    Int16 actual_range 1, 366;
    String ioos_category "Time";
    String long_name "Day of Year";
    String units "count";
  }
  temperature {
    Float32 actual_range 0.871364, 23.8213;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Surface Temperature";
    String units "degrees_C";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "cw.glerl@noaa.gov";
    String creator_name "NOAA GLERL";
    String creator_url "https://coastwatch.glerl.noaa.gov";
    String defaultGraphQuery "dayOfYear,temperature&.draw=lines&lake=\"s\"";
    String history 
"2018-11-18T00:28:27Z http://coastwatch.glerl.noaa.gov/statistic/statistic.html
2018-11-18T00:28:27Z http://coastwatch.glerl.noaa.gov/tabledap/glerlLTAvgTemp.das";
    String infoUrl "https://coastwatch.glerl.noaa.gov/statistic/statistic.html";
    String institution "NOAA GLERL";
    String keywords "average, daily, data, day, environmental, erie, glerl, great, great lakes, huron, laboratory, lake, lakes, long, michigan, noaa, ontario, research, superior, surface, temperature, term, water";
    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 "http://coastwatch.glerl.noaa.gov/statistic/statistic.html";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "lake";
    String summary "Great Lakes long term average surface water temperature, daily.";
    String title "Great Lakes Long Term Average Surface Water Temperature, Daily";
  }
}

 

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