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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [End members metadata] - Metadata (location, depth, water temperature,
salinity, etc.) describing end members compared to blue particles found in
Oceanic Flux Program (OFP) traps (OCE-PRF: Towards Quantifying Calcium
Carbonate Sediment Dissolution During Marine Diagenesis)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_960257_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Sample_type (unitless) ?          "Bryozoan on Sargas..."    "Serpulid worm on S..."
 Feeding_state_diet (unitless) ?          "Fasted (natural di..."    "Recently eaten (na..."
 Species (unitless) ?          "Albula vulpes"    "Sphyraena barracuda"
 Location (unitless) ?          "Eleuthera, The Bah..."    "Sargasso Sea (Berm..."
 latitude (degrees_north) ?          -14.6786    31.6833
  < slider >
 longitude (degrees_east) ?          -76.3584    145.4464
  < slider >
 Water_temperature (degrees Celsius) ?          "18 (culture temper..."    "31"
 Salinity (parts per thousand (ppt)) ?          "35"    "37"
 Collection_date (unitless) ?          "2009-12-01"    "2023-08-03"
 
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 {
  Sample_type {
    String long_name "Sample_type";
    String units "unitless";
  }
  Feeding_state_diet {
    String long_name "Feeding_state_diet";
    String units "unitless";
  }
  Species {
    String long_name "Species";
    String units "unitless";
  }
  Location {
    String long_name "Location";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -14.6786, 31.6833;
    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 -76.3584, 145.4464;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Water_temperature {
    String long_name "Water_temperature";
    String units "degrees  Celsius";
  }
  Salinity {
    String long_name "Salinity";
    String units "parts per thousand (ppt)";
  }
  Collection_date {
    String long_name "Collection_date";
    String units "unitless";
  }
 }
  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.960257.1";
    Float64 Easternmost_Easting 145.4464;
    Float64 geospatial_lat_max 31.6833;
    Float64 geospatial_lat_min -14.6786;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 145.4464;
    Float64 geospatial_lon_min -76.3584;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-16T00:46:17Z (local files)
2025-05-16T00:46:17Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_960257_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/960257";
    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.6833;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -14.6786;
    String summary "This dataset includes metadata for end members (fish, bryzoan, serpulid worm, red algae, and coccolithophore) that were compared to blue particles found in OFP traps. Data include species, location, depth, water temperature, salinity, and date of collection.";
    String title "[End members metadata] - Metadata (location, depth, water temperature, salinity, etc.) describing end members compared to blue particles found in Oceanic Flux Program (OFP) traps (OCE-PRF:  Towards Quantifying Calcium Carbonate Sediment Dissolution During Marine Diagenesis)";
    Float64 Westernmost_Easting -76.3584;
  }
}

 

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