Make A Graph

Dataset Title:	AMIS_DigTwin_Massa_griglia_utm32n_original
Institution:	Consorzio LaMMA (Dataset ID: amis_digtwin_massa_griglia_utm32n_original)
Information:	Summary \| License \| Metadata \| Background \| 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:

Dimensions

Start

Stop

ny (count)

nx (count)

specify just 1 value →

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

)

X 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 {
  ny {
    Int32 actual_range 0, 616;
    String ioos_category "Location";
    String long_name "indice di griglia ny";
    String units "count";
  }
  nx {
    Int16 actual_range 0, 566;
    String ioos_category "Location";
    String long_name "indice di griglia nx";
    String units "count";
  }
  globalx {
    UInt32 _ChunkSizes 617, 567;
    String axis "X";
    String ioos_category "Location";
    String long_name "x coordinate of projection";
    String standard_name "projection_x_coordinate";
    String units "m";
  }
  globaly {
    UInt32 _ChunkSizes 617, 567;
    String axis "Y";
    String ioos_category "Location";
    String long_name "y coordinate of projection";
    String standard_name "projection_y_coordinate";
    String units "m";
  }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.9.3,hdf5=1.14.6";
    String amis_file_origine "/DATA/DATI_AMIS/massa/aree_allagate/erddap_ready/utm/zs_max_rcp45_2050_ssh_020_hs_200_utm32n_cf.nc";
    String amis_griglia "griglia originale del modello XBeach, curvilinea e ruotata: gli assi nx, ny sono indici di griglia; le coordinate dei punti sono nelle variabili globalx, globaly (metri)";
    String amis_sistema_coordinate "UTM 32N (EPSG:32632): file della vista utm/ della catena AMIS di Massa (scripts/amis_prepare_utm_cf.py)";
    String amis_sito "Massa";
    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 "Grid";
    String CDO "Climate Data Operators version 1.9.8 (https://mpimet.mpg.de/cdo)";
    String Conventions "CF-1.4, COARDS, ACDD-1.3";
    String creator_name "Consorzio LaMMA";
    String creator_type "institution";
    String creator_url "https://www.lamma.toscana.it/";
    String history 
"Mon May 11 08:28:27 2026: cdo timmax -selname,zs /home/xbeach/dt_runs/runs/rcp45_2050/rcp45_2050_ssh020_hs200/rcp45_2050_ssh_020_hs_200.nc /home/xbeach/dt_runs/output_inviluppo/zs_max_rcp45_2050_ssh_020_hs_200.nc
Prepared for ERDDAP CF publication: UTM EPSG:32632
2026-11-15T00:13:05Z (local files)
2026-11-15T00:13:05Z https://erddap.lamma.toscana.it/griddap/amis_digtwin_massa_griglia_utm32n_original.das";
    String infoUrl "https://www.lamma.toscana.it/";
    String institution "Consorzio LaMMA";
    String keywords "AMIS, Digital Twin, griglia, Massa, XBeach";
    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 Producer "XBeach littoral zone wave model (http://www.xbeach.org)";
    String project "AMIS Digital Twin";
    String sourceUrl "(local files)";
    String summary "AMIS Digital Twin, Massa: coordinate UTM 32N (globalx, globaly) della griglia del modello, comune a tutti gli scenari: collocano gli indici nx, ny dei dataset Massa *_utm32n_original.";
    String title "AMIS_DigTwin_Massa_griglia_utm32n_original";
    String URL "URL: https://svn.oss.deltares.nl/repos/xbeach/tags/2023-10-31-XBeach-v1.24.6057-Halloween_BETA";
  }
}

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its projection 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. It makes 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/jplMURSST41.htmlTable?analysed_sst[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.