Make A Graph

Dataset Title:	Symphonie 3D (Z1, X, Y) mesh file "SIM7_3km_2001_2009" experiment.
Institution:	MIO UMR7294 CNRS / OSU Pytheas (Dataset ID: SIM7_3km_2001_2009_mesh3d)
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

Z1 (count)

specify just 1 value →

Y (count)

X (count)

Graph Settings
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

)

[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 {
  Z1 {
    Int32 actual_range 0, 39;
    String ioos_category "Unknown";
    String long_name "Z1";
    String units "count";
  }
  Y {
    Int16 actual_range 0, 114;
    String ioos_category "Location";
    String long_name "Y";
    String units "count";
  }
  X {
    Int16 actual_range 0, 338;
    String ioos_category "Location";
    String long_name "X";
    String units "count";
  }
  level_dpth3 {
    String associate "level_dpth3 lat3 lon3";
    String axis "ZYX";
    String ioos_category "Location";
    String long_name "levels depths3";
    Int32 type 1;
    String units "m";
  }
  level_dpth2 {
    String associate "level_dpth2 lat2 lon2";
    String axis "ZYX";
    String ioos_category "Location";
    String long_name "levels depths2";
    Int32 type 1;
    String units "m";
  }
  level_dpth {
    String associate "level_dpth lat lon";
    String axis "ZYX";
    String ioos_category "Location";
    String long_name "levels depths";
    Int32 type 1;
    String units "m";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "CF 1.0, COARDS, ACDD-1.3";
    String file_name "symphonie.nc";
    String grid_type "C";
    String history 
"Mon Mar  6 15:33:43 2017: ncks -O --mk_rec_dmn time 20010109_000000_8.nc 20010109_000000_8.nc
2024-04-16T14:01:53Z (local files)
2024-04-16T14:01:53Z http://erddap.osupytheas.fr/griddap/SIM7_3km_2001_2009_mesh3d.das";
    String infoUrl "https://dx.doi.org/10.1029/2011JC007074";
    String institution "MIO UMR7294 CNRS / OSU Pytheas";
    String keywords "data, depths, depths2, depths3, level_dpth, level_dpth2, level_dpth3, levels, local, source";
    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 "4.4.2";
    Int32 number_of_vartype 4;
    String production "POC 2003";
    String project "LATEX";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"These simulations are performed in the framework of the LATEX project
            Project Web Site:
            http://www.mio.univ-amu.fr/LATEX
            Review Paper:
            Petrenko, A.A., Doglioli, A.M., Nencioli, F., Kersale, M., Hu, Z., d'Ovidio, F. (accepted). A review of the LATEX project: mesoscale to submesoscale processes in a coastal environment. Ocean Dynam., doi:10.1007/s10236-017-1040-9.

            For detailed information on the model implementation the reader is referred to:
            - Hu, Z.H., Petrenko, A.A., Doglioli, A.M., Dekeyser, I. (2011). Numerical study of eddy generation in the western part of the Gulf of Lion. J. Geophys. Res., Vol.116, C12030, doi:10.1029/2011JC007074.
            - Kersale, M., Petrenko, A.A., Doglioli, A.M., Dekeyser, I., Nencioli, F. (2013). Physical characteristics and dynamics of the coastal Latex09 Eddy derived from in situ data and numerical modeling. J. Geophys. Res., Vol.118, pp.1-11, doi:10.1029/2012JC008229";
    String title "Symphonie 3D (Z1, X, Y) mesh file \"SIM7_3km_2001_2009\" experiment.";
  }
}

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.