EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data 		log in|?   
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  PSMSL stations Subscribe RSS
Institution:  PSMSL   (Dataset ID: PSMSL_STATIONS)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | 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 {
  id {
    String long_name "Id";
  }
  name {
    String long_name "Name";
  }
  gloss {
    String long_name "Gloss";
  }
  glosslink {
    String long_name "Glosslink";
  }
  country {
    String long_name "Country";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Last Updated";
    String source_name "last_updated";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  supplier {
    String long_name "Supplier";
  }
  isrlr {
    String long_name "Isrlr";
  }
  monthlyplot {
    String long_name "Monthlyplot";
  }
  annualplot {
    String long_name "Annualplot";
  }
  monthlyrlrdata {
    String long_name "Monthlyrlrdata";
  }
  annualrlrdata {
    String long_name "Annualrlrdata";
  }
  has_rlr_diagram {
    String long_name "Has Rlr Diagram";
  }
  qcflag {
    String long_name "Qcflag";
  }
  address {
    String long_name "Address";
  }
  metric_start {
    String long_name "Metric Start";
  }
  metric_end {
    String long_name "Metric End";
  }
  metric_completeness {
    String long_name "Metric Completeness";
  }
  rlr_start {
    String long_name "Rlr Start";
  }
  rlr_end {
    String long_name "Rlr End";
  }
  rlr_completeness {
    String long_name "Rlr Completeness";
  }
  vliz {
    String long_name "Vliz";
  }
  uhslc_quality {
    String long_name "Uhslc Quality";
  }
  uhslc_fast {
    String long_name "Uhslc Fast";
  }
  sonel {
    String long_name "Sonel";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String featureType "Point";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String history 
"2025-10-31T13:55:10Z (source database)
2025-10-31T13:55:10Z http://erddap.emodnet-physics.eu/tabledap/PSMSL_STATIONS.das";
    String infoUrl "https://www.psmsl.org/";
    String institution "PSMSL";
    String keywords "address, annualplot, annualrlrdata, center, completeness, country, data, diagram, end, fast, global, gloss, glosslink, has_rlr_diagram, hawaii, isrlr, latitude, level, local, longitude, metric, metric_completeness, metric_end, metric_start, monthlyplot, monthlyrlrdata, name, observing, qcflag, quality, rlr, rlr_completeness, rlr_end, rlr_start, sea, sonel, source, start, supplier, system, time, uhslc, uhslc_fast, uhslc_quality, university, updated, vliz";
    String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "PSMSL stations";
    String title "PSMSL stations";
  }
}

 

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