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:  MI Wave Forecast at buoy locations   RSS
Institution:  Marine Institute   (Dataset ID: IMI-WaveBuoyForecast)
Range: longitude = -15.93 to -5.425°E, latitude = 51.2166 to 55.0°N, time = 2018-09-17T00:00:00Z to 2018-09-26T00:00:00Z
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 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
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.)
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5371424e+9, 1.53792e+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";
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -15.93, -5.425;
    String axis "X";
    String ioos_category "Location";
    String long_name "longitude in decimal degree east";
    String standard_name "longitude";
    String units "degrees_east";
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 51.2166, 55.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "latitude in decimal degree north";
    String standard_name "latitude";
    String units "degrees_north";
  stationID {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station ID";
  significant_wave_height {
    Float64 actual_range 0.17931, 7.48434;
    String ioos_category "Surface Waves";
    String long_name "significant wave height";
    String units "m";
  mean_wave_period {
    Float64 actual_range 1.6608, 8.8545;
    String ioos_category "Surface Waves";
    String long_name "mean absolute zero-crossing period (TM02)";
    String units "s";
  mean_wave_direction {
    Float64 actual_range 0.004, 359.946;
    String ioos_category "Surface Waves";
    String long_name "mean wave to direction";
    String units "degrees";
  wave_power_per_unit_crest_length {
    Float64 actual_range 0.0889173925949786, 291.70812596581146;
    String ioos_category "Surface Waves";
    String long_name "wave power per unit crest length";
    String units "kW/m";
  peak_period {
    Float32 actual_range 2.413, 18.497;
    String comment "tp peak period";
    String ioos_category "Surface Waves";
    String long_name "sea_surface_wave_period_at_variance_spectral_density_maximum";
    String standard_name "sea_surface_wave_period_at_variance_spectral_density_maximum";
    String units "s";
  energy_period {
    Float32 actual_range 2.808, 14.1199;
    String ioos_category "Surface Waves";
    String long_name "Wave energy period";
    String standard_name "sea_surface_wave_mean_period_from_variance_spectral_density_inverse_frequency_moment";
    String units "s";
  project_code {
    String ioos_category "Other";
    String long_name "project_code";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "stationID, longitude, latitude";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    Float64 Easternmost_Easting -5.425;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 55.0;
    Float64 geospatial_lat_min 51.2166;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -5.425;
    Float64 geospatial_lon_min -15.93;
    String geospatial_lon_units "degrees_east";
    String history 
    String infoUrl "";
    String institution "Marine Institute";
    String keywords "Earth Science > Tide";
    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.";
    String Metadata_Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    Float64 Northernmost_Northing 55.0;
    String sourceUrl "";
    Float64 Southernmost_Northing 51.2166;
    String subsetVariables "stationID, longitude, latitude, project_code";
    String summary "MI Wave Forecast at buoy locations";
    String time_coverage_end "2018-09-26T00:00:00Z";
    String time_coverage_start "2018-09-17T00:00:00Z";
    String title "MI Wave Forecast at buoy locations";
    Float64 Westernmost_Easting -15.93;


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