Marine Institute Logo Marine Institute ERDDAP Server
Serving data from the Marine Institute (Ireland)
   
Brought to you by the Marine Institute(Ireland)    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Marine Institute Tide Prediction - High and Low tide times summary   RSS
Institution:  Marine Institute   (Dataset ID: IMI_TidePrediction_HighLow)
Range: longitude = -10.27732 to -6.0683°E, latitude = 51.559 to 55.37168°N
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";
  }
  time {
    String _CoordinateAxisType "Time";
    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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -10.27732, -6.0683;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 51.559, 55.37168;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  tide_time_category {
    String ioos_category "Sea Level";
  }
  tide_height_LAT {
    Float64 actual_range 0.0, 5.813;
    String ioos_category "Sea Level";
    String sea_level_datum "Lowest Astronomical Tide";
    String units "metres";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "stationID, longitude, latitude";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    String date_created "2023-06-29";
    String date_issued "2023-06-29";
    String defaultDataQuery "&time>=now-1day&time<=now+7days";
    Float64 Easternmost_Easting -6.0683;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 55.37168;
    Float64 geospatial_lat_min 51.559;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -6.0683;
    Float64 geospatial_lon_min -10.27732;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-02-27T15:43:25Z http://www.marine.ie/
2024-02-27T15:43:25Z https://erddap.marine.ie/tabledap/IMI_TidePrediction_HighLow.das";
    String id "ie.marine.data:dataset.2776";
    String infoUrl "http://data.marine.ie/geonetwork/srv/eng/catalog.search#/metadata/ie.marine.data:dataset.2776";
    String institution "Marine Institute";
    String keywords "Sea level, Vertical spatial coordinates";
    String keywords_vocabulary "SeaDataNet Parameter Discovery Vocabulary";
    String license "Creative Commons Attribution 4.0 (https://creativecommons.org/licenses/by/4.0/)";
    Float64 Northernmost_Northing 55.37168;
    String sourceUrl "http://www.marine.ie/";
    Float64 Southernmost_Northing 51.559;
    String subsetVariables "stationID, longitude, latitude, tide_time_category";
    String summary "This dataset contains a subset of the times and tidal heights of each low and high water from the Marine Institute Tidal Prediction dataset. Water Level is sea surface height above local Lowest Astronomical Tide measured in metres. Times of high and low water are at 5 minute resolution (i.e. reported to the nearest 5 minute division of an hour. Tidal predictions are generated from measured data via the Irish National Tide Gauge Network and via modelled data from the MI operational hydrodynamic model. Tidal prediction is a calculation of future tide ranges based on available oceanographic parameters. Users can select a station and datetime within the next 2-3 years for the tidal prediction using the menus available.";
    String title "Marine Institute Tide Prediction - High and Low tide times summary";
    Float64 Westernmost_Easting -10.27732;
  }
}

 

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