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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Edmunds et al. 2023 Oecologia: Settler Density] - Density of coral settlers
detected on settlement tiles each year at two 10m sites on the north shore of
Moorea, French Polynesia from 2008 to 2020 (Moorea Coral Reef Long-Term
Ecological Research site)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_918324_v1)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
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.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    [The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Year {
    String long_name "Year";
    String units "unitless";
  }
  Site {
    String long_name "Site";
    String units "unitless";
  }
  All_corals {
    Float32 actual_range 1.52, 10.479;
    String long_name "All_corals";
    String units "number of settlers per tile";
  }
  Pocillopora {
    Float32 actual_range 0.333, 9.69;
    String long_name "Pocillopora";
    String units "number of settlers per tile";
  }
 }
  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.918324.1";
    String history 
"2024-09-24T09:10:33Z (local files)
2024-09-24T09:10:33Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_918324_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/918324";
    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 
"Data Abstract:

These data describe the number of coral settlers detected on settlement tiles each year, with annual settlement determined by adding mean recruits on tiles retrieved in Jan/Feb to mean density on tiles retrieved Aug/Sept.


Results paper abstract, Edmunds et al. (2023) :
* [See \"Related Datasets\" section for access to related datasets discussed here]

Understanding population dynamics is a long-standing objective of ecology, but the need for progress in this area has become urgent. For coral reefs, achieving this objective is impeded by a lack of information on settlement versus post-settlement events in determining recruitment and population size. Declines in coral abundance are often inferred to be associated with reduced densities of recruits, which could arise from mechanisms occurring at larval settlement, or throughout post-settlement stages. This study uses annual measurements from 2008 to 2021 of coral cover, the density of coral settlers (S), the density of small corals (SC), and environmental conditions, to evaluate the roles of settlement versus post-settlement events in determining rates of coral recruitment and changes in coral cover at Moorea, French Polynesia. Coral cover, S, SC, and the SC:S ratio (a proxy for post-settlement success), and environmental conditions, were used in generalized additive models (GAMs) to show that: (a) coral cover was more strongly related to SC and SC:S than S, and (b) SC:S was highest when preceded by cool seawater, low concentrations of Chlorophyll a, and low flow speeds, and S showed evidence of declining with elevated temperature. Together, these results suggest that changes in coral cover in Moorea are more strongly influenced by post-settlement events than settlement. The key to understanding coral community resilience may lie in elucidating the factors attenuating the bottleneck between settlers and small corals.";
    String title "[Edmunds et al. 2023 Oecologia: Settler Density] - Density of coral settlers detected on settlement tiles each year at two 10m sites on the north shore of Moorea, French Polynesia from 2008 to 2020 (Moorea Coral Reef Long-Term Ecological Research site)";
  }
}

 

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