POLARIN ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	KIM Mooring T data @ 180m (vws21g)
Institution:	Italian National Research Council - Institute of Polar Sciences (Dataset ID: cnr_iadc_f5ff_4134_70dd)
Range:	longitude = 11.7237 to 11.72488°E, latitude = 79.12711 to 79.12797°N, depth = 180.0 to 294.0m, time = 2023-09-11T10:55:07Z to 2025-06-13T12:54:29Z
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.694429707e+9, 1.749819269e+9;
    String axis "T";
    Float64 colorBarMaximum 1.74e+9;
    Float64 colorBarMinimum 1.66e+9;
    String ioos_category "Time";
    String long_name "time of measurement";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String uncertainty "0.0035";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 79.12711, 79.12797;
    String axis "Y";
    String colorBarMaximum "90.0";
    String colorBarMinimum "-90.0";
    String comment "Surveyed mooring position";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "latitude of measurement";
    String references "WGS84";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue 9.96921e+36;
    Float32 actual_range 11.7237, 11.724883;
    String axis "X";
    String colorBarMaximum "180.0";
    String colorBarMinimum "-180.0";
    String comment "Surveyed mooring position";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::4326";
    String ioos_category "Location";
    String long_name "Longitude of measurement";
    String references "WGS84";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 180.0, 294.0;
    String axis "Z";
    String colorBarMaximum "8000.0";
    String colorBarMinimum "-8000.0";
    String colorBarPalette "TopographyDepth";
    String comment "Depth calculated from mooring diagram and other sensors";
    String coordinate_reference_frame "urn:ogc:def:crs:EPSG::5831";
    String ioos_category "Location";
    String long_name "Nominal Depth of sensor";
    String positive "down";
    String references "sea_level";
    String standard_name "depth";
    String units "m";
  }
  TEMP {
    Float32 _FillValue NaN;
    String accuracy "0.002";
    Float32 actual_range -0.1819, 4.752;
    String BODC_approved_data_storage_units "SDN:P06::UPAA";
    String BODC_Parameter_Usage_Vocabulary "SDN:P01::TEMPS901";
    String calibration_date "13-05-2011";
    String colorBarMaximum "32.0";
    String colorBarMinimum "0.0";
    String data_type "DMT";
    String Discipline "SDN:P08::DS03";
    String Discovery_parameter "SDN:P02::TEMP";
    String ioos_category "Temperature";
    String long_name "Temperature of the water column";
    String Parameter_Group "SDN:P03::D025";
    String QC_procedures "SDN:L12::D";
    String reference_scale "ITS-90";
    String sensor_data_end_date "2023-08-30T08:00:00Z";
    String sensor_data_start_date "2022-09-07T13:40:00Z";
    String sensor_depth "180.0";
    String sensor_manufacturer "Sea-Bird Scientific";
    String sensor_model "Sea-Bird SBE 56 temperature recorder";
    String sensor_mount "mounted_on_mooring_line";
    String sensor_SeaVoX_L22_code "SDN:L22::TOOL1393";
    String sensor_serial_number "05600575";
    String standard_name "sea_water_temperature";
    String Type_of_device "SDN:L05::134";
    String units "degree_Celsius";
    Float32 valid_max 45.0;
    Float32 valid_min -5.0;
  }
  TEMP_QC {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 0;
    String colorBarMaximum "10.0";
    String colorBarMinimum "0.0";
    String flag_values "0 1 2 3 4 5 7 8 9";
    String ioos_category "Quality";
    String L20_flag_meanings "0_no_qc_performed 1_good_value 2_probably_good_value3_probably_bad_value 4_bad_value5_changed_value 6_value_below_detection 7_value_in_excess8_interpolated_value 9_missing_value";
    String long_name "L20_quality control_flag";
  }
  station_id {
    String cf_role "timeseries_id";
    String ioos_category "Identifier";
    String long_name "Id of the station in the TimeSeries";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "station_id,latitude,longitude";
    String comment "The sensor during the 2023-2024 deployment period, addressing a mooring buoyancy issue, was positioned at a depth of 294 meters";
    String contributor_email "francesco.paladinidemendoza@cnr.it";
    String contributor_institution "CNR-ISP";
    String contributor_name "Francesco Paladini de Mendoza";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "francesco.paladinidemendoza@cnr.it";
    String creator_name "Italian National Research Council - Institute of Polar Sciences";
    String creator_url "https://www.isp.cnr.it/index.php/en/";
    String dataset_originator_person "Francesco Paladini de Mendoza";
    Float64 Easternmost_Easting 11.72488;
    String endpoint "https://data.iadc.cnr.it/erddap/info/index.html?page=1&itemsPerPage=1000";
    String Facility_reference_persons "Stefano Miserocchi; Leonardo Langone; Federico Giglio; Francesco Paladini de Mendoza";
    String featureType "TimeSeries";
    String funding_source "PNRR-ITINERIS";
    String geospatial_lat "79.127117";
    Float64 geospatial_lat_max 79.12797;
    Float64 geospatial_lat_min 79.12711;
    String geospatial_lat_units "degrees_north";
    String geospatial_lon "11.724883";
    Float64 geospatial_lon_max 11.72488;
    Float64 geospatial_lon_min 11.7237;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 294.0;
    Float64 geospatial_vertical_min 180.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"moorings activities in the Krossfjord since 2020
2026-05-29T14:43:10Z (local files)
2026-05-29T14:43:10Z https://data.iadc.cnr.it/erddap/tabledap/vws21g.das
2026-05-29T15:27:06Z https://data.iadc.cnr.it/erddap/tabledap/vws21g
2026-05-29T15:27:06Z https://erddap.s4polarin.eu/erddap-cnr/tabledap/cnr_iadc_f5ff_4134_70dd.das";
    String infoUrl "https://www.isp.cnr.it/index.php/en/";
    String institution "Italian National Research Council - Institute of Polar Sciences";
    String institution_edmo_code "6075";
    String institution_edmo_uri "https://edmo.seadatanet.org/report/6075";
    String Institution_managing_the_facility "CNR - Institute of Polar Science";
    String keywords "180m, cnr, column, control, council, data, depth, earth, Earth Science > Oceans > Ocean Temperature > Water Temperature, flag, identifier, institute, italian, kim, l20, latitude, local, longitude, measurement, mooring, national, nominal, ocean, oceans, polar, quality, research, science, sciences, sea, sea_water_temperature, seawater, sensor, source, station, station_id, TEMP, temp_qc, temperature, time, timeseries, vws21g, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY-4.0";
    String license_uri "https://spdx.org/licenses/CC-BY-4.0";
    Float64 Northernmost_Northing 79.12797;
    String Operating_facility_name "KIM";
    String Organization_owning_the_facility "CNR - Institute of Polar Science";
    String principal_investigator "Stefano Miserocchi";
    String principal_investigator_email "stefano.miserocchi@cnr.it";
    String Resource_Title "SBE56_data";
    String Resource_type "ERRDAP Web service";
    String RI_acronym "SIOS";
    String RI_geographical_coverage "SDN:C19::9";
    String RI_name "Svalbard_Integrated_Observing_System";
    String RI_start_date "September_2010";
    String sourceUrl "https://data.iadc.cnr.it/erddap/tabledap/vws21g";
    Float64 Southernmost_Northing 79.12711;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "time, latitude, longitude, depth, TEMP, TEMP_QC, station_id";
    String summary "Oceanographic mooring data from deployment of KIM mooring in the Krossfjord (Svalbard islands). Mesured properties: seawater temperature";
    String Temporal_extent_end "2023-08-30T08:00:00Z";
    String Temporal_extent_start "2022-09-07T13:40:00Z";
    String time_coverage_end "2025-06-13T12:54:29Z";
    String time_coverage_start "2023-09-11T10:55:07Z";
    String title "KIM Mooring T data @ 180m (vws21g)";
    String Type_of_platform "SDN:L06::43";
    String update_interval "PT10M";
    Float64 Westernmost_Easting 11.7237;
  }
}

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