RAISE ERDDAP
Easier access to scientific data
   
Brought to you by    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  2 days 1.1 km resolution forecast over Liguria - Animation of wind Subscribe RSS
Institution:  UNIGE-DICCA   (Dataset ID: unige-dicca_wind_animation_1_1km)
Range: time = 2026-04-03T00:00:00Z to 2026-04-04T00:00:00Z
Information:  Summary ? | License ? | 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: 
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 {
  url {
    String ioos_category "Identifier";
    String long_name "URL";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  name {
    String ioos_category "Identifier";
    String long_name "File Name";
  }
  lastModified {
    String ioos_category "Time";
    String long_name "Last Modified";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  size {
    String ioos_category "Other";
    String long_name "Size";
    String units "bytes";
  }
  fileType {
    String ioos_category "Identifier";
    String long_name "File Type";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String contributors_email "meteocean.unige@gmail.com";
    String contributors_name "MeteOcean research group";
    String contributors_role "Research management";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "francesco.ferrari@unige.it";
    String creator_name "Ferrari, Francesco";
    String creator_orcid "0000-0002-8752-993X";
    String creator_type "person";
    String creator_url "https://forecast.meteocean.science";
    String data_doi "10.5281/zenodo.18171634";
    String data_format_original "grib2";
    String data_version "3.9.1";
    String documentation "https://s4raise.it/dssmare/distributed_monitoring/, https://s4raise.it/dssmare/metocean_models/, https://raise-spoke3.s4raise.it/project01";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String history 
"2026-04-03T02:56:17Z (local files)
2026-04-03T02:56:17Z https://erddap.s4raise.it/tabledap/unige-dicca_wind_animation_1_1km.das";
    String infoUrl "https://www.raiseliguria.it/spoke-3/";
    String inspire "Oceanographic geographical features";
    String institution "UNIGE-DICCA";
    String institution_country "IT";
    String keywords "Vorticity (858a80ff-5aa4-4590-b2e2-e88a802a6ee4)";
    String keywords_vocabulary "GCMD Science Keywords";
    String language "XML";
    String license "CC-BY 4.0";
    String maintainer "ETT S.p.A.";
    String model_realtime "true";
    String naming_authority "RAISE, Sindbad 2.0";
    String owner "UNIGE-DICCA";
    String owner_url "https://meteocean.science/";
    String project_code "RAISE, Sindbad 2.0";
    String project_id "ECS00000035,";
    String project_name "Robotics and AI for Socio-economic Empowerment, Servizi per la Navigazione e Attività Marittime";
    String project_statement "RAISE: Robotics and AI for Socio-economic Empowerment is an innovation ecosystem funded by the Ministry of University and Research under the National Recovery and Resilience Plan (NRRP, Mission 4, Component 2, Investment 1.5). Sindbad 2.0: Servizi per la Navigazione e Attività Marittime (Services for Navigation and Maritime Activities)";
    String project_url "https://www.raiseliguria.it/, https://www.sindbad-liguria.it/";
    String publisher "ETT S.p.A.";
    String source "WRF simulations initialized with GFS global model simulation";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "fileType";
    String summary "Hourly 3-dimensional atmospheric gridded data, with a temporal coverage of 48 hours and a spatial resolution of 1.1 km. Data cover Central and Eastern Liguria - Animation of wind";
    String theme_eu_data "http://publications.europa.eu/resource/authority/data-theme/ENVI";
    String theme_eurovoc "http://publications.europa.eu/resource/authority/eurovoc/100224";
    String title "2 days 1.1 km resolution forecast over Liguria - Animation of wind";
    String visibility "public";
  }
}

 

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