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:  TAD - Collection of water surface height above a specific datum (SLEV)
TimeSeries - IN SITU MultiPointTimeSeriesObservation - METADATA
Subscribe RSS
Institution:  EMODnet Physics   (Dataset ID: TS_SLEV_TAD_1566_METADATA)
Range: longitude = 158.65 to 158.65°E, latitude = 53.016666 to 53.016666°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
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: 
[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 {
  PLATFORMCODE {
    String long_name "EMODnet Platform Code";
  }
  call_name {
    String long_name "Platform Call Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 53.016667, 53.016667;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 158.65, 158.65;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  DataFeatureType {
    String long_name "Data Feature Type";
  }
  firstDateObservation {
    String ioos_category "Time";
    String long_name "first Date Observation";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  lastDateObservation {
    String ioos_category "Time";
    String long_name "last Date Observation";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  parameters_group_longname {
    String long_name "Parameters Info Parameter Groups";
  }
  parameters_group_P02 {
    String long_name "Parameters Info P02";
  }
  parameters {
    String long_name "Parameters Info Parameters";
  }
  parameters_P01 {
    String long_name "Parameters Info P01";
  }
  WMO {
    Int32 _FillValue 2147483647;
    String long_name "WMO";
  }
  BEST_PRACTICES_DOI {
    String long_name "BEST PRACTICES DOI";
  }
  DATA_DOI {
    String long_name "DATA DOI";
  }
  data_owner_longname {
    String long_name "Data Owner Name";
  }
  data_owner_country_code {
    String long_name "Data Owner Country Code";
  }
  data_owner_country_longname {
    String long_name "Data Owner Country Name";
  }
  data_owner_EDMO {
    Byte _FillValue 127;
    String _Unsigned "false";
    String long_name "Data Owner EDMO Code";
  }
  data_assembly_center_longname {
    String long_name "Data Assembly Center";
  }
  platform_type_longname {
    String long_name "Platform Type";
  }
  platform_type_SDNL06 {
    String long_name "Platform Type SDN L06";
  }
  platformpage_link {
    String long_name "Platform Page";
  }
  integrator_id {
    String long_name "integrator_id";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    Float64 Easternmost_Easting 158.65;
    Float64 geospatial_lat_max 53.016667;
    Float64 geospatial_lat_min 53.016667;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 158.65;
    Float64 geospatial_lon_min 158.65;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-11T12:42:04Z (local files)
2025-05-11T12:42:04Z http://er2webapps.emodnet-physics.eu/metadata//tabledap/TS_SLEV_TAD_1566_METADATA.das";
    String infoUrl "https://emodnet.ec.europa.eu/en/physics";
    String institution "EMODnet Physics";
    String license "CC-BY";
    Float64 Northernmost_Northing 53.016667;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 53.016667;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "PLATFORMCODE";
    String summary "TAD - Collection of water surface height above a specific datum (SLEV) TimeSeries - IN SITU MultiPointTimeSeriesObservation - METADATA";
    String title "TAD - Collection of water surface height above a specific datum (SLEV) TimeSeries - IN SITU MultiPointTimeSeriesObservation - METADATA";
    Float64 Westernmost_Easting 158.65;
  }
}

 

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