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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  NOS ATGM1 CO-OPS Tide Prediction, 6-minute Subscribe RSS
Institution:  NOAA NOS CO-OPS   (Dataset ID: NOS_ATGM1_WLTP6)
Range: longitude = -68.20428 to -68.20428°E, latitude = 44.392193 to 44.392193°N, time = 2023-04-01T00:06:00Z to 2026-01-01T23:54:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")
 
Graph Settings
Marker Type:   Size: 
Color: 
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: 
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 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";
  }
  shefID {
    String comment "A.K.A. NWS Location Identifier (NWSLI)";
    String ioos_category "Identifier";
    String long_name "SHEF ID";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -68.204278, -68.204278;
    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 44.392194, 44.392194;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.68030756e+9, 1.76731164e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String source_name "time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    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";
  }
  predictedWL {
    Float64 actual_range -0.601, 4.083;
    String ioos_category "Sea Level";
    String long_name "Predicted Water Level";
    String standard_name "sea_surface_height_amplitude_due_to_geocentric_ocean_tide";
    String units "m";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "stationID, stationName, state, shefID, 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 "https: tidesandcurrents.noaa.gov";
    Float64 Easternmost_Easting -68.204278;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 44.392194;
    Float64 geospatial_lat_min 44.392194;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -68.204278;
    Float64 geospatial_lon_min -68.204278;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-28T21:47:36Z https://opendap.co-ops.nos.noaa.gov/axis/webservices/currents/plain/response.jsp?metadata=yes
2024-12-28T21:47:36Z http://data.neracoos.org/tabledap/NOS_ATGM1_WLTP6.das";
    String infoUrl "https://tidesandcurrents.noaa.gov";
    String institution "NOAA NOS CO-OPS";
    String keywords "6-minute, amplitude, co-ops, coastal, Coastal Processes, data, datum, deployment, designation, Earth Science, geocentric, height, identifier, level, minute, name, noaa, nos, ocean, Oceans, oceans, ops, predicted, prediction, processes, sea, sea level, Sea Surface Height, Sea Surface Topography, sea_surface_height_amplitude_due_to_geocentric_ocean_tide, seawater, shef_id, shefID, station, surface, tidal, Tidal Height, tide, Tides, tides, time, topography, water";
    String license 
"\"These raw data have not been subjected to the National Ocean Services (NOS)
            Quality Control procedures, and do not necessarily meet the criteria and
            standards of official NOS data. They are released for limited public use with
            appropriate caution.

            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 44.392194;
    String publisher_email "info@neracoos.org";
    String publisher_name 
"Northeastern Regional Association of Coastal and Ocean Observing
            Systems (NERACOOS)";
    String publisher_phone "(603) 319 1785";
    String publisher_url "http://www.neracoos.org/";
    String sourceUrl "https://opendap.co-ops.nos.noaa.gov/axis/webservices/currents/plain/response.jsp?metadata=yes";
    Float64 Southernmost_Northing 44.392194;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "stationID, stationName, state, shefID, longitude, latitude, datum";
    String summary 
"This dataset has Mean Lower 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.";
    String time_coverage_end "2026-01-01T23:54:00Z";
    String time_coverage_start "2023-04-01T00:06:00Z";
    String title "NOS ATGM1 CO-OPS Tide Prediction, 6-minute";
    Float64 Westernmost_Easting -68.204278;
  }
}

 

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 2.24
Disclaimers | Privacy Policy | Contact