Make A Graph

Dataset Title:	CURRISO timeSeries, NRT in situ Observations
Institution:	Protezione Civile - Friuli Venezia Giulia (Dataset ID: CURRISO_TS)
Range:	longitude = 13.496333 to 13.496333°E, latitude = 45.761665 to 45.761665°N, time = 2021-01-01T00:00:00Z to (now?)
Information:	Summary \| License \| FGDC \| ISO 19115 \| 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:

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 1.6094592e+9, NaN;
    String axis "T";
    String cf_role "timeseries_id";
    String ioos_category "Time";
    String long_name "Time";
    String sdn_parameter_name "Elapsed time relative to 1970-01-01T00:00:00Z";
    String sdn_parameter_urn "SDN:P01::ELTMEP01";
    String sdn_uom_name "Seconds";
    String sdn_uom_urn "SDN:P06::UTBB";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 45.7616667, 45.7616667;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String sdn_parameter_name "Latitude north";
    String sdn_parameter_urn "SDN:P01::ALATZZ01";
    String sdn_uom_name "Degrees north";
    String sdn_uom_urn "SDN:P06::DEGN";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 13.4963333, 13.4963333;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String sdn_parameter_name "Longitude east";
    String sdn_parameter_urn "SDN:P01::ALONZZ01";
    String sdn_uom_name "Degrees east";
    String sdn_uom_urn "SDN:P06::DEGE";
    String standard_name "longitude";
    String units "degrees_east";
  }
  PRES {
    Float32 _FillValue -999.0;
    String ancillary_variables "PRES_QC";
    String data_mode "R";
    String ioos_category "Pressure";
    String long_name "Sea pressure";
    String sdn_parameter_name "Depth (spatial coordinate) relative to water surface in the water body";
    String sdn_parameter_urn "SDN:P01::ADEPZZ01";
    String sdn_uom_name "Decibars";
    String sdn_uom_urn "SDN:P06::UPDB";
    String sensor_mount "mounted_on_fixed_structure";
    String standard_name "sea_water_pressure";
    String units "dbar";
  }
  PRES_QC {
    Byte _FillValue -127;
    String _Unsigned "false";
    Byte colorBarMaximum 9;
    Byte colorBarMinimum 0;
    String conventions "Copernicus Marine In Situ reference table 2";
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed value_below_detection nominal_value interpolated_value missing_value";
    Byte flag_values 0, 1, 2, 3, 4, 5, 6, 7, 8, 9;
    String ioos_category "Quality";
    String long_name "Sea pressure quality flag";
    String standard_name "quality_flag";
    Byte valid_max 9;
    Byte valid_min 0;
  }
  TEMP {
    Float32 _FillValue -999.0;
    String ancillary_variables "TEMP_QC";
    String data_mode "R";
    String ioos_category "Temperature";
    String long_name "Sea temperature";
    String sdn_parameter_name "Temperature of the water body";
    String sdn_parameter_urn "SDN:P01::TEMPPR01";
    String sdn_uom_name "Degrees Celsius";
    String sdn_uom_urn "SDN:P06::UPAA";
    String sensor_mount "mounted_on_fixed_structure";
    String standard_name "sea_water_temperature";
    String units "degrees_C";
  }
  TEMP_QC {
    Byte _FillValue -127;
    String _Unsigned "false";
    Byte colorBarMaximum 9;
    Byte colorBarMinimum 0;
    String conventions "Copernicus Marine In Situ reference table 2";
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed value_below_detection nominal_value interpolated_value missing_value";
    Byte flag_values 0, 1, 2, 3, 4, 5, 6, 7, 8, 9;
    String ioos_category "Quality";
    String long_name "Sea temperature quality flag";
    String standard_name "quality_flag";
    Byte valid_max 9;
    Byte valid_min 0;
  }
  RVFL {
    Float32 _FillValue -999.0;
    String ancillary_variables "RVFL_QC";
    String data_mode "R";
    String ioos_category "Hydrology";
    String long_name "River flow rate";
    String sdn_parameter_name "Riverine discharge of water by direct reading current meter and calculation from flow";
    String sdn_parameter_urn "SDN:P01::RFDSCH02";
    String sdn_uom_name "Cubic metres per second";
    String sdn_uom_urn "SDN:P06::CMPS";
    String sensor_mount "mounted_on_fixed_structure";
    String standard_name "water_volume_transport_into_sea_water_from_rivers";
    String units "m3 s-1";
  }
  RVFL_QC {
    Byte _FillValue -127;
    String _Unsigned "false";
    Byte colorBarMaximum 9;
    Byte colorBarMinimum 0;
    String conventions "Copernicus Marine In Situ reference table 2";
    String flag_meanings "no_qc_performed good_data probably_good_data bad_data_that_are_potentially_correctable bad_data value_changed value_below_detection nominal_value interpolated_value missing_value";
    Byte flag_values 0, 1, 2, 3, 4, 5, 6, 7, 8, 9;
    String ioos_category "Quality";
    String long_name "River flow rate quality flag";
    String standard_name "quality_flag";
    Byte valid_max 9;
    Byte valid_min 0;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "time,latitude,longitude";
    String contributor_name "National Institute of Oceanography and Applied Geophysics - OGS, Division of Oceanography";
    String Conventions "CF-1.6, Copernicus-InSituTAC-FormatManual-1.42, Copernicus-InSituTAC-SRD-1.5, Copernicus-InSituTAC-ParametersList-3.2.0, COARDS, ACDD-1.3, OceanSITES v1.4, SeaDataNet_1.0";
    String creator_name "Protezione Civile - Friuli Venezia Giulia";
    String creator_type "institution";
    String data_mode "R";
    String data_type "OceanSITES time-series data";
    String date_created "44197";
    Float64 Easternmost_Easting 13.4963333;
    String featureType "TimeSeries";
    String format_version "1.4";
    Float64 geospatial_lat_max 45.7616667;
    Float64 geospatial_lat_min 45.7616667;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 13.4963333;
    Float64 geospatial_lon_min 13.4963333;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_max "25";
    String geospatial_vertical_min "0";
    String history 
"river station
2025-10-25T16:15:15Z (source database)
2025-10-25T16:15:15Z https://nodc.ogs.it/tabledap/CURRISO_TS.das";
    String infoUrl "https://nodc.ogs.it";
    String institution "Protezione Civile - Friuli Venezia Giulia";
    String institution_edmo_code "1613";
    String keywords "AHGT, ALAT, AYMD, RVDS, TEMP";
    String keywords_vocabulary "SeaDataNet Parameter Discovery Vocabulary";
    String license "CC-BY-4.0";
    String network "OceanSITES";
    Float64 Northernmost_Northing 45.7616667;
    String platform_code "CURRISO";
    String principal_investigator "Fabio Brunetti";
    String principal_investigator_email "fbrunetti@ogs.it";
    String project "Monitoraggio-FVG";
    String publisher_email "nodc@ogs.it";
    String publisher_name "National Institute of Oceanography and Applied Geophysics - OGS, Division of Oceanography";
    String site_code "CURRISO";
    String source "river station";
    String source_platform_category_code "18";
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing 45.7616667;
    String standard_name_vocabulary "CF Standard Name Table v78";
    String summary "CURRISO timeSeries, NRT in situ Observations";
    String time_coverage_start "2021-01-01T00:00:00Z";
    String title "CURRISO timeSeries, NRT in situ Observations";
    String update_interval "void";
    Float64 Westernmost_Easting 13.4963333;
  }
}

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.

ERDDAP, Version 2.18
Disclaimers | Privacy Policy | Contact