NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  Datacenter Attributes Subscribe RSS
Institution:  OTN   (Dataset ID: nodename_aat_datacenter_attributes)
Information:  Summary ? | License ? | Metadata | Background (external link) | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 datacenter_reference ?              
 datacenter_name ?              
 datacenter_abstract ?              
 datacenter_citation ?              
 datacenter_pi ?              
 datacenter_pi_organization ?              
 datacenter_pi_contact ?              
 datacenter_infourl ?              
 datacenter_keywords ?              
 datacenter_keywords_vocabulary ?              
 datacenter_doi ?              
 datacenter_license ?              
 datacenter_distribution_statement ?              
 datacenter_date_modified ?              
 datacenter_geospatial_lon_min ?              
 datacenter_geospatial_lon_max ?              
 datacenter_geospatial_lat_min ?              
 datacenter_geospatial_lat_max ?              
 datacenter_time_coverage_start ?              
 datacenter_time_coverage_end ?              
 
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.Hover here to see a list of options. Click on an option to select it.")

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 {
  datacenter_reference {
    String ioos_category "Identifier";
    String long_name "Datacenter Reference";
  }
  datacenter_name {
    String ioos_category "Identifier";
    String long_name "Datacenter Name";
  }
  datacenter_abstract {
    String ioos_category "Unknown";
    String long_name "Datacenter Abstract";
  }
  datacenter_citation {
    String ioos_category "Unknown";
    String long_name "Datacenter Citation";
  }
  datacenter_pi {
    String ioos_category "Unknown";
    String long_name "Datacenter PI";
  }
  datacenter_pi_organization {
    String ioos_category "Unknown";
    String long_name "Datacenter PI Organization";
  }
  datacenter_pi_contact {
    String ioos_category "Unknown";
    String long_name "Datacenter PI Contact";
  }
  datacenter_infourl {
    String ioos_category "Unknown";
    String long_name "Datacenter Info URL";
  }
  datacenter_keywords {
    String ioos_category "Unknown";
    String long_name "Datacenter Keywords";
  }
  datacenter_keywords_vocabulary {
    String ioos_category "Unknown";
    String long_name "Datacenter Keywords Vocabulary";
  }
  datacenter_doi {
    String ioos_category "Unknown";
    String long_name "Datacenter Digital Object Identifier";
  }
  datacenter_license {
    String ioos_category "Unknown";
    String long_name "Datacenter License";
  }
  datacenter_distribution_statement {
    String ioos_category "Unknown";
    String long_name "Datacenter Distribution Statement";
  }
  datacenter_date_modified {
    String ioos_category "Unknown";
    String long_name "Datacenter Date Modified";
  }
  datacenter_geospatial_lon_min {
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Longitude Minimum";
  }
  datacenter_geospatial_lon_max {
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Longitude Maximum";
  }
  datacenter_geospatial_lat_min {
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Latitude Minimum";
  }
  datacenter_geospatial_lat_max {
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Latitude Maximum";
  }
  datacenter_time_coverage_start {
    String ioos_category "Unknown";
    String long_name "Datacenter Time Coverage Start";
  }
  datacenter_time_coverage_end {
    String ioos_category "Unknown";
    String long_name "Datacenter Time Coverage End";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "???";
    String history 
"2024-12-23T10:20:18Z (source database)
2024-12-23T10:20:18Z http://erddap.factnetwork.secoora.org:80/erddap/tabledap/nodename_aat_datacenter_attributes.html";
    String infoUrl "http://www.oceantrackingnetwork.org/";
    String institution "OTN";
    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 "(source database)";
    String summary "Datacenter Attributes.";
    String title "Datacenter Attributes";
  }
}

 

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