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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Upwelling Index, 36N 122W, 6-hourly Subscribe RSS
Institution:  NOAA/SWFSC Environmental Research Division   (Dataset ID: erdUI366hr)
Range: longitude = -122.0 to -122.0°E, latitude = 36.0 to 36.0°N, time = 1967-01-01T00:00:00Z to 2018-10-31T18:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
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 ? )
    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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -9.46944e+7, 1.5410088e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "reference time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  upwelling_index {
    Float32 _FillValue -1.0e+34;
    Float32 actual_range -2890.214, 1693.164;
    String history "From transport";
    String ioos_category "Wind";
    String long_name "Upwelling Index";
    String long_name_mod "X=122W@ITP, Y=36N@ITP";
    Float32 missing_value -1.0e+34;
  }
  station_id {
    String cf_role "timeseries_id";
    String ioos_category "Other";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 36.0, 36.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -122.0, -122.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "latitude,longitude,station_id";
    String Conventions "CF-1.4, NCCSV-1.0";
    String defaultGraphQuery "time,upwelling_index&time>=now-5years&time<=now&.draw=lines";
    Float64 Easternmost_Easting -122.0;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 36.0;
    Float64 geospatial_lat_min 36.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -122.0;
    Float64 geospatial_lon_min -122.0;
    String geospatial_lon_units "degrees_east";
    String history 
"FERRET V6.72    4-Nov-18
2018-11-13T16:53:35Z (local files)
2018-11-13T16:53:35Z http://coastwatch.pfeg.noaa.gov/tabledap/erdUI366hr.das";
    String infoUrl "https://oceanview.pfeg.noaa.gov/LAS/docs/wind_from_pressure.nc.html";
    String institution "NOAA/SWFSC Environmental Research Division";
    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 36.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 36.0;
    String start_time "1946-01-15T00:00:00";
    String summary "Upwelling index computed from 1-degree FNMOC sea level pressure for 15 locations off the North American West Coast at each 3 degrees of latitude from 21N to 60N. The coastal Upwelling Index is an index of the strength of the wind forcing on the ocean which has been used in many studies of the effects of ocean variability on the reproductive and recruitment success of many fish and invertebrate species.";
    String time_coverage_end "2018-10-31T18:00:00Z";
    String time_coverage_start "1967-01-01T00:00:00Z";
    String title "Upwelling Index, 36N 122W, 6-hourly";
    Float64 Westernmost_Easting -122.0;
  }
}

 

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