Make A Graph

Dataset Title:	AMIS_DigTwin_Massa_zs_max_rcp85_2100_ssh_040_hs_250_table
Institution:	Consorzio LaMMA (Dataset ID: amis_digtwin_massa_zs_max_rcp85_2100_ssh_040_hs_250_table)
Range:	longitude = 10.087821 to 10.131423°E, latitude = 43.9745 to 44.00601°N, time = 1970-01-01T00:00:00Z to 1970-01-01T00: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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 0.5, 0.5;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  row {
    Int32 actual_range 0, 410921;
    String ioos_category "Unknown";
    String long_name "row index";
  }
  ny_index {
    Int32 actual_range 0, 616;
    String ioos_category "Statistics";
    String long_name "original ny index";
  }
  nx_index {
    Int32 actual_range 0, 665;
    String ioos_category "Statistics";
    String long_name "original nx index";
  }
  x {
    Float64 actual_range 587231.2853038391, 590724.1465637473;
    String ioos_category "Location";
    String long_name "UTM x coordinate";
    String standard_name "projection_x_coordinate";
    String units "m";
  }
  y {
    Float64 actual_range 4869640.58, 4873136.988823077;
    String ioos_category "Location";
    String long_name "UTM y coordinate";
    String standard_name "projection_y_coordinate";
    String units "m";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 10.087821136086342, 10.13142342699937;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 43.97450055935762, 44.00600670085493;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  zs {
    Float32 _FillValue -3.402823e+38;
    Float32 actual_range 1.0536, 2.707939;
    String cell_methods "globaltime: maximum";
    String ioos_category "Sea Level";
    String long_name "water level";
    Float32 missing_value -3.402823e+38;
    String standard_name "sea_surface_height_above_sea_level";
    String units "m";
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.9.3,hdf5=1.14.6";
    String Build_Date "Fri Jan 16 13:15:32 UTC 2026";
    String Build_Revision "6139M";
    String CDI "Climate Data Interface version 1.9.8 (https://mpimet.mpg.de/cdi)";
    String cdm_data_type "Point";
    String CDO "Climate Data Operators version 1.9.8 (https://mpimet.mpg.de/cdo)";
    String Conventions "CF-1.10, ACDD-1.3, COARDS";
    String creator_name "Consorzio LaMMA";
    String creator_type "institution";
    String creator_url "https://www.lamma.toscana.it/";
    Float64 Easternmost_Easting 10.13142342699937;
    String featureType "Point";
    Float64 geospatial_lat_max 44.00600670085493;
    Float64 geospatial_lat_min 43.97450055935762;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 10.13142342699937;
    Float64 geospatial_lon_min 10.087821136086342;
    String geospatial_lon_units "degrees_east";
    String history 
"Mon May 18 10:28:52 2026: ncks -O -d ny,50,666 zs_max_rcp85_2100_ssh_040_hs_250.nc zs_max_rcp85_2100_ssh_040_hs_250_clip.nc
Mon May 11 09:42:57 2026: cdo timmax -selname,zs /home/xbeach/dt_runs/runs/rcp85_2100/rcp85_2100_ssh040_hs250/rcp85_2100_ssh_040_hs_250.nc /home/xbeach/dt_runs/output_inviluppo/zs_max_rcp85_2100_ssh_040_hs_250.nc
Converted to flat table for ERDDAP EDDTableFromNcFiles publication
2026-06-10T06:06:43Z (local files)
2026-06-10T06:06:43Z https://erddap.lamma.toscana.it/tabledap/amis_digtwin_massa_zs_max_rcp85_2100_ssh_040_hs_250_table.das";
    String infoUrl "https://www.lamma.toscana.it/";
    String institution "Consorzio LaMMA";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String NCO "netCDF Operators version 4.7.5 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 44.00600670085493;
    String Producer "XBeach littoral zone wave model (http://www.xbeach.org)";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 43.97450055935762;
    String subsetVariables "time";
    String summary "AMIS_DigTwin_Massa_zs_max_rcp85_2100_ssh_040_hs_250_table - vista tabellare puntuale per scenario AMIS DigTwin Massa.";
    String time_coverage_end "1970-01-01T00:00:00Z";
    String time_coverage_start "1970-01-01T00:00:00Z";
    String title "AMIS_DigTwin_Massa_zs_max_rcp85_2100_ssh_040_hs_250_table";
    String URL "URL: https://svn.oss.deltares.nl/repos/xbeach/tags/2023-10-31-XBeach-v1.24.6057-Halloween_BETA";
    Float64 Westernmost_Easting 10.087821136086342;
  }
}

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.