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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Nino Region Weekly SST OISST.v2 Subscribe RSS
Institution:  NCEP   (Dataset ID: ncepNinoSSTwk)
Range: time = 1990-01-03T00:00:00Z to 2018-01-10T00:00:00Z
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() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 6.313248e+8, 1.5155424e+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";
  }
  Nino1_2_sst {
    Float32 actual_range 18.3, 29.2;
    String ioos_category "Temperature";
    String long_name "Nino1+2 SST";
    String units "degrees C";
  }
  Nino1_2_ssta {
    Float32 actual_range -2.4, 4.6;
    String ioos_category "Temperature";
    String long_name "Nino1+2 SST Anomaly";
    String units "degrees C";
  }
  Nino3_sst {
    Float32 actual_range 23.0, 29.4;
    String ioos_category "Temperature";
    String long_name "Nino3 SST";
    String units "degrees C";
  }
  Nino3_ssta {
    Float32 actual_range -2.1, 3.7;
    String ioos_category "Temperature";
    String long_name "Nino3 SST Anomaly";
    String units "degrees C";
  }
  Nino34_sst {
    Float32 actual_range 24.4, 29.7;
    String ioos_category "Temperature";
    String long_name "Nino3.4 SST";
    String units "degrees C";
  }
  Nino34_ssta {
    Float32 actual_range -2.2, 3.1;
    String ioos_category "Temperature";
    String long_name "Nino3.4 SST Anomaly";
    String units "degrees C";
  }
  Nino4_sst {
    Float32 actual_range 26.2, 30.4;
    String ioos_category "Temperature";
    String long_name "Nino4 SST";
    String units "degrees C";
  }
  Nino4_ssta {
    Float32 actual_range -2.0, 1.8;
    String ioos_category "Temperature";
    String long_name "Nino4 SST Anomaly";
    String units "degrees C";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0, NCCSV-1.0";
    String creator_email "Lynn.Dewitt@noaa.gov";
    String defaultGraphQuery "time,Nino1_2_sst,Nino1_2_ssta&time>=now-5years&.draw=linesAndMarkers";
    String history 
"2018-01-18T03:45:53Z (local files)
2018-01-18T03:45:53Z https://oceanview.pfeg.noaa.gov/erddap/tabledap/ncepNinoSSTwk.das
2018-01-19T09:17:18Z (local files)
2018-01-19T09:17:18Z http://coastwatch.pfeg.noaa.gov/tabledap/ncepNinoSSTwk.das";
    String infoUrl "http://www.cpc.ncep.noaa.gov/data/indices/";
    String institution "NCEP";
    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";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF-12";
    String summary "Weekly OISST.v2 (1981-2010 base period) Niño 1+2 (0-10°South)(90°West-80°West) Niño 3 (5°North-5°South)(150°West-90°West) Niño 4 (5°North-5°South) (160°East-150°West) Niño 3.4 (5°North-5°South)(170-120°West)";
    String time_coverage_end "2018-01-10T00:00:00Z";
    String time_coverage_start "1990-01-03T00:00:00Z";
    String title "Nino Region Weekly SST OISST.v2";
  }
}

 

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