pacx challenge
Liquid Robotics
Pacific Crossing data

ERDDAP > tabledap > Make a Graph

Dataset Title:  MOSE-G directional wave sensor Subscribe RSS
Institution:  Liquid Robotics   (Dataset ID: DatawellMOSE)
Range:  longitude = -156.21619 to 0.0°E, latitude = 0.0 to 37.809647°N, time = 2000-01-13T04:00:00Z to (now?)
Information:  Summary | Metadata | Background | Data Access Form
 
Graph Type: 
X Axis: 
Y Axis: 
Color: 
 
Constraints   Constraint #1 Constraint #2
         
         
         
         
         
 
Server-side Functions
distinct()
orderBy(      " ")
orderByMax(" ")
 
Graph Settings
Marker Type:     Size:
Color: 
Color Bar:    Continuity:    Scale:
      Min:    Max:    N Sections:
Draw the land mask:
Y Axis Minimum:    Maximum:
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: and
or view the URL:
(Documentation / How to bypass this form ) (File Type information)
    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 {
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 0.0, 37.809646666666666;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -156.21619, 0.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.47736e+8, 1.3372578e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  id {
    String cf_role "trajectory_id";
    String long_name "id";
  }
  Hs {
    Float32 actual_range 0.02693529, 17.99401;
    String long_name "Significant vave height";
    String units "meters";
  }
  Tav {
    Float32 actual_range 2.485294, 86.0;
    String long_name "Average period";
    String units "seconds";
  }
  Tp {
    Float32 actual_range 2.031746, 25.6;
    String long_name "Dominant period";
    String units "seconds";
  }
  Dirp {
    Float32 actual_range 0.0365974, 359.9833;
    String long_name "Direction of dominant waves";
    String units "degrees_true";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "Hs,Tav,Tp,Dirp";
    Float64 Easternmost_Easting 0.0;
    Float64 geospatial_lat_max 37.809646666666666;
    Float64 geospatial_lat_min 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 0.0;
    Float64 geospatial_lon_min -156.21619;
    String geospatial_lon_units "degrees_east";
    String history 
"2012-05-17 file:///home/glassfish/robotCSV/DatawellMOSE
2012-05-17 http://data.liquidr.com/tabledap/DatawellMOSE.das";
    String infoUrl "http://liquidr.com/pacx";
    String institution "Liquid Robotics";
    Float64 Northernmost_Northing 37.809646666666666;
    String sourceUrl "file:///home/glassfish/robotCSV/DatawellMOSE";
    Float64 Southernmost_Northing 0.0;
    String summary "MOSE-G directional wave sensor";
    String time_coverage_end "2012-05-17T12:30:00Z";
    String time_coverage_start "2000-01-13T04:00:00Z";
    String title "MOSE-G directional wave sensor";
    Float64 Westernmost_Easting -156.21619;
  }
}

 

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 is a superset of the OPeNDAP DAP constraint protocol.

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
   http://data.liquidr.com/erddap/tabledap/datasetID.fileType{?query}
For example,
   http://data.liquidr.com/erddap/tabledap/erdGlobecBottle.htmlTable?longitude,latitude,time,bottle_posn,temperature1&time>=2002-08-17T00:00:00Z&time<=2002-08-19T20:18: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 separated by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.
 


ERDDAP, Version 1.36
Disclaimers | Privacy Policy | Contact