Make A Graph

Dataset Title:	Project AdriaClimPlus \| SHYFEM \| 3d-day-temperature \| Perturbed 2.0 \| ID 2397F100D2_0022
Institution:	ARPA FVG (Dataset ID: AdriaClimPlus_2397F100D2_0022_3d-day-temperature)
Range:	longitude = 12.77982 to 13.7599°E, latitude = 45.23782 to 45.77096°N, depth = 0.5 to 35.0m, time = 2011-01-01T12:00:00Z to 2020-12-31T12:00:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  node_id {
    Int32 _FillValue -999;
    Int32 actual_range 78, 18268;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String ioos_category "Identifier";
    String long_name "Node ID in the original SHYFEM mesh";
    Int32 missing_value -999;
    String standard_name "node_id";
  }
  time {
    UInt32 _ChunkSizes 512;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2938832e+9, 1.609416e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "time [UTC]";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 12.77982, 13.7599;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude of 2D mesh node";
    String source_name "longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 45.23782, 45.77096;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude of 2D mesh node";
    String source_name "latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.5, 35.0;
    String axis "Z";
    String description "bottom of vertical layers";
    String ioos_category "Location";
    String long_name "Depth Below Sea";
    String positive "down";
    String source_name "level";
    String standard_name "depth";
    String units "m";
  }
  total_depth {
    Float32 _FillValue -999.0;
    Float32 actual_range 0.25, 33.29;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String ioos_category "Location";
    String long_name "total depth at nodes: sea floor depth below sea surface";
    Float32 missing_value -999.0;
    String source_name "total_depth";
    String standard_name "sea_floor_depth_below_sea_surface";
    String units "m";
  }
  mean_temperature {
    String _ChunkSizes "1 8 1";
    Float32 _FillValue -999.0;
    Float32 actual_range -2.18, 35.56;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String frequency "day";
    String ioos_category "Temperature";
    String long_name "Sea water temperature";
    Float32 missing_value -999.0;
    String standard_name "sea_water_temperature";
    String statistics "daily mean of hourly timesteps";
    String units "°C";
  }
  min_temperature {
    UInt32 _ChunkSizes 1, 8, 1;
    Float32 _FillValue -999.0;
    Float32 actual_range -2.19, 33.42;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String frequency "day";
    String ioos_category "Temperature";
    String long_name "Sea water temperature";
    Float32 missing_value -999.0;
    String standard_name "sea_water_temperature";
    String statistics "daily min of hourly timesteps";
    String units "°C";
  }
  pctl_50_temperature {
    UInt32 _ChunkSizes 1, 8, 1;
    Float32 _FillValue -999.0;
    Float32 actual_range -2.18, 36.6;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String frequency "day";
    String ioos_category "Temperature";
    String long_name "Sea water temperature";
    Float32 missing_value -999.0;
    String standard_name "sea_water_temperature";
    String statistics "daily pctl_50 of hourly timesteps";
    String units "°C";
  }
  max_temperature {
    UInt32 _ChunkSizes 1, 8, 1;
    Float32 _FillValue -999.0;
    Float32 actual_range -2.14, 44.84;
    String CDI_grid_type "unstructured";
    String coordinates "latitude longitude";
    String frequency "day";
    String ioos_category "Temperature";
    String long_name "Sea water temperature";
    Float32 missing_value -999.0;
    String standard_name "sea_water_temperature";
    String statistics "daily max of hourly timesteps";
    String units "°C";
  }
 }
  NC_GLOBAL {
    String accessRights "CC BY";
    String accrualMethod "collection";
    String accrualPeriodicity "as needed";
    String acknowledgement "ARPA FVG - Regional Environmental Agency of Friuli Venezia Giulia Region";
    String adriaclim_dataset "indicator";
    String adriaclim_IDsimulation "2397F100D2_0022";
    String adriaclim_institution "ARPA FVG";
    String adriaclim_legend "temperature";
    String adriaclim_model "SHYFEM version 8.1.0";
    String adriaclim_scale "FVG pilot area";
    String adriaclim_timeperiod "daily";
    String adriaclim_type "timeseries";
    String cdm_data_type "Other";
    String comment "AdriaClimPlus Project: Statistical post-processing of simulation 2397F100D2_0022. Daily statistics of hourly timesteps. 10 years simulation (2011-2020) under GWL2.0";
    String contributor_name "CRMA - Regional Center for Environmental Modelling";
    String Conventions "COARDS, CF-1.10, ACDD-1.3, NCCSV-1.2";
    String conventions "COARDS";
    String coverage_content_type "modelResult";
    String creator_acronym "ARPA FVG";
    String creator_email "crma@arpa.fvg.it";
    String creator_longname_english "Regional Environmental Agency of Friuli Venezia Giulia Region";
    String creator_longname_italian "Agenzia Regionale per la Protezione dell'Ambiente del Friuli Venezia Giulia";
    String creator_name "CRMA - Regional Center for Environmental Modelling";
    String creator_url "https://www.arpa.fvg.it/";
    String CRMA_ID_code "2397F100D2_0022";
    String date_issued "2026-01-01";
    String department_acronym "CRMA";
    String department_longname_english "Regional Center for Environmental Modelling";
    String department_longname_italian "Centro Regionale di Modellistica Ambientale";
    String description_english "This is a climate perturbed hydrodynamic simulation identified with the code 2397F100D2_0022, generated in the frame of the Interreg IT-HR AdriaClimPlus project by CRMA – ARPA FVG. The simulation has been run with SHYFEM version 8.1.0, over the northernmost part of the Adriatic Sea, including the Gulf of Trieste and Marano-Grado Lagoon. It has been obtained by perturbing the inputs (marine initial and boundary conditions, hydrological boundary conditions and atmospheric forcing) of the benchmark 2395F100D2_0000, such that the covered 10-year period 2011-2020 corresponds to a 2.0 °C Global Warming Level (GWL). The atmospheric forcing comes from the NAUSICA reanalysis (1390FA01D0_2011 ÷ 1390FA01D0_2020) perturbed with the EURO-CORDEX simulation ran by SMHI (GCM: ICHEC-EC-EARTH, RCM: RCA4, ensemble member: r12i1p1). The hydrological boundary conditions come from the hydrological perturbed simulation 2394FA00D2_0022, carried out by CRMA – ARPA FVG through the WRF-Hydro model in the frame of the AdriaClimPlus project. The marine initial and boundary conditions come from CMEMS “Mediterranean Sea Physics Reanalysis” perturbed with the Med-CORDEX simulation ran by CLMcom-GUF (GCM: ICHEC-EC-EARTH, RCM: CLMcom-GUF-CCLM5-0-9-NEMOMED12-3-6, ensemble member: r12i1p1). The output 3D variables are salinity, water temperature, eastward current velocity (u_velocity) and northward current velocity (v_velocity), while the 2D variable is the dynamic component of sea surface height (ssh). The values are daily statistics: mean, minimum, median and maximum, computed from hourly instantaneous values. This dataset refers to 3d daily temperature, (mean, min, median and max)";
    String description_italian "Si tratta di una simulazione climatica idrodinamica identificata con il codice 2397F100D2_0022, prodotta dal CRMA - ARPA FVG nell'ambito del progetto Interreg IT-HR AdriaClimPlus. Questa simulazione è stata realizzata utilizzando il modello SHYFEM versione 8.1.0, sulla zona più settentrionale del Mar Adriatico, compresi il Golfo di Trieste e la Laguna di Marano-Grado. È stata ottenuta perturbando l’input (condizioni marine iniziali, condizioni al contorno idrologiche e forzante atmosferico) del benchmark 2395F100D2_0000, il periodo simulato è di 10 anni, dal 2011 al 2020, e si riferisce al livello di riscaldamento globale (GWL) ossia il GWL 2.0 °C. Il forzante atmosferico risulta da una rianalisi NAUSICA (1390FA01D0_2011 ÷ 1390FA01D0_2020) perturbata con la simulazione EURO-CORDEX eseguita da SMHI (GCM: ICHEC-EC-EARTH, RCM: RCA4, ensemble member: r12i1p1). Le condizioni al contorno idrologiche derivano dalla simulazione idrologica perturbata 2394FA00D2_0022, realizzato dal CRMA - ARPA FVG tramite il modello WRF-Hydro nell’ambito del progetto AdriaClimPlus. Le condizioni marine iniziali e quelle al contorno provengono dal Copernicus Marine Environment Monitoring Service (CMEMS) “Rianalisi della fisica del Mar Mediterraneo” perturbate con le simulazioni Med-CORDEX eseguite da CLMcom-GUF (GCM: ICHEC-EC-EARTH, RCM: CLMcom-GUF-CCLM5-0-9-NEMOMED12-3-6, ensemble member: r12i1p1). I risultati delle variabili 3D sono: la salinità, la temperatura dell'acqua, la velocità della corrente verso est (u_velocity) e la velocità della corrente verso nord (v_velocity); mentre la variabile 2D è la componente dinamica dell’altezza della superficie del mare (ssh). I valori sono le statistiche giornaliere: media, minima, mediana e massima, calcolate partendo dai valori orari. Questo set di dati si riferisce a: 3d daily temperature, (media, min, mediana e max)";
    String domain "single point";
    Float64 Easternmost_Easting 13.7599;
    String format "netCDF";
    String frequency "day";
    Float64 geospatial_lat_max 45.77096;
    Float64 geospatial_lat_min 45.23782;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 13.7599;
    Float64 geospatial_lon_min 12.77982;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 35.0;
    Float64 geospatial_vertical_min 0.5;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String GWL "GWL2.0";
    String history 
"2026-06-08T19:49:11Z https://fenice.arpa.fvg.it/geonetwork/
2026-06-08T19:49:11Z https://erddap-adriaclim.cmcc-opa.eu/tabledap/AdriaClimPlus_2397F100D2_0022_3d-day-temperature.das";
    String infoUrl "https://fenice.arpa.fvg.it/geonetwork/";
    String institution "ARPA FVG";
    String issued "01/01/2026";
    String keywords "AdriaClimPlus, Archivio, SHYFEM, WRF Hydro";
    String language "English";
    String license "CC BY";
    String medium "online";
    String metadata_Conventions "ISO 19115";
    Float64 Northernmost_Northing 45.77096;
    String project "AdriaClimPlus";
    String publisher "CRMA";
    String publisher_email "crma@arpa.fvg.it";
    String publisher_name "CRMA - Regional Center for Environmental Modelling";
    String publisher_url "https://www.arpa.fvg.it/";
    String references "Model info: http://www.ismar.cnr.it/shyfem";
    String rights "ARPA FVG";
    String simulation_id "2397F100D2_0022";
    String simulation_type "perturbation of benchmark";
    String source "Model data produced by SHYFEM at ISMAR-CNR";
    String sourceUrl "https://fenice.arpa.fvg.it/geonetwork/";
    Float64 Southernmost_Northing 45.23782;
    String subject_english "AdriaClimPlus - Progetto Interreg IT-HR - climate scenario 2397F100D2_0022 - Perturbed 2.0 - 3d-day-temperature";
    String subject_italian "AdriaClimPlus - Progetto Interreg IT-HR - scenario climatico 2397F100D2_0022 - Perturbed 2.0 - 3d-day-temperature";
    String subsetVariables "latitude, longitude, node_id, depth";
    String summary "This is a climate perturbed hydrodynamic simulation identified with the code 2397F100D2_0022, generated in the frame of the Interreg IT-HR AdriaClimPlus project by CRMA – ARPA FVG. The simulation has been run with SHYFEM version 8.1.0, over the northernmost part of the Adriatic Sea, including the Gulf of Trieste and Marano-Grado Lagoon. It has been obtained by perturbing the inputs (marine initial and boundary conditions, hydrological boundary conditions and atmospheric forcing) of the benchmark 2395F100D2_0000, such that the covered 10-year period 2011-2020 corresponds to a 2.0 °C Global Warming Level (GWL). The atmospheric forcing comes from the NAUSICA reanalysis (1390FA01D0_2011 ÷ 1390FA01D0_2020) perturbed with the EURO-CORDEX simulation ran by SMHI (GCM: ICHEC-EC-EARTH, RCM: RCA4, ensemble member: r12i1p1). The hydrological boundary conditions come from the hydrological perturbed simulation 2394FA00D2_0022, carried out by CRMA – ARPA FVG through the WRF-Hydro model in the frame of the AdriaClimPlus project. The marine initial and boundary conditions come from CMEMS “Mediterranean Sea Physics Reanalysis” perturbed with the Med-CORDEX simulation ran by CLMcom-GUF (GCM: ICHEC-EC-EARTH, RCM: CLMcom-GUF-CCLM5-0-9-NEMOMED12-3-6, ensemble member: r12i1p1). The output 3D variables are salinity, water temperature, eastward current velocity (u_velocity) and northward current velocity (v_velocity), while the 2D variable is the dynamic component of sea surface height (ssh). The values are daily statistics: mean, minimum, median and maximum, computed from hourly instantaneous values.";
    String summary_english "AdriaClimPlus - Interreg IT-HR Project - 3d daily temperature Perturbed 2.0";
    String summary_italian "AdriaClimPlus - Progetto Interreg IT-HR - 3d daily temperature Perturbed 2.0";
    String time_coverage_end "2020-12-31T12:00:00Z";
    String time_coverage_start "2011-01-01T12:00:00Z";
    String title "Project AdriaClimPlus | SHYFEM | 3d-day-temperature | Perturbed 2.0 | ID 2397F100D2_0022";
    Float64 Westernmost_Easting 12.77982;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.