Make A Graph

Dataset Title:	INGVXBT - Collection of sea temperature (TEMP) Profiles - METADATA
Institution:	INGVXBT (Dataset ID: XBT_ENEA_METADATA)
Range:	longitude = 8.2007 to 15.5951°E, latitude = 38.1372 to 44.3443°N
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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:

[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 "EMODNET Platform Code";
  }
  call_name {
    String long_name "Platform Call Name";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 38.1372, 44.3443;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 8.2007, 15.5951;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  dataFeatureType {
    String long_name "dataFeatureType";
  }
  firstDateObservation {
    Float64 actual_range 9.37857295e+8, NaN;
    String ioos_category "Time";
    String long_name "First Date Observation";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  lastDateObservation {
    Float64 actual_range 9.37857295e+8, NaN;
    String ioos_category "Time";
    String long_name "Last Date Observation";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  parameters_group_longname {
    String long_name "Parameters Info Parameter Groups";
  }
  parameters_group_P33 {
    String long_name "Parameters Info P33";
  }
  parameters {
    String long_name "Parameters Info Parameters";
  }
  parameters_P01 {
    String long_name "Parameters Info P01";
  }
  WMO {
    Int32 _FillValue 2147483647;
    String long_name "WMO";
  }
  data_DOI {
    String long_name "Data DOI";
  }
  best_practices_DOI {
    String long_name "Best Practices DOI";
  }
  data_owner_longname {
    String long_name "Data Owner Name";
  }
  data_owner_country_code {
    String long_name "Data Owner Country Code";
  }
  data_owner_country_longname {
    String long_name "Data Owner Country Name";
  }
  data_owner_EDMO {
    Int32 _FillValue 127;
    Int32 actual_range 136, 136;
    String long_name "Data Owner EDMO Code";
  }
  data_assembly_center_longname {
    String long_name "Data Assembly Center";
  }
  platform_type_longname {
    String long_name "Platform Type";
  }
  platform_type_SDNL06 {
    String long_name "Platform Type SDNL06";
  }
  platformpage_link {
    String long_name "Platformpage Page";
  }
  integrator_id {
    String long_name "Integrator Id";
  }
  IntegrationDate {
    Float64 actual_range 1.715684405e+9, NaN;
    String ioos_category "Time";
    String long_name "Integration Date";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  ingestion {
    String long_name "Ingestion";
  }
  official_repository {
    String long_name "Official Repository";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    Float64 Easternmost_Easting 15.5951;
    Float64 geospatial_lat_max 44.3443;
    Float64 geospatial_lat_min 38.1372;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 15.5951;
    Float64 geospatial_lon_min 8.2007;
    String geospatial_lon_units "degrees_east";
    String history 
"2026-04-03T04:33:07Z (local files)
2026-04-03T04:33:07Z https://erddap.s4raise.it/tabledap/XBT_ENEA_METADATA.das";
    String infoUrl "http://www.emodnet-physics.eu";
    String institution "INGVXBT";
    String keywords "assembly, best, best_practices_DOI, call, call_name, center, code, country, data, data_assembly_center_longname, data_DOI, data_owner_country_code, data_owner_country_longname, data_owner_EDMO, data_owner_longname, dataFeatureType, date, doi, edmo, feature, first, firstDateObservation, group, ingestion, integration, IntegrationDate, integrator, integrator_id, lastDateObservation, latitude, latitude2, link, local, longitude, longitude2, longname, meteorological, name, observation, official, official_repository, organisation, owner, p01, p33, parameters, parameters_group_longname, parameters_group_P33, parameters_P01, platform, platform_type_longname, platform_type_SDNL06, platformcode, platformpage, platformpage_link, practices, repository, sdnl06, source, type, wmo, world";
    String license "CC-BY";
    Float64 Northernmost_Northing 44.3443;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 38.1372;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "PLATFORMCODE";
    String summary "INGVXBT - Collection of sea temperature (TEMP) Profiles - METADATA";
    String testOutOfDate "now-2days";
    String title "INGVXBT - Collection of sea temperature (TEMP) Profiles - METADATA";
    Float64 Westernmost_Easting 8.2007;
  }
}

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