ERDDAP > tabledap > Data Access Form

Dataset Title:	Datacenter Attributes
Institution:	Ocean Tracking Network   (Dataset ID: otn_aat_datacenter_attributes)
Information:	Summary | License | Metadata | Background | 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()

orderBy orderByDescending orderByClosest orderByCount orderByLimit orderByMax orderByMin orderByMinMax orderByMean orderBySum (" 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 time_coverage_start time_coverage_end 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 time_coverage_start time_coverage_end 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 time_coverage_start time_coverage_end 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 time_coverage_start time_coverage_end 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 time_coverage_start time_coverage_end ")

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .dataTable - A JSON file formatted for use with the Google Visualization client library (Google Charts). .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriCsv - Download a ISO_8859_1 .csv file for ESRI's ArcGIS 9.x and below (separate date and time columns). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .geoJson - Download longitude,latitude,otherColumns data as a UTF-8 GeoJSON .json file. .graph - View a Make A Graph web page. .help - View a web page with a description of tabledap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each response column becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a flat, table-like, NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncCF - Download a NetCDF-3 CF Discrete Sampling Geometries file (Contiguous Ragged Array). .ncCFHeader - View the UTF-8 header (the metadata) for the .ncCF file. .ncCFMA - Download a NetCDF-3 CF Discrete Sampling Geometries file (Multidimensional Array). .ncCFMAHeader - View the UTF-8 header (the metadata) for the .ncCFMA file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download longitude,latitude,time,otherColumns as an ISO-8859-1 ODV Generic Spreadsheet File (.txt). .subset - View an HTML form which uses faceted search to simplify picking subsets of the data. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .kml - View a .kml file, suitable for Google Earth. .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form )
 
Submit (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-04-30T04:44:53Z (source database)
2024-04-30T04:44:53Z 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 Data Access Protocol (DAP) and its selection constraints.

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.

• (easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
• (easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
• (not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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