ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	XEOS HKB Buoy Wave Sensor
Institution:	XEOS (Dataset ID: SmartAtlantic_XEOS_hkb_buoy)
Range:	longitude = -63.5427 to -63.5427°E, latitude = 44.5973 to 44.5973°N, time = 2021-02-02T03:23:00Z to 2024-04-18T01:23:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

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 {
  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.61223618e+9, 1.71340338e+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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 44.5973, 44.5973;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -63.5427, -63.5427;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  precise_lat {
    Float64 actual_range 44.5973, 44.5973;
    String ioos_category "Location";
    String long_name "Precise Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  precise_lon {
    Float64 actual_range -63.5427, -63.5427;
    String ioos_category "Location";
    String long_name "Precise Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  battery_level {
    Float32 actual_range 12.3, 14.7;
    String ioos_category "Other";
    String long_name "Battery Voltage";
    String units "V";
  }
  temperature {
    String _Unsigned "false";
    Byte actual_range -19, 41;
    String ioos_category "Temperature";
    String long_name "Temperature";
    String units "degree_C";
  }
  wave_ht_sig {
    Float32 actual_range 0.08, 5.42;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Surface Waves";
    String long_name "Sea Surface Wave Significant Height";
    String standard_name "sea_surface_wave_significant_height";
    String units "m";
  }
  wave_period_max {
    Float32 actual_range 1.85, 19.69;
    Float64 colorBarMaximum 20.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Surface Waves";
    String long_name "Sea Surface Wave Maximum Period";
    String standard_name "sea_surface_wave_maximum_period";
    String units "s";
  }
  wave_ht_max {
    Float32 actual_range 0.08, 4.28;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Surface Waves";
    String long_name "Sea Surface Wave Significant Height";
    String standard_name "sea_surface_wave_significant_height";
    String units "m";
  }
  wave_dir_avg {
    Int16 actual_range 0, 359;
    Float64 colorBarMaximum 360.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Surface Waves";
    String long_name "Sea Surface Wave To Direction";
    String standard_name "sea_surface_wave_to_direction";
    String units "degree";
  }
  wave_spread_avg {
    String _Unsigned "false";
    Byte actual_range 33, 47;
    String ioos_category "Surface Waves";
    String long_name "Wavespread";
    String units "degree";
  }
  sea_surface_wave_mean_period {
    Float32 actual_range 2.36, 16.01;
    Float64 colorBarMaximum 20.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Surface Waves";
    String long_name "Mean Zero-Upcrossing Period";
    String units "s";
  }
  sample_quality {
    String _Unsigned "false";
    Byte actual_range 7, 7;
    String ioos_category "Quality";
    String long_name "Sample Quality";
    String units "1";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_name,longitude,latitude";
    String contributor_name "Canadian Coast Guard (CCG)";
    String contributor_role "Notices to Mariners - NOTMAR, West Outer Middle Ground light buoy HKB, https://www.notmar.gc.ca/publications/list-lights/atl/a327-en";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "dan@xeostech.com";
    String creator_name "Xeos Technologies";
    String creator_url "https://xeostech.com/";
    Float64 Easternmost_Easting -63.5427;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 44.5973;
    Float64 geospatial_lat_min 44.5973;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -63.5427;
    Float64 geospatial_lon_min -63.5427;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-18T01:30:20Z (local files)
2024-04-18T01:30:20Z https://www.smartatlantic.ca/tabledap/SmartAtlantic_XEOS_hkb_buoy.das";
    String infoUrl "https://www.smartatlantic.ca/station_alt.html?id=halifax_hk4";
    String institution "XEOS";
    String keywords "data, direction, Earth Science > Oceans > Ocean Waves > Significant Wave Height, Earth Science > Oceans > Ocean Waves > Swells, Earth Science > Oceans > Ocean Waves > Wave Period, Earth Science > Oceans > Ocean Waves > Wave Speed/Direction, height, identifier, institute, latitude, level, longitude, marine, maximumwaveheight, name, ocean, oceans, peakwaveperiod, period, sea, sea_surface_swell_wave_period, sea_surface_wave_significant_height, sea_surface_wave_to_direction, seaSurfaceHeight, significant, significantwaveheight, speed, station, station_name, surface, surface waves, swell, swells, time, timestamp, wave, wavedirection, waves, wavespread, xeos";
    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 44.5973;
    String platform "moored surface buoy";
    String platform_vocabulary "https://vocab.nerc.ac.uk/collection/L06/current/";
    String project "SmartAtlantic";
    String publisher_email "SmartBay@smartbay.ca";
    String publisher_name "SmartAtlantic";
    String publisher_url "https://www.smartatlantic.ca/";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.5973;
    String standard_name_vocabulary "CF Standard Name Table v79";
    String summary 
"The Brizo is a GNSS-based, directional wave height sensor. Developed by Xeos Technologies, it is a breakthrough product on the market that provides significant wave height, maximum wave height, peak wave period, average wave direction, and average wave spread. It was installed on the HKB navigational buoy in the Halifax Harbour near Meagher's Beach.

When the Port Authority raised a need for capturing wave data at this location, Xeos Technologies was happy to provide and install its own wave height sensor for the SmartAtlantic project. It is an opportunity to aid in the environmental monitoring of harbor conditions.";
    String summary_fra "Le Brizo est un capteur de hauteur d'onde directionnel basé sur GNSS. Développé par Xeos Technologies, il s'agit d'un produit révolutionnaire sur le marché qui offre une hauteur de vague importante, une hauteur maximale des vagues, une période de pointe, une direction moyenne des vagues et une propagation moyenne des vagues. Elle a été installée sur la bouée de navigation HKB dans le port d'Halifax, près de Meagher's Beach.  \\n \\nLorsque l'administration portuaire a soulevé le besoin de saisir les données sur les vagues à cet endroit, Xeos Technologies était heureuse de fournir et d'installer son propre capteur de hauteur des vagues pour le projet SmartAtlantic. Il s'agit d'une occasion de contribuer à la surveillance environnementale des conditions portuaires.";
    String testOutOfDate "now-120minutes";
    String time_coverage_end "2024-04-18T01:23:00Z";
    String time_coverage_start "2021-02-02T03:23:00Z";
    String title "XEOS HKB Buoy Wave Sensor";
    String title_fra "XEOS HKB Bouoy Wave Sensor";
    String uuid "1534e6ca-e607-4bcd-8b97-fcf02816f5a3";
    Float64 Westernmost_Easting -63.5427;
  }
}

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