EUSKOOS ERDDAP Installation EUSKOOS
Easier access to scientific data
log in    
Brought to you by EUSKOOS    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  R4C - Txingudi Obscape Tidal Gauge - 4464 Subscribe RSS
Institution:  AZTI   (Dataset ID: R4C_Txingudi_Obscape_TG_4464)
Range: time = 2024-01-30T00:00:00Z to 2025-10-10T15:00:00Z
Information:  Summary ? | License ? | Metadata | Background (external link) | 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: 
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 ? )
   
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.7065728e+9, 1.7601084e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Column#0";
    String source_name "Column#0";
    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";
  }
  Sea_level {
    Float32 _FillValue NaN;
    Float32 actual_range -2.26176, 3.77762;
    String long_name "Sea level";
    String units "m";
  }
 }
  NC_GLOBAL {
    String Acknowledgement "Regions4Climate, DOI: 10.3030/101093873";
    String cdm_data_type "Other";
    String contact "rgarnier at azti.es";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String geospatial_lat_max "43.367731";
    String geospatial_lat_min "43.367731";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_max "-1.791496";
    String geospatial_lon_min "-1.791496";
    String geospatial_lon_units "degrees_east";
    String history 
"2025-10-15T07:27:13Z (local files)
2025-10-15T07:27:13Z https://www.euskoos.eus/tabledap/R4C_Txingudi_Obscape_TG_4464.das";
    String infoUrl "https://regions4climate.eu/";
    String institution "AZTI";
    String keywords "Sea level";
    String license "The data may be used and redistributed for free but is not intended for legal use, since it may contain inaccuracies.";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Sea level data (m). Time step: 10 min. Updated interval: 1 hour. Vertical reference: REDNAP-08.  Obscape technology.";
    String testOutOfDate "now-1day";
    String time_coverage_end "2025-10-10T15:00:00Z";
    String time_coverage_start "2024-01-30T00:00:00Z";
    String title "R4C - Txingudi Obscape Tidal Gauge - 4464";
  }
}

 

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