Data Access Form

Dataset Title:	EMSO Western Ligurian : MII, OXYGEN sensor (CSV files from 2017-09)
Institution:	MIO UMR 7294 CNRS / OSU Pytheas (Dataset ID: Emso_Western_Ligurian_MII_Oxygen_CSV_2017)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| Files \| Make a graph

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.

Variable

Optional
Constraint #1

Optional
Constraint #2

Minimum

or a List of Values

Maximum

time (Date Time, UTC)

2017-09-29T12:44:11Z

2019-07-29T21:50:32Z

latitude (degrees_north)

longitude (degrees_east)

Optode_Type (Optode-Type)

Optode_Serial

Oxygen

185.353

201.942

Saturation_Oxygen

56.696

61.753

Temperature

13.285

13.314

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

File type: (more information)

(Documentation / Bypass this form )

(Please be patient. It may take a while to get the data.)

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.506689051e+9, 1.564437032e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date Time";
    String source_name "DateTime";
    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";
    Float32 actual_range 42.805, 42.805;
    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";
    Float32 actual_range 6.029, 6.029;
    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";
  }
  Optode_Type {
    Int16 _FillValue 32767;
    Int16 actual_range 4330, 4330;
    String ioos_category "Unknown";
    String long_name "Optode-Type";
  }
  Optode_Serial {
    Int16 _FillValue 32767;
    Int16 actual_range 1995, 1995;
    String ioos_category "Unknown";
    String long_name "Optode Serial";
  }
  Oxygen {
    Float32 actual_range 185.353, 201.942;
    String ioos_category "Dissolved O2";
    String long_name "Oxygen";
  }
  Saturation_Oxygen {
    Float32 actual_range 56.696, 61.753;
    String ioos_category "Dissolved O2";
    String long_name "Saturation Oxygen";
  }
  Temperature {
    Float32 actual_range 13.285, 13.314;
    String ioos_category "Temperature";
    String long_name "Temperature";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_name "MIO UMR 7294 CNRS / OSU Pytheas";
    String creator_type "institution";
    String creator_url "http://www.emso-fr.org/EMSO-France";
    Float64 Easternmost_Easting 6.029;
    String featureType "Point";
    Float64 geospatial_lat_max 42.805;
    Float64 geospatial_lat_min 42.805;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 6.029;
    Float64 geospatial_lon_min 6.029;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-12-21T16:06:46Z (local files)
2024-12-21T16:06:46Z http://erddap.osupytheas.fr/erddap/tabledap/Emso_Western_Ligurian_MII_Oxygen_CSV_2017.html";
    String infoUrl "http://www.emso-fr.org/EMSO-France";
    String institution "MIO UMR 7294 CNRS / OSU Pytheas";
    String keywords "cnrs, conductivity, csv, ctd, data, date, depth, dissolved, dissolved o2, emso, files, latitude, ligurian, longitude, mii, mio, O2, optode, optode-type, Optode_Serial, Optode_Type, oregon, osu, oxygen, pytheas, saturation, Saturation_Oxygen, sensor, serial, sonde, state, temperature, time, type, umr, university, western";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    Float64 Northernmost_Northing 42.805;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 42.805;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "latitude, longitude, Optode_Type, Optode_Serial";
    String summary "The European Multidisciplinary Seafloor and water column Observatory (EMSO) is a research infrastructure distributed throughout Europe for seabed and water column observatories. It aims to further explore the oceans, better understand the phenomena that occur on the seabed, and elucidate the critical role that these phenomena play in global Earth systems. This observatory is based on observation sites (or nodes) that have been deployed in strategic locations in European seas, from the Arctic to the Atlantic, from the Mediterranean to the Black Sea. There are currently eleven deep water nodes plus four shallow water test nodes. EMSO Western Ligurian is one of these permanent underwater observatories located in the Ligurian Sea and is deployed off Toulon, France. This region was chosen for its particular scientific interests such as: seismicity, topography, turbidity, biodiversity, water mass dynamics and organic matter flow. This underwater observation network is also part of KM3NeT (https://www.km3net.org/) which has a modular topology designed to connect up to 120 neutrino detection units. Earth and Sea Science (ESS) instrumentation connected to KM3NeT is based on two complementary components: an instrumented interface module (MII) and an autonomous instrumented line (ALBATROSS). The ALBATROSS line is an inductive line (2000 m) composed of an acoustic communication system, two inductive cables equipped with Conductivity, Temperature, Depth (CTD)-O2 sensors, current meters and two instrumented buoys. This line is deployed at a distance of 2-3 kilometers from the MII, and communication on land is done by an acoustic link with the MII, and electro-optical cable via the KM3NeT node.";
    String time_coverage_end "2019-07-29T21:50:32Z";
    String time_coverage_start "2017-09-29T12:44:11Z";
    String title "EMSO Western Ligurian : MII, OXYGEN sensor (CSV files from 2017-09)";
    Float64 Westernmost_Easting 6.029;
  }
}

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.