Make A Graph

Dataset Title:	NAUTILOS - SOMA daily averaged 3D fields forecast (DAILY 3D 1km best) [time], 2022-present - UAlg
Institution:	UAlg (Dataset ID: hydroSOMA_model_daily_1km_3_ualg)
Information:	Summary \| License \| Metadata \| Background \| Data Access Form

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

time (UTC)

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:

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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6723584e+9, 1.7492544e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Forecast time for ForecastModelRunCollection";
    Float64 missing_value NaN;
    String parameter_sdn_name "Elapsed time";
    String parameter_sdn_uri "https://vocab.nerc.ac.uk/collection/P01/current/ELTMZZZZ/";
    String parameter_sdn_urn "SDN:P01::ELTMZZZZ";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String unit_sdn_name "Seconds";
    String unit_sdn_uri "https://vocab.nerc.ac.uk/collection/P06/current/UTBB/";
    String unit_sdn_urn "SDN:P06::UTBB";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time_run {
    String _CoordinateAxisType "RunTime";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "run times for coordinate = time";
    String parameter_sdn_name "Elapsed time";
    String parameter_sdn_uri "https://vocab.nerc.ac.uk/collection/P01/current/ELTMZZZZ/";
    String parameter_sdn_urn "SDN:P01::ELTMZZZZ";
    String standard_name "forecast_reference_time";
    String time_origin "01-JAN-1970 00:00:00";
    String unit_sdn_name "Seconds";
    String unit_sdn_uri "https://vocab.nerc.ac.uk/collection/P06/current/UTBB/";
    String unit_sdn_urn "SDN:P06::UTBB";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time_offset {
    String _CoordinateAxisType "TimeOffset";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "offset hour from start of run for coordinate = time";
    String parameter_sdn_name "Elapsed time";
    String parameter_sdn_uri "https://vocab.nerc.ac.uk/collection/P01/current/ELTMZZZZ/";
    String parameter_sdn_urn "SDN:P01::ELTMZZZZ";
    String standard_name "forecast_period";
    String time_origin "01-JAN-1970 00:00:00";
    String unit_sdn_name "Seconds";
    String unit_sdn_uri "https://vocab.nerc.ac.uk/collection/P06/current/UTBB/";
    String unit_sdn_urn "SDN:P06::UTBB";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String area "South Portugal";
    String cdm_data_type "Grid";
    String contact "https://www.cima.ualg.pt/en/contactos";
    String Conventions "CF-1.10, COARDS, ACDD-1.3";
    String creator_name "UAlg Centre for Marine and Environmental Research";
    String creator_type "institution";
    String creator_url "https://soma.ualg.pt";
    String history 
"FMRC Best Dataset
2025-06-07T04:51:19Z https://cima-somathredds.ualg.pt/thredds/dodsC/soma-fes14/daily-3D_1km/DAILY_3D_1km_best.ncd
2025-06-07T04:51:19Z https://data-nautilos-h2020.eu/griddap/hydroSOMA_model_daily_1km_3_ualg.das";
    String infoUrl "https://soma.ualg.pt";
    String inspire "Oceanographic geographical features";
    String institution "UAlg";
    String institution_country "PT";
    String institution_edmo_code "5675";
    String keywords "1km, averaged, best, centre, coordinate, daily, data, day, environmental, fields, forecast, forecast_period, forecast_reference_time, hour, marine, offset, period, reference, research, run, soma, start, time, time_offset, time_run, times, ualg";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY 4.0";
    String location "Proto fmrc:SOMA-3D_1km";
    String naming_authority "NAUTILOS";
    String project_code "NAUTILOS";
    String Project_DOI "https://doi.org/10.3030/101000825";
    String project_edmerp "13720";
    String project_id "101000825";
    String project_name "New Approach to Underwater Technologies for Innovative, Low-cost Ocean obServation";
    String project_statement "This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 101000825 (NAUTILOS). This output reflects only the author's view and the European Union cannot be held responsible for any use that may be made of the information contained therein";
    String references "https://soma.ualg.pt";
    String sourceUrl "https://cima-somathredds.ualg.pt/thredds/dodsC/soma-fes14/daily-3D_1km/DAILY_3D_1km_best.ncd";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "SOMA daily averaged 3D fields forecast (DAILY 3D 1km best)";
    String testOutOfDate "now+1day";
    String time_coverage_end "2025-06-07T00:00:00Z";
    String time_coverage_start "2022-12-30T00:00:00Z";
    String title "NAUTILOS - SOMA daily averaged 3D fields forecast (DAILY 3D 1km best) [time], 2022-present - UAlg";
    String variables "run times for coordinate, offset hour from start of run for coordinate";
  }
}

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.

ERDDAP, Version 2.18
Disclaimers | Privacy Policy | Contact