Make A Graph

Dataset Title:	NRL HYCOM+NCODA, GLBu0.08/expt 90.9, Global, 1/12 deg, 2012-2013, at Surface, Lon+/-180
Institution:	Naval Oceanographic Office (Dataset ID: nrlHycomGLBu008e909S_LonPM180)
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 1.3274496e+9, 1.3769568e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Valid Time";
    Int32 NAVO_code 13;
    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";
    Float64 actual_range -80.0, 80.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Int32 NAVO_code 1;
    String point_spacing "even";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -180.0, 179.9200439453125;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String modulo "360 degrees";
    Int32 NAVO_code 2;
    String standard_name "longitude";
    String units "degrees_east";
  }
  surf_el {
    String _CoordinateAxes "time lat lon";
    Float32 _FillValue -30.0;
    Float64 colorBarMaximum 2.0;
    Float64 colorBarMinimum -2.0;
    String ioos_category "Sea Level";
    String long_name "Water Surface Elevation";
    Float32 missing_value -30.0;
    Int32 NAVO_code 32;
    String standard_name "sea_surface_elevation";
    String units "m";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String classification_authority "not applicable";
    String classification_level "UNCLASSIFIED";
    String Conventions "CF-1.6, NAVO_netcdf_v1.0, COARDS, ACDD-1.3";
    String creator_email "hycomdata@coaps.fsu.edu";
    String creator_name "Naval Oceanographic Office";
    String creator_type "institution";
    String creator_url "https://www.hycom.org";
    String distribution_statement "Approved for public release. Distribution unlimited.";
    String downgrade_date "not applicable";
    Float64 Easternmost_Easting 179.9200439453125;
    String field_type "instantaneous";
    Float64 geospatial_lat_max 80.0;
    Float64 geospatial_lat_min -80.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 179.9200439453125;
    Float64 geospatial_lon_min -180.0;
    String geospatial_lon_units "degrees_east";
    String history 
"archv2ncdf2d
2024-11-05T00:06:46Z https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_90.9
2024-11-05T00:06:46Z https://coastwatch.pfeg.noaa.gov/griddap/nrlHycomGLBu008e909S_LonPM180.das";
    String infoUrl "https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_90.9.html";
    String institution "Naval Oceanographic Office";
    String keywords "data, glbu, naval, oceanographic, office, tau, tds.hycom.org, thredds, time";
    String license 
"Approved for public release. Distribution unlimited.
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 80.0;
    String source "HYCOM archive file";
    String sourceUrl "https://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_90.9";
    Float64 Southernmost_Northing -80.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "HYbrid Coordinate Ocean Model (HYCOM) + NCODA, GLBu0.08/expt 90.9, Global, 1/12 deg, from the U.S. Navy's Naval Research Laboratory (NRL). The hybrid coordinate is one that is isopycnal in the open, stratified ocean, but smoothly reverts to a terrain-following coordinate in shallow coastal regions, and to z-level coordinates in the mixed layer and/or unstratified seas. The hybrid coordinate extends the geographic range of applicability of traditional isopycnic coordinate circulation models (the basis of the present hybrid code), such as the Miami Isopycnic Coordinate Ocean Model (MICOM) and the Navy Layered Ocean Model (NLOM), toward shallow coastal seas and unstratified parts of the world ocean.";
    String time_coverage_end "2013-08-20T00:00:00Z";
    String time_coverage_start "2012-01-25T00:00:00Z";
    String title "NRL HYCOM+NCODA, GLBu0.08/expt 90.9, Global, 1/12 deg, 2012-2013, at Surface, Lon+/-180";
    Float64 Westernmost_Easting -180.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.