OSU Pytheas ERDDAP OSU Pytheas
Accès aux données environnementales...
log in    
Erddap est un produit développé par : NOAA ERD    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  EMSO Western Ligurian : Albatross mooring, AQUADOPP sensor (CSV files 2021-07
to 2023-05)
Subscribe RSS
Institution:  MIO UMR 7294 CNRS / OSU Pytheas   (Dataset ID: Emso_Western_Ligurian_Albatross_Aquadopp_CSV_2021)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 Id ?      
   - +  ?
 time (Date, UTC) ?          2021-07-18T00:00:00Z    2023-05-16T11:30:00Z
  < slider >
 Profondeur ?      
   - +  ?
 latitude (degrees_north) ?      
   - +  ?
  < slider >
 longitude (degrees_east) ?      
   - +  ?
  < slider >
 X_East ?          -0.286    0.284
 Y_North ?          -0.327    0.74
 Z_Up ?          -1.243    1.511
 Amplitude_X ?          28.0    136.0
 Amplitude_Y ?          37.0    139.0
 Amplitude_Z ?          22.0    142.0
 Batterie ?      
   - +  ?
 SoundSpeed ?      
   - +  ?
 Heading ?          0.0    359.9
 Pitch ?          -25.6    11.6
 Roll ?          -5.1    17.9
 Pressure ?          13.868    2396.149
 Temperature ?      
   - +  ?
 Speed ?          0.0    0.749
 Direction ?          0.0    359.5
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.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 {
  Id {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 13;
    String ioos_category "Identifier";
    String long_name "Id";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.6265664e+9, 1.6842366e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Date";
    String source_name "Date";
    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";
  }
  Profondeur {
    Float32 actual_range 500.0, 2400.0;
    String ioos_category "Unknown";
    String long_name "Profondeur";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 42.79, 42.79;
    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.0312, 6.0312;
    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";
  }
  X_East {
    Float32 actual_range -0.286, 0.284;
    String ioos_category "Location";
    String long_name "X East";
  }
  Y_North {
    Float32 actual_range -0.327, 0.74;
    String ioos_category "Location";
    String long_name "Y North";
  }
  Z_Up {
    Float32 actual_range -1.243, 1.511;
    String ioos_category "Location";
    String long_name "Z Up";
  }
  Amplitude_X {
    Float32 actual_range 28.0, 136.0;
    String ioos_category "Location";
    String long_name "Amplitude X";
  }
  Amplitude_Y {
    Float32 actual_range 37.0, 139.0;
    String ioos_category "Location";
    String long_name "Amplitude Y";
  }
  Amplitude_Z {
    Float32 actual_range 22.0, 142.0;
    String ioos_category "Location";
    String long_name "Amplitude Z";
  }
  Batterie {
    Float32 actual_range 11.6, 14.1;
    String ioos_category "Unknown";
    String long_name "Batterie";
  }
  SoundSpeed {
    Float32 actual_range 1503.9, 1516.4;
    String ioos_category "Currents";
    String long_name "Sound Speed";
  }
  Heading {
    Float32 actual_range 0.0, 359.9;
    String ioos_category "Unknown";
    String long_name "Heading";
  }
  Pitch {
    Float32 actual_range -25.6, 11.6;
    String ioos_category "Unknown";
    String long_name "Pitch";
  }
  Roll {
    Float32 actual_range -5.1, 17.9;
    String ioos_category "Unknown";
    String long_name "Roll";
  }
  Pressure {
    Float32 actual_range 13.868, 2396.149;
    String ioos_category "Pressure";
    String long_name "Pressure";
  }
  Temperature {
    Float32 actual_range 13.08, 17.05;
    String ioos_category "Temperature";
    String long_name "Temperature";
  }
  Speed {
    Float32 actual_range 0.0, 0.749;
    String ioos_category "Currents";
    String long_name "Speed";
  }
  Direction {
    Float32 actual_range 0.0, 359.5;
    Float64 colorBarMaximum 360.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Currents";
    String long_name "Direction";
  }
 }
  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.0312;
    String featureType "Point";
    Float64 geospatial_lat_max 42.79;
    Float64 geospatial_lat_min 42.79;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 6.0312;
    Float64 geospatial_lon_min 6.0312;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-05-25T17:07:12Z (local files)
2024-05-25T17:07:12Z http://erddap.osupytheas.fr/erddap/tabledap/Emso_Western_Ligurian_Albatross_Aquadopp_CSV_2021.html";
    String infoUrl "http://www.emso-fr.org/EMSO-France";
    String institution "MIO UMR 7294 CNRS / OSU Pytheas";
    String keywords "2021-07, albatross, amplitude, Amplitude_X, Amplitude_Y, Amplitude_Z, aquadopp, batterie, cnrs, conductivity, csv, ctd, currents, data, date, depth, direction, east, emso, files, heading, identifier, latitude, ligurian, longitude, mio, mooring, north, oregon, osu, pitch, pressure, profondeur, pytheas, roll, sensor, sonde, sound, SoundSpeed, speed, state, temperature, time, umr, university, western, X_East, Y_North, Z_Up";
    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.79;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 42.79;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "Id, Profondeur, latitude, longitude, Batterie, SoundSpeed, Temperature";
    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 "2023-05-16T11:30:00Z";
    String time_coverage_start "2021-07-18T00:00:00Z";
    String title "EMSO Western Ligurian : Albatross mooring, AQUADOPP sensor (CSV files 2021-07 to 2023-05)";
    Float64 Westernmost_Easting 6.0312;
  }
}

 

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.

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