Make A Graph

Dataset Title:	FNMOC 500 mb Geopotential Height, 360x181, Monthly
Institution:	FNMOC, NOAA ERD (Dataset ID: erdlasFn500mb)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:
X Axis:
Y Axis:
Color:

Dimensions

Start

Stop

time (UTC)

specify just 1 value →

latitude (degrees_north)

longitude (degrees_east)

Graph Settings
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.)

Optional:
Then set the File Type: (File Type information)
and

or view the URL:
(Documentation / Bypass this form

)

Click on the map to specify a new center point.

Zoom:

[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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 8.992512e+8, 1.7251488e+9;
    String axis "T";
    String calendar "standard";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -90.0, 90.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 0.0, 359.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  z_mean {
    Float32 _FillValue -9999.0;
    Float64 colorBarMaximum 6000.0;
    Float64 colorBarMinimum 4500.0;
    String ioos_category "Pressure";
    String long_name "Geopotential height at 500mb";
    Float32 missing_value -9999.0;
    String units "gp";
  }
  NC_GLOBAL {
    String CDI "Climate Data Interface version ?? (https://code.mpimet.mpg.de/projects/cdi)";
    String cdm_data_type "Grid";
    String CDO "Climate Data Operators version 1.9.3 (https://code.mpimet.mpg.de/projects/cdo)";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 359.0;
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min -90.0;
    Float64 geospatial_lat_resolution 1.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 359.0;
    Float64 geospatial_lon_min 0.0;
    Float64 geospatial_lon_resolution 1.0;
    String geospatial_lon_units "degrees_east";
    String history 
"Wed Oct 02 15:18:09 2024: cdo mergetime /data/fnmoc/monthly_aves/backup/500mbaves.nc 500mbaves_test.nc 500mbaves_merged.nc
Wed Dec  1 19:16:38 2021: ncks -F -d time_series,,278 500mbaves.nc 500mbaves_truncated.nc
2024-10-09T04:21:05Z https://oceanview.pfeg.noaa.gov/thredds/dodsC/FNMOC/500mbaves.nc
2024-10-09T04:21:05Z https://coastwatch.pfeg.noaa.gov/griddap/erdlasFn500mb.das";
    String infoUrl "https://www.pfeg.noaa.gov/products/PFEL/modeled/500mb_height/500mb_height.html";
    String institution "FNMOC, NOAA ERD";
    String keywords "360x181, 500mb, erd, fnmoc, geopotential, height, monthly, noaa, pressure";
    String keywords_vocabulary "GCMD Science Keywords";
    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 NCO "4.4.2";
    Float64 Northernmost_Northing 90.0;
    String sourceUrl "https://oceanview.pfeg.noaa.gov/thredds/dodsC/FNMOC/500mbaves.nc";
    Float64 Southernmost_Northing -90.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary 
"Monthly means of the FNMOC (Fleet Numerical Meteorology and Oceanography Center) 6-hourly analyzed geopotential height field on a 360 by 181 global spherical grid (1 degree). For more information on the models used to compute these data please see:

Rosmond, T. E., 1992: A prototype fully coupled Ocean-Atmosphere Prediction System, Oceanography Vol. 5, No. 1, 25-30.

Clancy, R. M., 1992: Operational Modeling: Ocean Modeling at the Fleet Numerical Oceanography Center, Oceanography Vol. 5, No. 1, 31-35.

ERD was established at the U.S. Navy Fleet Numerical Meteorology and Oceanography Center (FNMOC) to take advantage of the Navy's global oceanographic and meteorological databases. FNMOC produces operational forecasts of the state of the atmosphere and the ocean several times daily and maintains archives of several important parameters, such as sea level pressure and temperature. ERD derives a number of well-known environmental data and index products which are routinely distributed to researchers at many state and federal laboratories, as well as to academic and international researchers.";
    String time_coverage_end "2024-09-01T00:00:00Z";
    String time_coverage_start "1998-07-01T00:00:00Z";
    String title "FNMOC 500 mb Geopotential Height, 360x181, Monthly";
    Float64 Westernmost_Easting 0.0;
  }
}

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its projection 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.

(easy) You can get data by using the dataset's Data Access Form. It makes the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.