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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Overtopping Zarautz events Subscribe RSS
Institution:  AZTI   (Dataset ID: VIDEOMETRY_OUTPUT)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 time_ini (UTC) ?          2018-01-01T00:00:00Z    2024-12-31T23:50:00Z
 time_fin (UTC) ?          2018-01-01T00:19:00Z    2024-12-31T23:59:30Z
 Period (Period (s), s) ?          0.5    1.0
 Number_of_overtoppings ?          0    10
 File_name ?          "https://www.euskoo..."    "https://www.euskoo..."
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time_ini {
    Float64 actual_range 1.5147648e+9, 1.735689e+9;
    String ioos_category "Time";
    String long_name "Time Ini(YYYY-MM-DD HH:MM:SS)";
    String source_name "Time_ini(YYYY-MM-DD HH:MM:SS)";
    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";
  }
  time_fin {
    Float64 actual_range 1.51476594e+9, 1.73568957e+9;
    String ioos_category "Time";
    String long_name "Time Fin(YYYY-MM-DD HH:MM:SS)";
    String source_name "Time Fin(YYYY-MM-DD HH:MM:SS)";
    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";
  }
  Period {
    Float32 _FillValue NaN;
    Float32 actual_range 0.5, 1.0;
    String long_name "Period (s)";
    String units "s";
  }
  Number_of_overtoppings {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 10;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String long_name "Number Of Overtoppings";
  }
  File_name {
    String long_name "File Name";
  }
 }
  NC_GLOBAL {
    String acknowledgements "These data were collected and made freely available by Emodnet.";
    String cdm_data_type "Other";
    String citation "These data were collected and made freely available by Emodnet.";
    String contact_email "pliria@azti.es";
    String contact_name "Pedro Liria Loza";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "iepelde@azti.es";
    String creator_name "Irati Epelde Pagola";
    String geospatial_altitude "4,3";
    String geospatial_lat "43.287286°";
    String geospatial_lon "-2.173878°";
    String history 
"2026-07-21T23:22:45Z (local files)
2026-07-21T23:22:45Z https://www.euskoos.eus/erddap/tabledap/VIDEOMETRY_OUTPUT.html";
    String infoUrl "https://info.euskoos.eus/";
    String institution "AZTI";
    String institution_edmo_code "1623";
    String keywords "overtopping, videometry";
    String license "Data must be used following CC BY-NC 4.0 Creative Commons license";
    String location "Zarautz";
    String owner "AZTI, Gipuzkoako Foru Aldundia (GFA), Euskalmet, Zarauzko Udala";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary 
"Overtopping events Zarautz
Location: Zarautz
Geospatial_lat: 43.287286°
Geospatial_lon: -2.173878°
Geospatial_altitude: 4,3";
    String time_coverage_end "2024-04-01";
    String time_coverage_resolution "10 minutes";
    String time_coverage_start "2023-10-01";
    String title "Overtopping Zarautz events";
    String variables "Number of over: Number of overtoppings detected in the timestack image captured";
    String z_reference_level "Topografic 0 IGN-REDNAP2008";
  }
}

 

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