Ifremer ERDDAP
Easier access to scientific data

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Technical data: EMSO-Azores GeoSurface near real time data from the 2014-2015
deployment
Subscribe RSS
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: GeoSurface_2014-2015)
Range: longitude = -72.282585 to 18.074247°E, latitude = -61.81595 to 37.31619°N, altitude = 0.0 to 9.0179251E8m, time = 1944-08-25T17:34:47Z to 2030-09-09T06:10:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
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.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.")
 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  PLATFORM {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 16, 32;
    String ioos_category "Unknown";
    String long_name "PLATFORM";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range -8.00000713e+8, 1.9151646e+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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -61.815948, 37.31619;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "LATITUDE (degree_north)";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -72.282586, 18.074248;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    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 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 29, 29;
    String ioos_category "Unknown";
    String long_name "Sms (none)";
  }
  Nbm {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 1, 5;
    String ioos_category "Unknown";
    String long_name "Nbm (none)";
  }
  GPSTime {
    String ioos_category "Unknown";
    String long_name "GPSTime (UTC)";
  }
  GPSValidity {
    String ioos_category "Unknown";
    String long_name "GPSValidity (none)";
  }
  SatellitesNb {
    Int16 _FillValue 32767;
    Int16 actual_range 4, 196;
    String ioos_category "Unknown";
    String long_name "Satellites Nb (none)";
  }
  HDOP {
    Float32 actual_range 0.0, 19.1;
    String ioos_category "Unknown";
    String long_name "HDOP (none)";
  }
  altitude {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "up";
    Float64 actual_range 0.0, 9.01792512e+8;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Altitude";
    String positive "up";
    String source_name "Altitude (m)";
    String standard_name "altitude";
    String units "m";
  }
  GeoidHeight {
    String ioos_category "Unknown";
    String long_name "Geoid Height (m)";
  }
  QC {
    String ioos_category "Quality";
    String long_name "QC";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 18.074248;
    String featureType "Point";
    Float64 geospatial_lat_max 37.31619;
    Float64 geospatial_lat_min -61.815948;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 18.074248;
    Float64 geospatial_lon_min -72.282586;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 9.01792512e+8;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "up";
    String geospatial_vertical_units "m";
    String history 
"2024-04-27T10:33:42Z (local files)
2024-04-27T10:33:42Z https://erddap.emso-fr.org/tabledap/GeoSurface_2014-2015.das";
    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 keywords_vocabulary "GCMD Science Keywords";
    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 37.31619;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -61.815948;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "Instrument_Name, Sms, GPSValidity, 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 "2030-09-09T06:10:00Z";
    String time_coverage_start "1944-08-25T17:34:47Z";
    String title "Technical data: EMSO-Azores GeoSurface near real time data from the 2014-2015 deployment";
    Float64 Westernmost_Easting -72.282586;
  }
}

 

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