UCONN ERDDAP
Easier access to realtime and historic LISICOS buoy observations.
   
Brought to you by NOAA IOOS NERACOOS UCONN LISICOS    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  DEEP Nutrient Data Subscribe RSS
Institution:  University of Connecticut   (Dataset ID: DEEP_Nutrient)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 cruise ?              
 Lab_ID ?              
 Station_Name ?              
 Depth_Code ?              
 Detection_Limit ?              
 Dilution_Factor ?              
 PQL ?              
 Parameter ?              
 Result ?              
 non_detect (Non-Detect) ?              
 Units ?              
 Comment ?              
 Month ?              
 latitude (degrees_north) ?              
 longitude (degrees_east) ?              
 Time_ON_Station ?              
 Time_OFF_Station ?              
 time (UTC) ?              
 Start_Date (UTC) ?              
 End_Date (UTC) ?              
 B_Sample_Depth ?              
 M_Sample_Depth ?              
 S_Sample_Depth ?              
 NB_Sample_Depth ?              
 
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 {
  cruise {
    String ioos_category "Identifier";
    String long_name "Cruise";
  }
  Lab_ID {
    String ioos_category "Identifier";
    String long_name "Lab ID";
  }
  Station_Name {
    String ioos_category "Identifier";
    String long_name "Station Name";
  }
  Depth_Code {
    String ioos_category "Identifier";
    String long_name "Depth Code";
  }
  Detection_Limit {
    String ioos_category "Unknown";
    String long_name "Detection Limit";
  }
  Dilution_Factor {
    String ioos_category "Unknown";
    String long_name "Dilution Factor";
  }
  PQL {
    String ioos_category "Unknown";
    String long_name "PQL";
  }
  Parameter {
    String ioos_category "Identifier";
    String long_name "Parameter";
  }
  Result {
    String ioos_category "Unknown";
    String long_name "Result";
  }
  non_detect {
    String ioos_category "Unknown";
    String long_name "Non-Detect";
  }
  Units {
    String ioos_category "Unknown";
    String long_name "Units";
  }
  Comment {
    String ioos_category "Unknown";
    String long_name "Comment";
  }
  Month {
    String ioos_category "Unknown";
    String long_name "Month";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Time_ON_Station {
    String ioos_category "Unknown";
    String long_name "Time ON Station";
  }
  Time_OFF_Station {
    String ioos_category "Unknown";
    String long_name "Time OFF Station";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Start_Date {
    String ioos_category "Time";
    String long_name "Start Date";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  End_Date {
    String ioos_category "Time";
    String long_name "End Date";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  B_Sample_Depth {
    String ioos_category "Unknown";
    String long_name "B Sample Depth";
  }
  M_Sample_Depth {
    String ioos_category "Unknown";
    String long_name "M Sample Depth";
  }
  S_Sample_Depth {
    String ioos_category "Unknown";
    String long_name "S Sample Depth";
  }
  NB_Sample_Depth {
    String ioos_category "Unknown";
    String long_name "NB Sample Depth";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String contributor_name "Department of Energy and Environmental Protection (DEEP)";
    String contributor_role "sponsor";
    String contributor_url "https://www.ct.gov/deep/site/default.asp";
    String Conventions "COARDS, CF-1.6, Unidata Dataset Discovery v1.0";
    String creator_address "1080 Shennecossett Road, Groton, CT 06340 USA";
    String creator_city "Groton";
    String creator_country "United States";
    String creator_email "james.odonnell@uconn.edu,todd.fake@uconn.edu";
    String creator_institution "University of Connecticut";
    String creator_sector "academic";
    String creator_url "http://lisicos.uconn.edu";
    String featureType "Point";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String history 
"2024-03-29T12:11:04Z (source database)
2024-03-29T12:11:04Z http://merlin.dms.uconn.edu:8080/erddap/tabledap/DEEP_Nutrient.html";
    String id "DEEP";
    String info_url "http://lisicos.uconn.edu/dep_portal.php";
    String infoUrl "http://lisicos.uconn.edu/NutrientID.pdf";
    String institution "University of Connecticut";
    String keywords "Buoy > Oceans > Ocean Data > Long Island Sound";
    String keywords_vocabulary "GCMD Science Keywords";
    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 naming_authority "edu.connecticut";
    String neracoos_data_provider "UCONN";
    String project "DEEP";
    String publisher_country "United States";
    String publisher_email "todd.fake@uconn.edu";
    String publisher_institution "University of Connecticut";
    String publisher_name "Department of Marine Sciences, University of Connecticut";
    String publisher_url "http://lisicos.uconn.edu";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF-1.6";
    String station "DEEP CTD Data";
    String station_site_desc "DEEP Nutrient Data";
    String summary "Long Island Sound observation data from the Department of Energy and Environmental Protection (NERACOOS). These data are served by Unidata's Thematic Realtime Environmental Distributed Data Services (THREDDS) Data Server (TDS) in a variety of interoperable data services and output formats.";
    String testOutOfDate "now-1day";
    String title "DEEP Nutrient Data";
  }
}

 

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