ERDDAP
Easier access to scientific data

Brought to you by

Make A Graph

Dataset Title:	Sea Surface Temperature data collected during Citizen Science activities using the Brizo device
Institution:	ETT (Dataset ID: brizo)
Range:	longitude = -4.768479 to 15.665458°E, latitude = 0.0 to 48.170094°N, time = 2018-06-25T17:00:00Z to 2025-03-20T15:01:06Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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 {
  platformcode {
    String long_name "Platformcode";
  }
  mission {
    String long_name "Mission";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.529946e+9, 1.742482866e+9;
    String axis "T";
    Float64 colorBarMaximum 1.75e+9;
    Float64 colorBarMinimum 1.5e+9;
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 0.0, 48.17009283333334;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -4.768478900000001, 15.665458166666667;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  temperature {
    Float32 actual_range 0.0, 281258.28;
    Float64 colorBarMaximum 300000.0;
    Float64 colorBarMinimum 0.0;
    String long_name "Temperature";
  }
  timestamp {
    Float64 actual_range 0.0, 1.742569206291e+9;
    Float64 colorBarMaximum 2.0e+9;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Time";
    String long_name "Timestamp";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.000Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  author {
    String long_name "Author";
  }
  command {
    Float32 actual_range 0.0, 0.0;
    String long_name "Command";
  }
 }
  NC_GLOBAL {
    String acquisition_methodology "Brizo tracker";
    String acquisition_mode "delayed";
    String cdm_data_type "Point";
    String contributors_email "giulia.dapueto@dedagroup.it; antonio.novellino@dedagroup.it";
    String contributors_name "Dapueto, Giulia; Novellino, Antonio";
    String contributors_orcid "0000-0002-3263-5583; 0000-0003-4020-2056";
    String contributors_role "data collector; data curator";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info.ett@dedagroup.it";
    String creator_name "ETT";
    String creator_type "institution";
    String creator_url "https://ettsolutions.com/smartcity/";
    String data_doi "10.5281/zenodo.17572696";
    String data_format_original "csv";
    String data_version "1";
    String distribution "https://s4raise.it/dssmare/citizen_science/";
    String documentation "https://s4raise.it/dssmare/citizen_science/, https://raise-spoke3.s4raise.it/project11";
    Float64 Easternmost_Easting 15.665458166666667;
    String featureType "Point";
    Float64 geospatial_lat_max 48.17009283333334;
    Float64 geospatial_lat_min 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 15.665458166666667;
    Float64 geospatial_lon_min -4.768478900000001;
    String geospatial_lon_units "degrees_east";
    String history 
"2026-04-02T20:17:14Z (local files)
2026-04-02T20:17:14Z http://erddap.s4oceandata.eu/erddap/tabledap/brizo_raise.das
2026-04-03T04:34:24Z https://erddap.s4oceandata.eu/erddap/tabledap/brizo_raise
2026-04-03T04:34:24Z https://erddap.s4raise.it/tabledap/brizo.das";
    String infoUrl "https://www.raiseliguria.it/spoke-3/";
    String inspire "Oceanographic geographical features";
    String institution "ETT";
    String institution_country "IT";
    String institution_edmo_code "2764";
    String keywords "Water Temperature (46206e8c-8def-406f-9e62-da4e74633a58)";
    String keywords_vocabulary "GCMD Science Keywords";
    String language "XML";
    String license "CC-BY 4.0";
    String maintainer "ETT S.p.A.";
    String naming_authority "RAISE";
    Float64 Northernmost_Northing 48.17009283333334;
    String owner "ETT";
    String owner_url "https://ettsolutions.com/smartcity/";
    String project_code "RAISE";
    String project_id "ECS00000035";
    String project_name "Robotics and AI for Socio-economic Empowerment";
    String project_statement "RAISE: Robotics and AI for Socio-economic Empowerment is an innovation ecosystem funded by the Ministry of University and Research under the National Recovery and Resilience Plan (NRRP, Mission 4, Component 2, Investment 1.5)";
    String project_url "https://www.raiseliguria.it/";
    String publisher "ETT S.p.A.";
    String references "10.5281/zenodo.17572696";
    String sensors "Brizo tracker";
    String source "Data was collected by citizens by using Brizo sensors";
    String sourceUrl "https://erddap.s4oceandata.eu/erddap/tabledap/brizo_raise";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "platformcode, mission, time, latitude, longitude, temperature, timestamp, author, command";
    String summary "Brizo is a smart temperature logger to support marine environmental research. The system offers data in near real time.";
    String theme_eu_data "http://publications.europa.eu/resource/authority/data-theme/ENVI";
    String theme_eurovoc "http://publications.europa.eu/resource/authority/eurovoc/100224";
    String time_coverage_end "2025-03-20T15:01:06Z";
    String time_coverage_start "2018-06-25T17:00:00Z";
    String title "Sea Surface Temperature data collected during Citizen Science activities using the Brizo device";
    String visibility "public";
    Float64 Westernmost_Easting -4.768478900000001;
  }
}

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.25_1
Disclaimers | Privacy Policy | Contact