BODC log in | ?    
Brought to you by BODC    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CreamT flood web service: [Dawlish_1A] NRT wind West Bay Harbour station 95 Subscribe RSS
Institution:  Regional Coastal Monitoring Programme   (Dataset ID: cco_met_95_41333_f8a2_ea64_66d5)
Range: longitude = -2.82 to -2.82°E, latitude = 50.71017 to 50.71017°N, time = 2021-05-27T09:20:00Z to 2023-01-09T14:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
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 ioos_category "Identifier";
    String long_name "West Bay Harbour meteorological station 95";
    String station_identifier "met.95";
    String wmo_number "6201005";
  }
  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.6221072e+9, 1.6732728e+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.71017, 50.71017;
    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 -2.82, -2.82;
    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";
  }
  wind_speed {
    Float64 _FillValue -1.0;
    Float64 actual_range 0.2, 21.6;
    String long_name "Wind Speed";
    String sdn_P02_urn "SDN:P02::EWSB";
    String sdn_parameter_name "Speed of wind {wind speed} in the atmosphere";
    String sdn_parameter_urn "SDN:P01::EWSBZZ01";
    String sdn_uom_name "Metres per second";
    String sdn_uom_urn "SDN:P06::UVAA";
    String standard_name "wind_speed";
    String units "m/s";
  }
  wind_from_direction {
    Float64 _FillValue -1.0;
    Float64 actual_range 0.0, 358.0;
    String long_name "Wind From Direction";
    String sdn_P02_urn "SDN:P02::EWSB";
    String sdn_parameter_name "Direction (from) of wind relative to True North {wind direction} in the atmosphere";
    String sdn_parameter_urn "SDN:P01::EWDAZZ01";
    String sdn_uom_name "Degrees True";
    String sdn_uom_urn "SDN:P06::UABB";
    String standard_name "wind_from_direction";
    String units "deg T";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "IOOS-1.2, COARDS, CF-1.6, ACDD-1.3, NCCSV-1.0";
    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 -2.82;
    String featureType "Point";
    Float64 geospatial_lat_max 50.71017;
    Float64 geospatial_lat_min 50.71017;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -2.82;
    Float64 geospatial_lon_min -2.82;
    String geospatial_lon_units "degrees_east";
    String history 
"Downloaded from http://data.channelcoast.org/observations/tides/ on 2021-05-27T14:00:00Z
2024-04-23T18:35:13Z http://data.channelcoast.org/observations/met/latest?key=XXXX
2024-04-23T18:35:13Z https://linkedsystems.uk/tabledap/cco_met_95_41333_f8a2_ea64_66d5.das";
    String infoUrl "https://www.channelcoast.org/realtimedata/?chart=95&tab=met&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.71017;
    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 - Dawlish_1A";
    String site_url "TBC";
    String sourceUrl "http://data.channelcoast.org/observations/met/latest?key=XXXX";
    Float64 Southernmost_Northing 50.71017;
    String standard_name_vocabulary "https://vocab.nerc.ac.uk/collection/P07/current/";
    String subsetVariables "stationID,instrumentID,time,latitude,longitude";
    String summary "Near real-time wind timeseries from Regional Coastal Monitoring Programme West Bay Harbour station 95. The data are used in this instance of ERDDAP as part of the CreamT flood hazard web service that monitors site  Dawlish_1A.";
    String time_coverage_end "2023-01-09T14:00:00Z";
    String time_coverage_start "2021-05-27T09:20:00Z";
    String title "CreamT flood web service: [Dawlish_1A] NRT wind West Bay Harbour station 95";
    Float64 Westernmost_Easting -2.82;
  }
}

 

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