Make A Graph

Dataset Title:	NAUTILOS - Temperature profiles 2012-2020 - Fishing Vessels profiles by AdriFOOS platform - CNR IRBIM
Institution:	CNR IRBIM (Dataset ID: AdriFOOS_profiles_2012-2020)
Range:	longitude = 12.4062 to 18.60072°E, latitude = 40.39051 to 44.97817°N, time = 2012-11-26T05:12:52Z to 2020-02-26T11:43:25Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| 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:

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 {
  Cruise {
    String long_name "Cruise";
  }
  Station {
    Int16 _FillValue 32767;
    Int16 actual_range 1, 154;
    String long_name "Station";
  }
  Type {
    String long_name "Type";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.353906772e+9, 1.582717405e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "YYYY-MM-DD THH:MM:SS.SSS";
    String source_name "yyyy-mm-ddThh:mm:ss.sss";
    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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 12.4062, 18.60072;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "Longitude [degrees_east]";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 40.39051, 44.97817;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "Latitude [degrees_north]";
    String standard_name "latitude";
    String units "degrees_north";
  }
  SN {
    String long_name "SN";
  }
  Pressure {
    Float64 _FillValue NaN;
    Float64 actual_range -1.93, 288.089996;
    String long_name "Pressure";
    String units "dbar";
  }
  QV_SEADATANET {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 9;
    String long_name "QV:SEADATANET";
  }
  Temperature {
    Float64 _FillValue NaN;
    Float64 actual_range 6.29, 28.93;
    String long_name "Temperature";
    String SDN "SDN:P01::TEMPPR01";
    String units "degrees_C";
  }
  QV_SEADATANET_1 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 9;
    String long_name "QV:SEADATANET.1";
  }
  QV_ODV_SAMPLE {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 1;
    String long_name "QV:ODV:SAMPLE";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String contributors_email "pierluigi.penna@cnr.it, andrea.belardinelli@cnr.it, , filippo.domenichetti@cnr.it, michela.martinelli@cnr.it";
    String contributors_name "Penna Pierluigi; Belardinelli Andrea; Domenichetti Filippo; Martinelli Michela";
    String contributors_orcid "0000-0003-1806-1576; ; 0000-0002-8052-7544; 0000-0003-1231-2346";
    String contributors_role "data curation, investigation, methodology, software, supervision, validation; funding acquisition, investigation, methodology, supervision; investigation; data curation, funding acquisition, investigation, methodology, project administration, software, supervision, validation";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "pierluigi.penna@cnr.it";
    String creator_name "Pierluigi Penna";
    String creator_type "institution";
    String creator_url "https://www.irbim.cnr.it/";
    String data_doi "https://doi.org/10.17882/73008";
    Float64 Easternmost_Easting 18.60072;
    String featureType "Point";
    Float64 geospatial_lat_max 44.97817;
    Float64 geospatial_lat_min 40.39051;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 18.60072;
    Float64 geospatial_lon_min 12.4062;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-23T14:15:45Z (local files)
2024-11-23T14:15:45Z http://data-nautilos-h2020.eu/tabledap/AdriFOOS_profiles_2012-2020.das";
    String infoUrl "https://doi.org/10.5194/essd-15-3513-2023";
    String inspire "Oceanographic geographical features";
    String institution "CNR IRBIM";
    String institution_country "IT";
    String institution_edmo_code "1367";
    String keywords "cruise, data, dbar, latitude, longitude, ocean, pressure, QV_ODV_SAMPLE, QV_SEADATANET, QV_SEADATANET_1, source, station, temperature, time, type.";
    String license "CC-BY 4.0";
    String naming_authority "NAUTILOS";
    Float64 Northernmost_Northing 44.97817;
    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 reference "https://doi.org/10.17882/73008";
    String source "CNR-IRBIM implemented the \"AdriFOOS\" observational system, by installing the FOOS on some commercial fishing boats operating in the Adriatic Sea. Since then the datacenter based in Ancona receives daily data sets of environmental parameters collected along the water column and close to the sea bottom (eg. temperature, salinity, etc.), together with GPS haul tracks, catch amounts per haul, target species sizes and weather information. Some temperature and salinity measurements acquired by the FOOS in the Adriatic Sea from January 2014 to March 2015 were published within the JERICO project and some oxygen and fluorescence profiles obtained in 2017 within the NEXOS project.";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 40.39051;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "CNR-IRBIM implemented the \"AdriFOOS\" observational system, by installing the FOOS on some commercial fishing boats operating in the Adriatic Sea. Since then the datacenter based in Ancona receives daily data sets of environmental parameters collected along the water column and close to the sea bottom (eg. temperature, salinity, etc.), together with GPS haul tracks, catch amounts per haul, target species sizes and weather information. Some temperature and salinity measurements acquired by the FOOS in the Adriatic Sea from January 2014 to March 2015 were published within the JERICO project and some oxygen and fluorescence profiles obtained in 2017 within the NEXOS project.";
    String time_coverage_end "2020-02-26T11:43:25Z";
    String time_coverage_start "2012-11-26T05:12:52Z";
    String title "NAUTILOS - Temperature profiles 2012-2020 - Fishing Vessels profiles by AdriFOOS platform - CNR IRBIM";
    String variables "Type, Cruise, Station, time, longitude, latitude, SN, Pressure, QV_SEADATANET, Temperature, QV_SEADATANET_1, QV_ODV_SAMPLE";
    Float64 Westernmost_Easting 12.4062;
  }
}

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