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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  North Pacific High, 1967 - present Subscribe RSS
Institution:  NOAA ERD   (Dataset ID: erdNph)
Range: longitude = 201.3 to 233.5°E, latitude = 23.3 to 39.3°N, time = 1967-01-16 to 2014-01-16
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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.33984e+7, 1.3898304e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Centered Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  year {
    Int16 actual_range 1967, 2014;
    String ioos_category "Time";
    String long_name "Year";
  month {
    Byte actual_range 1, 12;
    String ioos_category "Time";
    String long_name "Month (1 - 12)";
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 201.3, 233.5;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude of the Center of the NPH";
    String standard_name "longitude";
    String units "degrees_east";
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 23.3, 39.3;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude of the Center of the NPH";
    String standard_name "latitude";
    String units "degrees_north";
  area {
    Float32 actual_range 0.0, 7810500.0;
    String ioos_category "Pressure";
    String long_name "Areal Extent of the 1020 hPa Contour";
    String units "km2";
  maxSLP {
    Float32 actual_range 1016.7, 1033.3;
    String ioos_category "Pressure";
    String long_name "Maximum Sea Level Pressure";
    String units "hPa";
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String defaultDataQuery "time,year,month,longitude,latitude,area,maxSLP";
    String defaultGraphQuery "longitude,latitude,month&.draw=markers";
    Float64 Easternmost_Easting 233.5;
    String featureType "Point";
    Float64 geospatial_lat_max 39.3;
    Float64 geospatial_lat_min 23.3;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 233.5;
    Float64 geospatial_lon_min 201.3;
    String geospatial_lon_units "degrees_east";
    String history 
"2020-10-21T22:56:20Z (local files)
    String id "erdNph";
    String infoUrl "";
    String institution "NOAA ERD";
    String keywords "area, areal, california, ccs, center, centered, contour, current, data, extent, high, hpa, level, maximum, month, north, nph, pacific, pressure, sea, system, time, year";
    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.";
    Float64 Northernmost_Northing 39.3;
    String references "Schroeder, Isaac D., Bryan A. Black, William J. Sydeman, Steven J. Bograd, Elliott L. Hazen, Jarrod A. Santora, and Brian K. Wells. \"The North Pacific High and wintertime pre-conditioning of California current productivity\", Geophys. Res. Letters, VOL. 40, 541-546, doi:10.1002/grl.50100, 2013";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 23.3;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "time, year, month";
    String summary "Variations in large-scale atmospheric forcing influence upwelling dynamics and ecosystem productivity in the California Current System (CCS). In this paper, we characterize interannual variability of the North Pacific High over 40 years and investigate how variation in its amplitude and position affect upwelling and biology. We develop a winter upwelling \"pre-conditioning\" index and demonstrate its utility to understanding biological processes. Variation in the winter NPH can be well described by its areal extent and maximum pressure, which in turn is predictive of winter upwelling. Our winter pre-conditioning index explained 64% of the variation in biological responses (fish and seabirds). Understanding characteristics of the NPH in winter is therefore critical to predicting biological responses in the CCS.";
    String time_coverage_end "2014-01-16";
    String time_coverage_start "1967-01-16";
    String title "North Pacific High, 1967 - present";
    Float64 Westernmost_Easting 201.3;


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{?query}
For example,,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