VOTO Voice of the Ocean ERDDAP
Easier access to scientific data 		| ?    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  requests Subscribe RSS
Institution:  Voice of the Ocean foundation   (Dataset ID: requests)
Range: time = 2022-09-16T06:52:08.000Z to 2024-10-22T04:50:27.000Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
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 {
  ip_id {
    String ioos_category "Identifier";
    String long_name "Ip Id";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.663311128e+9, 1.729572627e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime";
    String source_name "datetime";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String time_precision "1970-01-01T00:00:00.000Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  url {
    String ioos_category "Unknown";
    String long_name "Url";
  }
  status_code {
    Int16 _FillValue 32767;
    Int16 actual_range 200, 503;
    String ioos_category "Unknown";
    String long_name "Status-code";
  }
  bytes_sent {
    Float64 _FillValue 9223372036854775807;
    Float64 actual_range 0, 3827082278;
    String ioos_category "Unknown";
    String long_name "bytes_sent";
  }
  erddap_request_type {
    String ioos_category "Unknown";
    String long_name "Erddap Request Type";
  }
  dataset_id {
    String ioos_category "Identifier";
    String long_name "Dataset Id";
  }
  file_type {
    String ioos_category "Unknown";
    String long_name "File Type";
  }
  dataset_type {
    String ioos_category "Unknown";
    String long_name "Dataset Type";
  }
  BrowserFamily {
    String ioos_category "Taxonomy";
    String long_name "Browser Family";
  }
  DeviceFamily {
    String ioos_category "Taxonomy";
    String long_name "Device Family";
  }
  OS {
    String ioos_category "Unknown";
    String long_name "OS";
  }
  base_url {
    String ioos_category "Unknown";
    String long_name "OS";
  }
  request_kwargs {
    String ioos_category "Unknown";
    String long_name "OS";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String history 
"2024-10-22T18:47:33Z (local files)
2024-10-22T18:47:33Z https://erddap.observations.voiceoftheocean.org/tabledap/requests.das";
    String infoUrl "https://github.com/callumrollo/erddaplogs";
    String institution "Voice of the Ocean foundation";
    String keywords "browser, BrowserFamily, bytes, bytes_sent, code, data, dataset, dataset_id, dataset_type, datetime, device, DeviceFamily, erddap, erddap_request_type, family, file, file_type, identifier, local, request, sent, source, status, status-code, status_code, taxonomy, time, type";
    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 summary "Usage data for this ERDDAP server- anonymised requests";
    String testOutOfDate "now-1day";
    String time_coverage_end "2024-10-22T04:50:27.000Z";
    String time_coverage_start "2022-09-16T06:52:08.000Z";
    String title "requests";
  }
}

 

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