NOAA ERDDAP
Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  NOS CO-OPS Water Level Data, High Low Tide Prediction Subscribe RSS
Institution:  NOAA NOS CO-OPS   (Dataset ID: nosCoopsWLTPHL)
Range: longitude = -177.36 to 167.7361°E, latitude = -14.2767 to 70.4114°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
   
- +
       
   
- +
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Color: 
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 ? )
    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 {
  stationID {
    String cf_role "timeseries_id";
    String comment "Queries for data MUST include \"stationID=\".";
    String ioos_category "Identifier";
    String long_name "Station ID";
  }
  stationName {
    String ioos_category "Identifier";
    String long_name "Station Name";
  }
  state {
    String ioos_category "Location";
    String long_name "State";
  }
  dateEstablished {
    Float64 actual_range -3.6757152e+9, 1.4979168e+9;
    String ioos_category "Time";
    String long_name "Date Established";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  shefID {
    String comment "A.K.A. NWS Location Identifier (NWSLI)";
    String ioos_category "Identifier";
    String long_name "SHEF ID";
  }
  deployment {
    String ioos_category "Identifier";
    String long_name "Deployment Designation";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -177.36, 167.7361;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -14.2767, 70.4114;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String comment "Queries for data MUST include \"time>=\" and \"time<=\".";
    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";
  }
  datum {
    String comment "This dataset only returns data with the MLLW (Mean Lower-Low Water) datum.";
    String ioos_category "Location";
    String long_name "Datum";
  }
  waterLevel {
    String ioos_category "Sea Level";
    String long_name "Water Level";
    String standard_name "sea_surface_height_amplitude_due_to_geocentric_ocean_tide";
    String units "m";
  }
  type {
    String comment "H=High water, L=Low water";
    String ioos_category "Sea Level";
    String long_name "Designation of Water Level Height";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "stationID, stationName, state, dateEstablished, shefID, deployment, longitude, latitude, datum";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "COOPS.IOOS@noaa.gov";
    String creator_name "NOAA NOS COOPS";
    String creator_type "institution";
    String creator_url "http://tidesandcurrents.noaa.gov/";
    String defaultDataQuery "&time%3E=now&time%3C=now+7days&stationName=%22San%20Francisco%22&datum=%22MLLW%22";
    String defaultGraphQuery "time,waterLevel&time%3E=now&time%3C=now+7days&stationName=%22San%20Francisco%22&datum=%22MLLW%22&.draw=lines";
    Float64 Easternmost_Easting 167.7361;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 70.4114;
    Float64 geospatial_lat_min -14.2767;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 167.7361;
    Float64 geospatial_lon_min -177.36;
    String geospatial_lon_units "degrees_east";
    String history 
"2018-04-25T16:31:34Z https://opendap.co-ops.nos.noaa.gov/axis/webservices/highlowtidepred/plain/response.jsp?unit=1&timeZone=1&datum=0&metadata=yes&Submit=Submit
2018-04-25T16:31:34Z http://coastwatch.pfeg.noaa.gov/tabledap/nosCoopsWLTPHL.das";
    String infoUrl "http://tidesandcurrents.noaa.gov/";
    String institution "NOAA NOS CO-OPS";
    String keywords "amplitude, co-ops, coastal, data, datum, deployment, designation, due, Earth Science > Oceans > Coastal Processes > Tidal Height, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, Earth Science > Oceans > Tides > Tidal Height, geocentric, height, high, identifier, level, low, name, noaa, nos, ocean, oceans, ops, prediction, processes, sea, sea level, sea_surface_height_amplitude_due_to_geocentric_ocean_tide, seawater, shef_id, shefID, station, surface, tidal, tide, tides, time, topography, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The official Tide and Tidal Current prediction tables are published annually on
October 1, for the following calendar year. Tide and Tidal Current predictions
generated prior to the publishing date of the official tables are subject to
change. The enclosed data are based upon the latest information available as of
the date of your request. Tide and Tidal Current predictions generated may
differ from the official predictions if information for the station requested
has been updated since the publishing date of the official tables.

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 70.4114;
    String sourceUrl "https://opendap.co-ops.nos.noaa.gov/axis/webservices/highlowtidepred/plain/response.jsp?unit=1&timeZone=1&datum=0&metadata=yes&Submit=Submit";
    Float64 Southernmost_Northing -14.2767;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "stationID, stationName, state, dateEstablished, shefID, deployment, longitude, latitude, datum";
    String summary 
"This dataset has High Low Tide Predictions from NOAA NOS Center for Operational
Oceanographic Products and Services (CO-OPS).

The official Tide and Tidal Current prediction tables are published annually on
October 1, for the following calendar year. Tide and Tidal Current predictions
generated prior to the publishing date of the official tables are subject to
change. The enclosed data are based upon the latest information available as of
the date of your request. Tide and Tidal Current predictions generated may
differ from the official predictions if information for the station requested
has been updated since the publishing date of the official tables.

WARNING:
* Queries for data MUST include stationID=, time>= and time<=.
  Queries MUST be for less than 30 days worth of data.
* This dataset only returns data for the MLLW (Mean Lower-Low Water) datum.
* The data source isn't completely reliable. If your request returns no data
  when you think it should:
  * Try revising the request (e.g., a different time range).
  * The list of stations offering this data may be incorrect.
  * Sometimes a station or the entire data service is unavailable.
    Wait a while and try again.";
    String title "NOS CO-OPS Water Level Data, High Low Tide Prediction";
    Float64 Westernmost_Easting -177.36;
  }
}

 

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