Brought to you by BODC

Make A Graph

Dataset Title:	CreamT flood web service: [Penzance_1A] NRT waves Penzance station 75
Institution:	Regional Coastal Monitoring Programme (Dataset ID: cco_waves_75_0fba_44fb_3c28)
Range:	longitude = -5.5494 to -5.48°E, latitude = 50.10545 to 50.11491°N, time = 2020-10-30T13:00:00Z to 2022-12-05T02:30:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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 {
  stationID {
    String ioos_category "Identifier";
    String long_name "Penzance wave station 75";
    String station_identifier "waves.75";
    String wmo_number "6201000";
  }
  instrumentID {
    String instrumentID_uri_path "https://linkedsystems.uk/system/instance/";
    String ioos_category "Identifier";
    String long_name "Instrument instance identifier";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6040628e+9, 1.6702074e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String sdn_P02_urn "SDN:P02::AYMD";
    String sdn_parameter_name "Date and time (UT in ISO8601 format to known precision)";
    String sdn_parameter_urn "SDN:P01::DTUT8601";
    String sdn_uom_name "ISO8601";
    String sdn_uom_urn "SDN:P06::TISO";
    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";
    Float64 _FillValue -99.0;
    Float64 actual_range 50.10545, 50.11491;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String sdn_P02_urn "SDN:P02::ALAT";
    String sdn_parameter_name "Latitude north";
    String sdn_parameter_urn "SDN:P01::ALATZZ01";
    String sdn_uom_name "Degrees north";
    String sdn_uom_urn "SDN:P06::DEGN";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -999.0;
    Float64 actual_range -5.5494, -5.48;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String sdn_P02_urn "SDN:P02::ALAT";
    String sdn_parameter_name "Longitude east";
    String sdn_parameter_urn "SDN:P01::ALONZZ01";
    String sdn_uom_name "Degrees east";
    String sdn_uom_urn "SDN:P06::DEGE";
    String standard_name "longitude";
    String units "degrees_east";
  }
  significant_wave_height {
    Float64 _FillValue -1.0;
    Float64 actual_range 0.08, 10.01;
    String long_name "Significant Wave Height (hs)";
    String sdn_P02_urn "SDN:P02::WVST";
    String sdn_parameter_name "Significant wave height of waves {Hs} on the water body";
    String sdn_parameter_urn "SDN:P01::GTDHZZ01";
    String sdn_uom_name "Metres";
    String sdn_uom_urn "SDN:P06::ULAA";
    String standard_name "sea_surface_wave_significant_height";
    String units "m";
  }
  sea_surface_temperature {
    Float64 _FillValue -9.0;
    Float64 actual_range 6.95, 21.45;
    String long_name "Water Temperature";
    String sdn_P02_urn "SDN:P02::TEMP";
    String sdn_parameter_name "Temperature of the water body";
    String sdn_parameter_urn "SDN:P01::TEMPPR01";
    String sdn_uom_name "Degrees Celsius";
    String sdn_uom_urn "SDN:P06::UPAA";
    String standard_name "sea_water_temperature";
    String units "degC";
  }
  wave_from_direction {
    Float64 _FillValue -1.0;
    Float64 actual_range 0.0, 358.6;
    String long_name "Peak wave from direction relative to magnetic north";
    String sdn_P02_urn "SDN:P02::GWDR";
    String sdn_parameter_name "Direction (from) of waves on the water body";
    String sdn_parameter_urn "SDN:P01::GWDRZZ01";
    String sdn_uom_name "Degrees";
    String sdn_uom_urn "SDN:P06::UAAA";
    String standard_name "sea_surface_wave_from_direction";
    String units "deg";
  }
  wave_period {
    Float64 _FillValue -1.0;
    Float64 actual_range 1.72, 28.57;
    String long_name "Peak wave period";
    String sdn_P02_urn "SDN:P02::WVST";
    String sdn_parameter_name "Period at spectral maximum of waves {peak period Tp} on the water body";
    String sdn_parameter_urn "SDN:P01::GTPKZZ01";
    String sdn_uom_name "Seconds";
    String sdn_uom_urn "SDN:P06::UTBB";
    String standard_name "sea_surface_wave_period_at_variance_spectral_density_maximum";
    String units "s";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "cco@channelcoast.org";
    String creator_name "Regional Coastal Monitoring Programme of England";
    String creator_url "http://www.coastalmonitoring.org/";
    Float64 Easternmost_Easting -5.48;
    String featureType "Point";
    Float64 geospatial_lat_max 50.11491;
    Float64 geospatial_lat_min 50.10545;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -5.48;
    Float64 geospatial_lon_min -5.5494;
    String geospatial_lon_units "degrees_east";
    String history 
"Downloaded from http://data.channelcoast.org/observations/waves/ on 2020-10-30T13:00:00Z
2025-05-16T08:21:19Z http://data.channelcoast.org/observations/waves/latest.geojson?key=XXXX
2025-05-16T08:21:19Z https://linkedsystems.uk/tabledap/cco_waves_75_0fba_44fb_3c28.das";
    String infoUrl "https://www.channelcoast.org/realtimedata/?chart=75&tab=waves&disp_option=";
    String institution "Regional Coastal Monitoring Programme";
    String license "Real time data displayed on this page are from the Regional Coastal Monitoring Programme, made freely available under the terms of the Open Government Licence (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Please note that these are real-time data and are not quality-controlled.";
    Float64 Northernmost_Northing 50.11491;
    String publisher_email "enquiries@bodc.ac.uk";
    String publisher_institution "National Oceanography Centre (NOC)";
    String publisher_name "British Oceanographic Data Centre (BODC)";
    String publisher_url "https://www.bodc.ac.uk/";
    String site_name "CreamT flood hazard monitoring site - Penzance_1A";
    String site_url "TBC";
    String sourceUrl "http://data.channelcoast.org/observations/waves/latest.geojson?key=XXXX";
    Float64 Southernmost_Northing 50.10545;
    String standard_name_vocabulary "https://vocab.nerc.ac.uk/collection/P07/current/";
    String subsetVariables "stationID,instrumentID,time,latitude,longitude";
    String summary "Near real-time waves timeseries data from Regional Coastal Monitoring Programme Penzance station 75. The data are used in this instance of ERDDAP as part of the CreamT flood hazard web service that monitors site Penzance_1A.";
    String time_coverage_end "2022-12-05T02:30:00Z";
    String time_coverage_start "2020-10-30T13:00:00Z";
    String title "CreamT flood web service: [Penzance_1A] NRT waves Penzance station 75";
    Float64 Westernmost_Easting -5.5494;
  }
}

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