Serving data from
log in    
Brought to you by    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  INTERREG VA COMPASS Mooring Data Subscribe RSS
Institution:  SEUPB   (Dataset ID: do_compass)
Range: longitude = -9.5605 to -5.635°E, latitude = 53.19877 to 54.66348°N, time = 2017-09-22T00:00:00Z to 2020-02-18T12:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
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 {
  station_id {
    String ioos_category "Identifier";
    String long_name "Station Id";
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5060384e+9, 1.5820272e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Timestamp";
    String source_name "timestamp";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  year {
    Float64 actual_range 2017, 2020;
    String ioos_category "Time";
    String long_name "Year";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 53.198769, 54.66348;
    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";
    Float64 actual_range -9.5605, -5.635;
    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";
  temperature {
    Float64 actual_range -99.99, 20.84;
    String ioos_category "Temperature";
    String long_name "Temperature";
  salinity {
    Float64 actual_range -99.99, 34.9251;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Sea Water Practical Salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "SEUPB";
    String creator_type "institution";
    String creator_url "";
    Float64 Easternmost_Easting -5.635;
    String featureType "Point";
    Float64 geospatial_lat_max 54.66348;
    Float64 geospatial_lat_min 53.198769;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -5.635;
    Float64 geospatial_lon_min -9.5605;
    String geospatial_lon_units "degrees_east";
    String history 
"2020-02-18T14:58:21Z (source database)
2024-05-18T01:41:58Z (local database)
    String id "do_compass";
    String infoUrl "";
    String institution "SEUPB";
    String keywords "compass, data, density, earth, Earth Science, identifier, interreg, latitude, longitude, mooring, ocean, oceans, Oceans Salinity, practical, salinity, science, sea, sea_water_practical_salinity, seawater, seupb, station, station_id, temperature, time, timestamp, water, year";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "Creative Commons Attribution 4.0 (";
    Float64 Northernmost_Northing 54.66348;
    String sourceUrl "(local database)";
    Float64 Southernmost_Northing 53.198769;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "station_id, year";
    String summary "Mooring data from three moored buoys off the coasts of Ireland. One at Mace Head, Galaway, Ireland. One at Belfast Pile8, Northern Ireland, UK. One at Strangford Lough, Northern Ireland, UK.";
    String time_coverage_end "2020-02-18T12:00:00Z";
    String time_coverage_start "2017-09-22T00:00:00Z";
    String title "INTERREG VA COMPASS Mooring Data";
    Float64 Westernmost_Easting -9.5605;


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