Marine Institute ERDDAP Server
Serving data from the Marine Institute (Ireland)

Brought to you by the Marine Institute(Ireland)

Make A Graph

Dataset Title:	Irish Wave Buoy Network - zerocrossing wave parameters
Institution:	Marine Institute (Dataset ID: IWaveBNetwork_zerocrossing)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  buoy_id {
    String ioos_category "Identifier";
    String long_name "TBC";
  }
  station_id {
    String ioos_category "Location";
    String long_name "TBC";
  }
  instrument {
    String ioos_category "Location";
    String long_name "TBC";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "longitude of measurement";
    String Processing_level "Instrument data that has been converted to geophysical values";
    String QC_indicator "nominal_value";
    String reference "WGS84";
    String sdn_parameter_name "Longitude east";
    String sdn_parameter_urn "SDN:P01::ALONZZ01";
    String sdn_units_name "Degrees east";
    String sdn_units_urn "SDN:P06::DEGE";
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_max 180.0;
    Float64 valid_min -180.0;
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "latitude of measurement";
    String Processing_level "Instrument data that has been converted to geophysical values";
    String QC_indicator "nominal_value";
    String reference "WGS84";
    String sdn_parameter_name "Latitude north";
    String sdn_parameter_urn "SDN:P01::ALATZZ01";
    String sdn_units_name "Degrees north";
    String sdn_units_urn "SDN:P06::DEGN";
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_max 90.0;
    Float64 valid_min -90.0;
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String calendar "julian";
    String ioos_category "Time";
    String long_name "time of measurement";
    String Processing_level "Instrument data that has been converted to geophysical values";
    String QC_indicator "good";
    String sdn_parameter_name "Elapsed time relative to 1970-01-01T00:00:00Z";
    String sdn_parameter_urn "SDN:P01::ELTMEP01";
    String sdn_units_name "Seconds";
    String sdn_units_urn "SDN:P06::UTBB";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Hmax {
    Float64 _FillValue -9999.0;
    String ancillary_variables "qcflag";
    String ioos_category "Surface Waves";
    String units "m";
  }
  HmaxPeriod {
    Float64 _FillValue -9999.0;
    String ancillary_variables "qcflag";
    String ioos_category "Surface Waves";
    String units "s";
  }
  Havg {
    Float64 _FillValue -9999.0;
    String ancillary_variables "qcflag";
    String ioos_category "Surface Waves";
    String units "m";
  }
  Tavg {
    Float64 _FillValue -9999.0;
    String ancillary_variables "qcflag";
    String ioos_category "Surface Waves";
    String units "s";
  }
  qcflag {
    Int32 _FillValue 9;
    String Conventions "SeaDataNet measurand qualifier flags";
    String flag_meanings "no_quality_control good_value probably_good_value probably_bad_value bad_value changed_value value_below_detection value_in_excess interpolated_value missing_value";
    String flag_values "0 1 2 3 4 5 6 7 8 9";
    String ioos_category "Quality";
    String long_name "temperature data quality flag";
    String sdn_conventions_urn "SDN:L20::";
    String standard_name "quality_flag";
  }
  data_modified {
    String ioos_category "Time";
    String long_name "time of last modification of data in the database";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  qc_modified {
    String ioos_category "Time";
    String long_name "time of last modification of nrt qc flags in the database";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String acknowledgement "TBC";
    String area "North Atlantic Ocean";
    String cdm_data_type "Point";
    String contact "data_requests@marine.ie";
    String contributor_name "Alan Berry; Conall O'Malley; Rob Thomas";
    String contributor_role "ProjectManager; ProjectMember; DataManager";
    String Conventions "Copernicus-InSituTAC-FormatManual-1.4, SeaDataNet_1.0, CF-1.6, OceanSITES-1.3, ACDD-1.2, COARDS";
    String creator_name "Marine Institute";
    String creator_url "http://www.marine.ie";
    String data_mode "R";
    String data_type "OceanSITES time-series data";
    String date_created "2015-12-10";
    String defaultDataQuery "&time>=now-24hours";
    String featureType "Point";
    String geospatial_lat_max "54.2796";
    String geospatial_lat_min "51.6470";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_max "-9.2670";
    String geospatial_lon_min "-10.2961";
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_max "0";
    String geospatial_vertical_min "0";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "meters";
    String history 
"2015-12-10: Dataset first published.
2025-11-17T05:15:23Z (source database)
2025-11-17T05:15:23Z https://erddap.marine.ie/tabledap/IWaveBNetwork_zerocrossing.das";
    String id "ie.marine.data:dataset.4775";
    String infoUrl "http://data.marine.ie/geonetwork/srv/eng/catalog.search#/metadata/ie.marine.data:dataset.4775";
    String institution "Marine Institute";
    String institution_edmo_code "396";
    String institution_references "https://www.marine.ie";
    String keywords "Wave height and period statistics";
    String keywords_vocabulary "SeaDataNet Parameter Discovery Vocabulary";
    String license "Creative Commons Attribution 4.0 (https://creativecommons.org/licenses/by/4.0/)";
    String licenseURL "https://creativecommons.org/licenses/by/4.0/legalcode";
    String naming_authority "Marine Institute";
    String network "Irish Wave Buoy Network";
    String principal_investigator "Alan Berry";
    String principal_investigator_email "alan.berry@marine.ie";
    String principal_investigator_url "https://www.marine.ie/site-area/infrastructure-facilities/marine-research-infrastructures/wave-buoy-network";
    String processing_level "Other QC process applied";
    String publisher_email "data_requests@marine.ie";
    String publisher_name "Marine Institute";
    String publisher_url "https://www.marine.ie";
    String source "moored surface buoy";
    String source_platform_category_code "41";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v72";
    String summary "TBC";
    String time_coverage_resolution "PT30M";
    String time_coverage_start "2006-04-10T13:20:00Z";
    String title "Irish Wave Buoy Network - zerocrossing wave parameters";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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