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:  Ocean Tracking Network   (Dataset ID: otn_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 ?          -175.90598    19.37508
 datacenter_geospatial_lon_max ?          -55.6    148.82999999999998
 datacenter_geospatial_lat_min ?          -49.36753    38.01934
 datacenter_geospatial_lat_max ?          -30.24398    74.75011
 time_coverage_start (UTC) ?          1970-01-01T00:00:00Z    1970-01-01T00:00:00Z
 time_coverage_end (UTC) ?          1970-01-01T00:00:00Z    1970-01-01T00:00:00Z
 
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 information)

(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 {
    Float64 actual_range -175.90598, 19.37508;
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Longitude Minimum";
  }
  datacenter_geospatial_lon_max {
    Float64 actual_range -55.6, 148.82999999999998;
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Longitude Maximum";
  }
  datacenter_geospatial_lat_min {
    Float64 actual_range -49.36753, 38.01934;
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Latitude Minimum";
  }
  datacenter_geospatial_lat_max {
    Float64 actual_range -30.24398, 74.75011;
    String ioos_category "Location";
    String long_name "Datacenter Geospatial Latitude Maximum";
  }
  time_coverage_start {
    Float64 actual_range 0.0, 0.0;
    String ioos_category "Time";
    String long_name "Datacenter Time Coverage Start";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time_coverage_end {
    Float64 actual_range 0.0, 0.0;
    String ioos_category "Time";
    String long_name "Datacenter Time Coverage End";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "AAT, COARDS, CF-1.6, ACDD-1.3";
    String history 
"2024-11-14T07:24:35Z (source database)
2024-11-14T07:24:35Z https://members.oceantrack.org/erddap/tabledap/otn_aat_datacenter_attributes.html";
    String infoUrl "http://oceantrackingnetwork.org/";
    String institution "Ocean Tracking Network";
    String keywords "ACOUSTIC RECEIVERS, ACOUSTIC TAGS, Earth Science > Biological Classification > Animals/Vertebrates > Fish";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "By accessing or using OTN Data you agree to: a) give proper attribution to all Data Providers and to OTN by using the preformed citations contained in OTN metadata reports and in the data records, b) inform OTN of publications, products or commercial applications using the data, c) acknowledge that neither the OTN nor the provider is liable for inaccuracies in the data, d) assume responsibility for investigating and understanding the limitations of the data, e) report all problems with respect to data to otndc@dal.ca. For full policy, see: https://members.oceantrack.org/data/policies.";
    String publisher_email "otndc@dal.ca";
    String publisher_name "OTN Data Centre";
    String publisher_url "http://members.oceantrack.org";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF-11";
    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.23
Disclaimers | Privacy Policy | Contact