Marine Institute Logo Marine Institute ERDDAP Server
Serving data from the Marine Institute (Ireland) 		   
Brought to you by the Marine Institute(Ireland)    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Irish National Tide Gauge Network   RSS
Institution:  Marine Institute   (Dataset ID: IrishNationalTideGaugeNetwork)
Range: longitude = -10.27732 to -6.06809°E, latitude = 51.6496 to 55.3717°N, altitude = 0.0 to 0.0m
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() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -10.27732, -6.06809;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 51.6496, 55.3717;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  altitude {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    Float32 actual_range 0.0, 0.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Altitude";
    String positive "up";
    String standard_name "altitude";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Detection Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  station_id {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Station ID";
  }
  datasourceid {
    String ioos_category "Identifier";
    String long_name "Datasource ID";
  }
  Water_Level {
    String ioos_category "Sea Level";
    String long_name "sea level above LAT";
    String standard_name "sea surface height above local lat lowest astronomical tide";
    String units "m";
  }
  Water_Level_LAT {
    String ioos_category "Sea Level";
    String long_name "sea level above LAT";
    String standard_name "sea surface height above local lat lowest astronomical tide";
    String units "m";
  }
  Water_Level_OD_Malin {
    String ioos_category "Sea Level";
    String long_name "sea level OD Malin";
    String standard_name "sea surface height ordnance datum malin";
    String units "m";
  }
  QC_Flag {
    String ioos_category "Quality";
    String long_name "Quality Control Flags";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id, longitude, latitude";
    String Conventions "COARDS, CF-1.4, Unidata Dataset Discovery v1.0";
    Float64 Easternmost_Easting -6.06809;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 55.3717;
    Float64 geospatial_lat_min 51.6496;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -6.06809;
    Float64 geospatial_lon_min -10.27732;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 0.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "up";
    String geospatial_vertical_units "m";
    String history 
"2019-06-18T22:54:40Z (source database)
2019-06-18T22:54:40Z https://erddap.marine.ie/tabledap/IrishNationalTideGaugeNetwork.das";
    String infoUrl "http://catalog.marine.ie/geonetwork/srv/en/main.home?uuid=0da11e42-2d03-4c64-8b0d-0e78c04efc34";
    String institution "Marine Institute";
    String license "Creative Commons Attribution 4.0 (https://creativecommons.org/licenses/by/4.0/)";
    Float64 Northernmost_Northing 55.3717;
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing 51.6496;
    String standard_name_vocabulary "CF-12";
    String subsetVariables "station_id, longitude, latitude";
    String summary "The Irish National Tide Gauge Network is an on-going development involving the Marine Institute and a number of organisations in the public and private sectors to develop a permanent tidal monitoring infrastructure, ultimately consisting of between 35 and 40 stations.";
    String title "Irish National Tide Gauge Network";
    Float64 Westernmost_Easting -10.27732;
  }
}

 

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