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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Coral clipping experiment - growth] - Branch extension measurements from a
clipping experiment conducted on the coral Antillogorgia elisabethae at two
sites in the Bahamas determined from June 1999 to June 2000 (Collaborative
Research: Pattern and process in the abundance and recruitment of Caribbean
octocorals)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_872600_v2)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Location (unitless) ?          "Abaco"    "San Salvador"
 Latitude (degrees_north) ?          24.05833    25.9926
 longitude (degrees_east) ?          -77.42675    -74.54166
  < slider >
 Colony (unitless) ?          92.0    990.0
 Treatment (unitless) ?          "Clipped (10)"    "Not Clipped"
 SiteTreat (unitless) ?          "Abaco0"    "SanSal4"
 Branch_Number (unitless) ?          1    152
 Growth_cm (centimeters (cm)) ?          0.0    28.07
 Jun_99 (centimeters (cm)) ?          0.0    247.72
 Jul_00 (centimeters (cm)) ?          1.02    248.94
 BranchType (unitless) ?          "New"    "Old"
 
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 {
    Float32 actual_range 24.05833, 25.9926;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -77.42675, -74.54166;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Colony {
    Float32 actual_range 92.0, 990.0;
    String long_name "Colony";
    String units "unitless";
  }
  Treatment {
    String long_name "Treatment";
    String units "unitless";
  }
  SiteTreat {
    String long_name "Sitetreat";
    String units "unitless";
  }
  Branch_Number {
    Int32 actual_range 1, 152;
    String long_name "Branch_number";
    String units "unitless";
  }
  Growth_cm {
    Float32 actual_range 0.0, 28.07;
    String long_name "Growth_cm";
    String units "centimeters (cm)";
  }
  Jun_99 {
    Float32 actual_range 0.0, 247.72;
    String long_name "Jun_99";
    String units "centimeters (cm)";
  }
  Jul_00 {
    Float32 actual_range 1.02, 248.94;
    String long_name "Jul_00";
    String units "centimeters (cm)";
  }
  BranchType {
    String long_name "Branchtype";
    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.872600.2";
    Float64 Easternmost_Easting -74.54166;
    Float64 geospatial_lon_max -74.54166;
    Float64 geospatial_lon_min -77.42675;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-05T14:41:46Z (local files)
2024-11-05T14:41:46Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_872600_v2.html";
    String infoUrl "https://www.bco-dmo.org/dataset/872600";
    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.";
    String sourceUrl "(local files)";
    String summary "This dataset results from an experiment in which colonies of the coral Antillogorgia elisabethae were clipped to simulate harvesting/disturbance at 2 sites in the Bahamas, one at Great Abaco and another at San Salvador Island. This dataset includes branch extension measurements for colonies that were clipped to 10 or 4 branches or not clipped. Version 2 of this dataset, created on 2023-11-07, includes a correction to the latitude of the Abaco site.";
    String title "[Coral clipping experiment - growth] - Branch extension measurements from a clipping experiment conducted on the coral Antillogorgia elisabethae at two sites in the Bahamas determined from June 1999 to June 2000 (Collaborative Research: Pattern and process in the abundance and recruitment of Caribbean octocorals)";
    Float64 Westernmost_Easting -77.42675;
  }
}

 

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