Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  St. John's Tide Station Subscribe RSS
Institution:  MI   (Dataset ID: SMA_st_johns_wharf)
Range: longitude = -52.69221 to -52.6922°E, latitude = 47.5689 to 47.5689°N, time = 2014-05-22T10:41:35Z to 2021-09-15T16:44:54Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
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 {
  year {
    UInt16 _FillValue 65535;
    UInt16 actual_range 2014, 2021;
    String ioos_category "Other";
    String long_name "Year";
    String units "1";
  station_name {
    String _Encoding "UTF-8";
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station Name";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.400755295e+9, 1.631724294e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Timestamp";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -52.69221, -52.6922;
    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 47.5689, 47.5689;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  wind_spd_avg {
    Float32 actual_range 0.0, 72.2;
    String ioos_category "Wind";
    String long_name "Wind Spd Avg";
    String standard_name "wind_speed";
    String units "m s-1";
  wind_spd_max {
    Float32 actual_range 0.0, 76.2;
    String ioos_category "Wind";
    String long_name "Wind Spd Max";
    String standard_name "wind_speed_of_gust";
    String units "m s-1";
  wind_dir_avg {
    Float32 actual_range 0.0, 359.999;
    Float64 colorBarMaximum 360.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Wind";
    String long_name "Wind From Direction";
    String standard_name "wind_from_direction";
    String units "degree";
  tide_ht_avg {
    Float32 actual_range -4.8, 19.062;
    Float64 colorBarMaximum 2.0;
    Float64 colorBarMinimum -2.0;
    String ioos_category "Sea Level";
    String long_name "Sea Surface Height";
    String standard_name "sea_surface_height";
    String units "m";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_name,longitude,latitude";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.2";
    String creator_email "";
    String creator_name "Marine Institute";
    String creator_url "";
    Float64 Easternmost_Easting -52.6922;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 47.5689;
    Float64 geospatial_lat_min 47.5689;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -52.6922;
    Float64 geospatial_lon_min -52.69221;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-07-18T17:14:52Z (local files)
    String infoUrl "";
    String institution "MI";
    String instrument_1_description "Anemometer";
    String instrument_1_id "12480049";
    String instrument_1_manufacturer "Gill";
    String instrument_1_type "Sensor";
    String instrument_1_version "Windsonic";
    String instrument_2_description "Remote Power Bar";
    String instrument_2_id "Remote Power Bar-444";
    String instrument_2_manufacturer "APC";
    String instrument_2_type "Equipment";
    String instrument_2_version "AP7900";
    String instrument_3_description "Telemetry";
    String instrument_3_id "Telemetry-442";
    String instrument_3_manufacturer "B&B Electronics";
    String instrument_3_type "Equipment";
    String instrument_3_version "Spectre-3G";
    String instrument_4_description "Tide Meter";
    String instrument_4_id "42745";
    String instrument_4_manufacturer "Valeport";
    String instrument_4_type "Sensor";
    String instrument_4_version "Tidemaster";
    String keywords "atmosphere, atmospheric, average, data, direction, Earth Science > Atmosphere > Atmospheric Winds > Surface Winds, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, height, identifier, institute, level, marine, max, name, ocean, oceans, sea, sea level, sea_surface_height, seaSurfaceHeight, spd, st., station, station_name, surface, tide_ht_avg, time, timestamp, topography, wind, wind_dir_avg, wind_from_direction, wind_spd_avg, wind_spd_max, winds";
    String keywords_fra "seaSurfaceHeight";
    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 47.5689;
    String platform "coastal structure";
    String platform_description "Valeport Tidemaster";
    String platform_id "42745";
    String platform_vocabulary "";
    String project "SmartAtlantic";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 47.5689;
    String standard_name_vocabulary "CF Standard Name Table v79";
    String subsetVariables "year";
    String summary "Installation of the St. John's Tide Station was undertaken in early 2014 with the site becoming operational on May 22, 2014. The Station is located at Pier 18 on the St. John's Port Authority property in St. John's, NL Harbour.The Station consists of a TideMaster portable water level recorder with VRS-20 radar level sensor and a meteorological sensor to measure wind speed and direction. The instrument has been designed to provide accurate and versatile information in an easily deployed gauge for use in short or long term hydrographic survey operations.";
    String summary_fra "L'installation de la station de marée de St. John's a été entreprise au début de 2014 et le site est devenu opérationnel le 22 mai 2014. La station est située au quai 18 sur la propriété de l'Administration portuaire de St. John's, dans le port de St. John's, à Terre-Neuve-et-Labrador, est composée d'un enregistreur de niveau d'eau portatif TideMaster muni d'un capteur de niveau radar VRS-20 et d'un capteur météorologique pour mesurer la vitesse et la direction du vent. L'instrument a été conçu pour fournir des renseignements précis et polyvalents dans un jauge facilement déployé pour les opérations de levés hydrographiques à court ou à long terme.";
    String time_coverage_end "2021-09-15T16:44:54Z";
    String time_coverage_start "2014-05-22T10:41:35Z";
    String title "St. John's Tide Station";
    String title_fra "station de marée de St. John's";
    String uuid "dc4e98e8-2010-4e7a-a69a-a5b9b3fe06a1";
    Float64 Westernmost_Easting -52.69221;


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{?query}
For example,,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.23
Disclaimers | Privacy Policy | Contact