Oleander Project The Oleander Project ERDDAP
Easier access to the project's datasets
   


Brought to you by NSF NOAA BIOS SUNY URI/GSO UHawaii WHOI    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Oleander 150kHz CODAS bundles Subscribe RSS
Institution:  Bermuda Institute of Ocean Sciences   (Dataset ID: oleanderCodas150kHz)
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
   or a List of Values ?
   Maximum ?
 
 url ?              
 name (File Name) ?              
 lastModified (UTC) ?          2020-06-30T09:48:55Z    2020-06-30T09:50:23Z
 size (bytes) ?          1.8587782E7    4.0039019E7
 fileType ?      
   - +  ?
 
Server-side Functions ?
 distinct() ?
? (" ")

File type: (more info)

(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 {
  url {
    String ioos_category "Identifier";
    String long_name "URL";
  }
  name {
    String ioos_category "Identifier";
    String long_name "File Name";
  }
  lastModified {
    String ioos_category "Time";
    String long_name "Last Modified";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  size {
    String ioos_category "Other";
    String long_name "Size";
    String units "bytes";
  }
  fileType {
    String ioos_category "Identifier";
    String long_name "File Type";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String history 
"2024-11-22T00:58:38Z (local files)
2024-11-22T00:58:38Z http://erddap.oleander.bios.edu:8080/erddap/tabledap/oleanderCodas150kHz.html";
    String infoUrl "http://oleander.bios.edu";
    String institution "Bermuda Institute of Ocean Sciences";
    String keywords "adcp, CODAS, currents, eastward_sea_water_velocity, latitude, longitude, northward_sea_water_velocity, profile, time, u, v";
    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 subsetVariables "fileType";
    String summary "Compressed CODAS bundles for ADCP profiles along a transit line between New Jersey and Bermuda — one voyage per bundle";
    String title "Oleander 150kHz CODAS bundles";
  }
}

 

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