Ifremer ERDDAP
Easier access to scientific data

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Technical data: EMSO-Azores IpgpJPP 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: IpgpJPP_2014-2015)
Range: time = 2014-07-20T18:15:10Z to 2014-07-20T19:10:09Z
Information:  Summary ? | License ? | 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: 
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 ? )
   
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 66, 66;
    String ioos_category "Unknown";
    String long_name "PLATFORM";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.40588011e+9, 1.405883409e+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 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 24, 24;
    String ioos_category "Unknown";
    String long_name "Sms (none)";
  }
  Nbm {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 11, 11;
    String ioos_category "Unknown";
    String long_name "Nbm (none)";
  }
  Channels {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 15, 15;
    String ioos_category "Unknown";
    String long_name "Channels (none)";
  }
  PressurePeriod1 {
    Float64 actual_range 30.077581, 30.077717;
    String ioos_category "Pressure";
    String long_name "Pressure Period1 (sec)";
  }
  TempPeriod1 {
    Float32 actual_range 5.761071, 5.761091;
    String ioos_category "Unknown";
    String long_name "Temp Period1 (sec)";
  }
  PressurePeriod2 {
    Float64 actual_range 30.318827, 30.318851;
    String ioos_category "Pressure";
    String long_name "Pressure Period2 (sec)";
  }
  TempPeriod2 {
    Float32 actual_range 5.84378, 5.843795;
    String ioos_category "Unknown";
    String long_name "Temp Period2 (sec)";
  }
  ExtTemp {
    Float32 actual_range 24.01, 24.0884;
    String ioos_category "Unknown";
    String long_name "Ext Temp (Celsius Degree)";
  }
  IntTemp {
    Float32 actual_range 26.558, 27.2062;
    String ioos_category "Unknown";
    String long_name "Int Temp (Celsius Degree)";
  }
  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-10-03T20:42:21Z (local files)
2024-10-03T20:42:21Z https://erddap.emso-fr.org/tabledap/IpgpJPP_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 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 "PLATFORM, latitude2, longitude2, Instrument_Name, Sms, Nbm, Channels, 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 "2014-07-20T19:10:09Z";
    String time_coverage_start "2014-07-20T18:15:10Z";
    String title "Technical data: EMSO-Azores IpgpJPP near real time data from the 2014-2015 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.

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