ERDDAP at the APDRC
Easier access to scientific data

Make A Graph

Dataset Title:	Adak (51.867 -176.633 1950-2014) (Sea Level Time Series (HOURLY)) (OS UH-RQH040A 20160323 R)
Institution:	SOEST.HAWAII (Dataset ID: hawaii_soest_240c_6107_2661)
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)

depth (m)

specify just 1 value →

latitude (degrees_north)

specify just 1 value →

longitude (degrees_east)

specify just 1 value →

Graph Settings

Marker Type:

Size:

Color:

Color Bar: Continuity: Scale:

Min: Max: N Sections:

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)

Time range:

[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 -6.31152e+8, 1.420066799999712e+9;
    String axis "T";
    String calendar "gregorian";
    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";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.0, 0.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 51.867, 51.867;
    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 -176.633, -176.633;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  sea_surface_height_above_reference_level {
    Int16 _FillValue -32768;
    String ancillary_variables "sensor_type_code";
    Float64 colorBarMaximum 2.0;
    Float64 colorBarMinimum -2.0;
    String ioos_category "Sea Level";
    String long_name "Sea Level (HOURLY)";
    String standard_name "sea_surface_height";
    String units "millimeters";
  }
  sensor_type_code {
    Byte _FillValue 0;
    Float64 colorBarMaximum 8.0;
    Float64 colorBarMinimum 0.0;
    Byte flag_masks 7, 7, 7, 7;
    String flag_meanings "unknown float_gauge echo_sounder radar";
    Byte flag_values 1, 2, 3, 4;
    String ioos_category "Quality";
    String long_name "sensor type code";
    String standard_name "sensor_type_code status_flag";
    Byte valid_range 1, 4;
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String contact "xxxxxxxxxx@soest.hawaii.edu";
    String Conventions "CF-1.6, OceanSITES 1.2, TideGauge-0.2, COARDS, ACDD-1.3";
    String creator_email "xxxxxxxxxx@soest.hawaii.edu";
    String creator_name "XXXXXXXXXX";
    String creator_type "institution";
    String creator_url "https://uhslc.soest.hawaii.edu/thredds/dodsC/uhslc/rqh/OS_UH-RQH040A_20160323_R.html";
    String data_assembly_center "UHSLC";
    String date_created "14:47 23-03-2016";
    String date_updated "14:47 23-03-2016";
    Float64 Easternmost_Easting -176.633;
    String GCOS "true";
    String geolocated "false";
    Float64 geospatial_lat_max 51.867;
    Float64 geospatial_lat_min 51.867;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -176.633;
    Float64 geospatial_lon_min -176.633;
    String geospatial_lon_units "degrees_east";
    String history 
"2022-08-11T23:54:35Z https://uhslc.soest.hawaii.edu/thredds/dodsC/uhslc/rqh/OS_UH-RQH040A_20160323_R
2022-08-11T23:54:35Z http://apdrc.soest.hawaii.edu/griddap/hawaii_soest_240c_6107_2661.das";
    String id "OS_UH-RQH040A_20160323_R";
    String infoUrl "https://uhslc.soest.hawaii.edu/thredds/dodsC/uhslc/rqh/OS_UH-RQH040A_20160323_R.html";
    String institution "SOEST.HAWAII";
    String institution_references "http://uhslc.soest.hawaii.edu";
    String instrument_type "FLOAT GAUGE";
    String keywords 
"-176.633, 1950-2014, adak, code, data, depth, flag, height, hour, hourly,
latitude, level, longitude, ocean, oceans,
Oceans > Sea Surface Topography > Sea Surface Height,
quality, rqh040a, sea, sea level, sea_surface_height,
sea_surface_height_above_reference_level, sensor, sensor_type_code,
sensor_type_code status_flag, series, soest.hawaii, status, surface, time,
time series, topography, type, uh-rqh040a";
    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 naming_authority "OceanSITES";
    Float64 Northernmost_Northing 51.867;
    String pi_name "Mark Merrifield";
    String processing_level "Research Quality";
    String project "XXXXX";
    String publisher_email "xxxxxxxxxx@soest.hawaii.edu";
    String publisher_name "UHSLC (University of Hawaii Sea Level Center)";
    String publisher_type "group";
    String publisher_url "uhslc.soest.hawaii.edu";
    String quality_control_level "Research Quality";
    String quality_control_method 
"The quality assessment is mostly based on the residuals (observed data minus
predicted tides) of the hourly data. This assessment also applies to the
daily and monthly data since they were derived from the quality-controlled
hourly data.  The following corrections are made to the hourly data prior to
this assessment: 1) Gaps or obviously wrong data points in a span less than
25 hours are filled by the predicted tide method*. 2) Timing errors of exact
increments of an hour are corrected by shifting the data. 3) Reference level
shifts are only corrected after information from tide staff readings or
comparative readings with a fixed bench mark are checked to verify that the
shift was not a natural event.  If comparative readings are missing or
incomplete, comparisons of the data with nearby stations may warrant the
adjustment of some obvious shifts. 4) Data with unresolved datum shifts are
not disseminated. However, if sufficient time spans of data are available
before or after the year(s) with the unresolved shift(s), a subset of quality
assured data is made available.  Thus, the Span field in the Quality
Assessment may not match the span of the distribution data set.  As the
questionable datum shifts are resolved, the data set will be updated. 
Although this policy adds some complexity, it allows more rapid dissemination
of at least the quality assured years.  Note : If the predicted tides poorly
model the observed heights due to the inability of the tidal analysis to
completely resolve the non-linear shallow water effects, the residuals are
not (observed data minus predicted tides) of the hourly data. This assessment
also applies to the daily and monthly data since they were derived from the
quality-controlled hourly data.  *The predicted tides are obtained with the
use of a harmonic analysis program (Foreman, 1977) which is executed on a
year of apparently good data for a given station.  The Predicted Tide Method
for filling gaps consists of statistically comparing the predicted tides to
the observed data and shifting the predicted tides in time to correct for
timing differences.  Then the linear interpolation between hourly values at
the end points of the gap in the residual series is added to the
corresponding corrected predicted tide data to obtain interpolated values
over the span of the gap.";
    Float32 sea_level_data_reference_level 0.0;
    String service_date "YYYY-MM-DD";
    String sourceUrl "https://uhslc.soest.hawaii.edu/thredds/dodsC/uhslc/rqh/OS_UH-RQH040A_20160323_R";
    Float64 Southernmost_Northing 51.867;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String station_name "Adak";
    String summary "Sea Level Time Series (HOURLY) (Adak (51.867 -176.633 1950-2014))";
    String time_coverage_end "2014-12-31T23:00:00Z";
    String time_coverage_resolution "1hour";
    String time_coverage_start "1950-01-01T00:00:00Z";
    String time_zone "GMT-10:00";
    String title 
"Adak (51.867 -176.633 1950-2014) (Sea Level Time Series (HOURLY)) (OS
UH-RQH040A 20160323 R)";
    String TOGA_ID "40";
    Float64 Westernmost_Easting -176.633;
    String wmo_platform_code "not assigned yet";
  }
}

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
http://apdrc.soest.hawaii.edu/erddap/griddap/datasetID.fileType{?query}
For example,
http://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