BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [HOTS & BATS Depth Profile Fluorescence] - Fluorescence data from a depth
profile collected at 200 m depth intervals at the Bermuda Atlantic Time Series
Station (BATS) in August 2019 and at the Hawaii Ocean Time Series Staiton Aloha
in July 2021 (The fate of lysis products of picocyanobacteria contributes to
marine humic-like chromophoric dissolved organic matter)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_905149_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 location (unitless) ?          "Aloha"    "BATS"
 latitude (degrees_north) ?          22.75    31.83333
  < slider >
 longitude (degrees_east) ?          -158.0    -64.16666
  < slider >
 depth (m) ?          0    4760
  < slider >
 Fmax1 (Raman units (RU)) ?          0.13    0.99
 Fmax2 (Raman units (RU)) ?          0.23    1.24
 Fmax3 (Raman units (RU)) ?          0.24    0.79
 Fmax4 (Raman units (RU)) ?          0.04    0.39
 
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 {
  location {
    String long_name "Location";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 22.75, 31.83333;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -158.0, -64.16666;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 0, 4760;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Fmax1 {
    Float32 actual_range 0.13, 0.99;
    String long_name "Fmax1";
    String units "Raman units (RU)";
  }
  Fmax2 {
    Float32 actual_range 0.23, 1.24;
    String long_name "Fmax2";
    String units "Raman units (RU)";
  }
  Fmax3 {
    Float32 actual_range 0.24, 0.79;
    String long_name "Fmax3";
    String units "Raman units (RU)";
  }
  Fmax4 {
    Float32 actual_range 0.04, 0.39;
    String long_name "Fmax4";
    String units "Raman units (RU)";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.905149.1";
    Float64 Easternmost_Easting -64.16666;
    Float64 geospatial_lat_max 31.83333;
    Float64 geospatial_lat_min 22.75;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.16666;
    Float64 geospatial_lon_min -158.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 4760.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:59:32Z (local files)
2024-11-08T05:59:32Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_905149_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/905149";
    String institution "BCO-DMO";
    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.";
    Float64 Northernmost_Northing 31.83333;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 22.75;
    String summary "This dataset contains the Parallel Factor Analysis data derived from excitation emission matrix data from solid-phase extracted.";
    String title "[HOTS & BATS Depth Profile Fluorescence] - Fluorescence data from a depth profile collected at 200 m depth intervals at the Bermuda Atlantic Time Series Station (BATS) in August 2019 and at the Hawaii Ocean Time Series Staiton Aloha in July 2021 (The fate of lysis products of picocyanobacteria contributes to marine humic-like chromophoric dissolved organic matter)";
    Float64 Westernmost_Easting -158.0;
  }
}

 

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