ERDDAP
Easier access to scientific data

Data Access Form

Dataset Title:	Technical data: EMSO-Azores WetlabTurb near real time data from the 2016-2017 deployment
Institution:	Ifremer, Institut FranÃ§ais de Recherche pour l'Exploitation de la Mer;Institute of Earth Physics of Paris (IPGP);La Rochelle University, Littoral Environment and Societies (LIENSS) (Dataset ID: WetlabTurb_2016-2017)
Information:	Summary \| License \| Metadata \| Background \| Subset \| 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

PLATFORM

time (UTC)

1956-11-25T05:25:10Z

2017-06-22T06:00:00Z

latitude2 (Latitude, degrees_north)

longitude2 (Longitude, degrees_east)

Instrument_Name (Instrument Name (none))

Sms (Sms (none))

812

Nbm (Nbm (none))

Channels (Channels (none))

7936

wave_length_1 (Wave Length 1 (nm))

902

ntu_signal_1 (Ntu Signal 1 (NTU))

0.0

3867950.25

wave_length_2 (Wave Length 2 (nm))

700

661260

ntu_signal_2 (Ntu Signal 2 (NTU))

62.8

670433.4

NTUThermistor (NTUThermistor (none))

33.0

581.0

Server-side Functions

distinct()

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

File type: (more info)

(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 {
  PLATFORM {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 56, 63;
    String ioos_category "Unknown";
    String long_name "PLATFORM";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -4.1340449e+8, 1.4981112e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "DATE (yyyy-mm-dd Thh:mi:ss Z)";
    String source_name "DATE (yyyy-mm-ddThh:mi:ssZ)";
    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";
  }
  latitude2 {
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "LATITUDE (degree_north)";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude2 {
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "LONGITUDE (degree_east)";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Instrument_Name {
    String ioos_category "Unknown";
    String long_name "Instrument Name (none)";
  }
  Sms {
    Int16 _FillValue 32767;
    Int16 actual_range 8, 812;
    String ioos_category "Unknown";
    String long_name "Sms (none)";
  }
  Nbm {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 39;
    String ioos_category "Unknown";
    String long_name "Nbm (none)";
  }
  Channels {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 7936;
    String ioos_category "Unknown";
    String long_name "Channels (none)";
  }
  wave_length_1 {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 902;
    String ioos_category "Surface Waves";
    String long_name "Wave Length 1 (nm)";
  }
  ntu_signal_1 {
    Float64 _FillValue NaN;
    Float64 actual_range 0.0, 3867950.25;
    String ioos_category "Unknown";
    String long_name "Ntu Signal 1 (NTU)";
  }
  wave_length_2 {
    Int32 _FillValue 2147483647;
    Int32 actual_range 700, 661260;
    String ioos_category "Surface Waves";
    String long_name "Wave Length 2 (nm)";
  }
  ntu_signal_2 {
    Float64 _FillValue NaN;
    Float64 actual_range 62.8, 670433.4;
    String ioos_category "Unknown";
    String long_name "Ntu Signal 2 (NTU)";
  }
  NTUThermistor {
    Float32 _FillValue NaN;
    Float32 actual_range 33.0, 581.0;
    String ioos_category "Unknown";
    String long_name "NTUThermistor (none)";
  }
  QC {
    String ioos_category "Quality";
    String long_name "QC";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String history 
"2024-11-21T09:43:15Z (local files)
2024-11-21T09:43:15Z https://erddap.emso-fr.org/erddap/tabledap/WetlabTurb_2016-2017.html";
    String infoUrl "???";
    String institution "Ifremer, Institut FranÃ§ais de Recherche pour l'Exploitation de la Mer;Institute of Earth Physics of Paris (IPGP);La Rochelle University, Littoral Environment and Societies (LIENSS)";
    String keywords "EMSO, EMSO Azores, Environmental monitoring, Environmental monitoring node, Geophysical data, Hydrothermal Vents, Lucky Strike, Marine imagery, Mid-Atlantic Ridge, MoMARSAT, Multidisciplinary data, TEMPO, Time-series";
    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.";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "latitude2, longitude2, Instrument_Name, QC";
    String summary "This dataset contains real-time data acquired from the EMSO-Azores observatory. Data are managed by the COSTOF2 (COmmunication and STOrage Front-end second generation), developed by Ifremer. It's a smart multisensor marine observation platform designed to suit a wide range of observation systems. The data is located on one of the three Infrastructure constituting Emso Acores site (Transmission buoy BOREL , SeaMoN West or SeaMoN East)";
    String time_coverage_end "2017-06-22T06:00:00Z";
    String time_coverage_start "1956-11-25T05:25:10Z";
    String title "Technical data: EMSO-Azores WetlabTurb near real time data from the 2016-2017 deployment";
  }
}

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