ERDDAP > griddap > Data Access Form

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

 

Dimensions	Start	Stride	Stop	Size	Spacing
time (UTC)				309	30 days 10h 31m 10s (uneven)
latitude (degrees_north)				181	1.0 (even)
longitude (degrees_east)				360	1.0 (even)

Grid Variables (which always also download all of the dimension variables)

z_mean (Geopotential height at 500mb, gp)

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriAscii - Download an ISO-8859-1 ESRI ASCII file (latitude longitude data only; longitude must be all below or all above 180). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .graph - View a Make A Graph web page. .help - View a web page with a description of griddap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each axis variable and each data variable becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncml - View the dataset's structure and metadata as a UTF-8 NCML .xml file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download time,latitude,longitude,otherVariables as an ODV Generic Spreadsheet File (.txt). .timeGaps - View a UTF-8 list of gaps in the time values which are larger than the median gap. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .geotif - View a grayscale GeoTIFF .tif file (for latitude longitude data; longitude must be all below or all above 180). .kml - View a Google Earth .kml file (for latitude, longitude data only). .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form)
 
Submit (Please be patient. It may take a while to get the data.)

 

---

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 8.992512e+8, 1.7092512e+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";
  }
  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";
    String units "gp";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    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 Dec  1 19:16:38 2021: ncks -F -d time_series,,278 500mbaves.nc 500mbaves_truncated.nc
2024-04-16T12:22:25Z https://oceanview.pfeg.noaa.gov/thredds/dodsC/FNMOC/500mbaves.nc
2024-04-16T12:22:25Z http://coastwatch.pfeg.noaa.gov/erddap/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-03-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 Data Access Protocol (DAP) and its projection constraints.

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.

 

---

ERDDAP, Version 2.23
Disclaimers | Privacy Policy | Contact