ERDDAP at the APDRC
Easier access to scientific data

Make A Graph

Dataset Title:	Model output HYCOM ESPC-D-V02 hycom ESPC-D-V02 a0 s3z
Institution:	APDRC (Dataset ID: hawaii_soest_f79d_0ff9_ef21)
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 : Show advanced settings : Privacy / Content settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Internet Explorer: "Tools : Internet Options : Security : Internet : Custom level :
          Sripting/ Active Scripting : Enable : OK : OK"
      • 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 →

LEV (meters)

specify just 1 value →

latitude (degrees_north)

longitude (degrees_east)

Graph Settings
Color Bar: Continuity: Scale:
Min: Max: N Sections:
Draw the land mask:
Y Axis Minimum: Maximum:

(Please be patient. It may take a while to get the data.)

Optional:
Then set the File Type: and

or view the URL:
(Documentation / Bypass this form

) (File Type information)

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.723248e+9, 1.7671392e+9;
    String axis "T";
    String calendar "GREGORIAN";
    String direction "L";
    String ioos_category "Time";
    String long_name "Time";
    String point_spacing "even";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  LEV {
    Float64 actual_range 0.0, 5000.0;
    String axis "Z";
    String direction "K";
    String ioos_category "Location";
    String long_name "altitude";
    String name "Depth";
    String point_spacing "uneven";
    String positive "down";
    String standard_name "depth";
    String units "meters";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -80.0, 90.0;
    String axis "Y";
    String direction "J";
    String ioos_category "Location";
    String long_name "Latitude";
    String point_spacing "uneven";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 0.0, 359.92004394531;
    String axis "X";
    String direction "I";
    String ioos_category "Location";
    String long_name "Longitude";
    String point_spacing "uneven";
    String standard_name "longitude";
    String units "degrees_east";
  }
  salinity {
    Float32 _FillValue -30000.0;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String direction "IJKL";
    String ioos_category "Salinity";
    String long_name "salinity [psu]";
    Float32 missing_value -30000.0;
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "forum@hycom.org";
    String creator_name "APDRC";
    String creator_type "institution";
    String creator_url "https://hycom.org/";
    Float64 Easternmost_Easting 359.92004394531;
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min -80.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 359.92004394531;
    Float64 geospatial_lon_min 0.0;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-02T21:50:36Z http://apdrc.soest.hawaii.edu/thredds/dodsC/las/hycom_ESPC-D-V02_a0_ts3z/data_apdrc.soest.hawaii.edu_80_dods_public_data_Model_output_HYCOM_ESPC-D-V02_hycom_ESPC-D-V02_a0_s3z.jnl
2025-05-02T21:50:36Z http://apdrc.soest.hawaii.edu/griddap/hawaii_soest_f79d_0ff9_ef21.das";
    String infoUrl "http://apdrc.soest.hawaii.edu/thredds/dodsC/las/hycom_ESPC-D-V02_a0_ts3z/data_apdrc.soest.hawaii.edu_80_dods_public_data_Model_output_HYCOM_ESPC-D-V02_hycom_ESPC-D-V02_a0_s3z.jnl.html";
    String institution "APDRC";
    String keywords 
"apdrc.soest.hawaii.edu, coordinate, data, density, dods, earth, espc,
espc-d-v02, hawaii, hybrid, hycom, latitude, LEV, longitude, model, ocean,
oceans,
Oceans > Salinity/Density > Salinity,
output, practical, psu, public, s3z, salinity, school, science, sea,
sea_water_practical_salinity, seawater, soest, technology, time, unit, v02,
water";
    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.";
    Float64 Northernmost_Northing 90.0;
    String sourceUrl "http://apdrc.soest.hawaii.edu/thredds/dodsC/las/hycom_ESPC-D-V02_a0_ts3z/data_apdrc.soest.hawaii.edu_80_dods_public_data_Model_output_HYCOM_ESPC-D-V02_hycom_ESPC-D-V02_a0_s3z.jnl";
    Float64 Southernmost_Northing -80.0;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"Model output HYbrid Coordinate Ocean Model (HYCOM) ESPC-D-V02 hycom
ESPC-D-V02 a0 s3z";
    String time_coverage_end "2025-12-31T00:00:00Z";
    String time_coverage_start "2024-08-10T00:00:00Z";
    String title "Model output HYCOM ESPC-D-V02 hycom ESPC-D-V02 a0 s3z";
    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://apdrc.soest.hawaii.edu/erddap/griddap/datasetID.fileType{?query}
For example,
https://apdrc.soest.hawaii.edu/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2015-06-09T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a variable name (e.g., analysed_sst),
followed by a set of [] for each of the variable's dimensions
(for example, [time][latitude][longitude]),
with your desired (start):stride:(stop) values within each [].

For details, see the griddap Documentation.

ERDDAP, Version 1.80
Disclaimers | Privacy Policy | Contact