NERACOOS   ERDDAP
Easier access to realtime and historic NERACOOS buoy observations.
   
Brought to you by NOAA IOOS NERACOOS    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Hampton Harbor, NH Tide Gauge   RSS
Institution:  Onset Hobolink   (Dataset ID: ONSET_hamptonbay_hourly_water_level)
Range: longitude = -70.8185 to -70.8185°E, latitude = 42.9001 to 42.9001°N, time = 2019-09-25T17:00:00Z to 2023-09-17T12:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Station {
    String ioos_category "Identifier";
    String long_name "Station";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 42.9001, 42.9001;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -70.8185, -70.8185;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5694308e+9, 1.694952e+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";
  }
  Temp {
    Float64 actual_range -0.54, 22.94;
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "celsius";
  }
  MLLW_feet {
    Float64 actual_range -6.7603, 24.5444;
    String ioos_category "Unknown";
    String long_name "Mean Lower Low Level feet";
    String units "feet";
  }
  MLLW_meter {
    Float64 actual_range -2.06053944, 7.48113312;
    String ioos_category "Unknown";
    String long_name "Mean Low Low Water meters";
    String units "m";
  }
  MSL {
    Float64 actual_range -0.7525394399999998, 8.78913312;
    String ioos_category "Unknown";
    String long_name "Mean Sea Level";
    String units "m";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "[email protected]";
    String creator_name "Onset Hobolink";
    String creator_type "institution";
    String creator_url "http://hobolink.com";
    String defaultGraphQuery "time%2CMLLW_feet&time%3E=now-7day&.draw=lines&.color=0x000000&.bgColor=0xffffffff";
    Float64 Easternmost_Easting -70.8185;
    String featureType "Point";
    Float64 geospatial_lat_max 42.9001;
    Float64 geospatial_lat_min 42.9001;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -70.8185;
    Float64 geospatial_lon_min -70.8185;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-29T05:00:28Z (local files)
2024-03-29T05:00:28Z http://www.neracoos.org/tabledap/ONSET_hamptonbay_hourly_water_level.das";
    String infoUrl "http://hobolink.com";
    String institution "Onset Hobolink";
    String keywords "gauge, hampton, hobolink, mean, meter, mllw, MLLW_feet, MLLW_meter, msl, onset, sea, station, Temp, temperature, tide, water level";
    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 42.9001;
    String project "NERACOOS";
    String project_url "http://www.neracoos.org";
    String publisher_email "[email protected]";
    String publisher_phone "(603) 319 1785";
    String publisher_url "http://www.neracoos.org";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 42.9001;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Tide gauge located in Hampton Harbor, NH. Funded by NERACOOS.  Data is reported in elevation above MLLW (NAVD88) in feet and also converted to meters.  NOAA uses Mean Lower Low Water (MLLW), which is the average height of the lowest tide recorded at a tide station each day during a 19-year recording period, known as the National Tidal Datum Epoch.[5] MLLW is only a mean, so some tidal levels may be negative relative to MLLW; see also mean low water spring. The 19-year recording period is the nearest full year count to the 18.6-year cycle of the lunar node regression, which has an effect on tides.  At this location Mean Sea Level (MSL) is 1.308 meters above MLLW Benchmark used: NOAA Station ID: 8440452   - PLUM ISLAND, MERRIMACK  RIVER ENTRANCE (with extrapolated estimate) MSL meters = (MLLW ft. * 0.3048) + GAUGE location correction.";
    String testOutOfDate "now-1day";
    String time_coverage_end "2023-09-17T12:00:00Z";
    String time_coverage_start "2019-09-25T17:00:00Z";
    String title "Hampton Harbor, NH Tide Gauge";
    Float64 Westernmost_Easting -70.8185;
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection 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.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact