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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Census of heat tolerance among Florida's threatened staghorn corals] - Census
of heat tolerance among Florida's threatened staghorn corals from a study of
Acropora cervicornis conducted from August to October 2020 (Collaborative
Research: Investigating the genomic basis of key performance traits to quantify
the evolutionary potential of coral populations under climate change)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_920653_v1)
Range: longitude = -82.9052 to -80.08746°E
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 {
  nursery {
    String long_name "Nursery";
    String units "unitless";
  }
  colonyID {
    String long_name "Colonyid";
    String units "unitless";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -82.9052, -80.08746;
    String axis "X";
    String ioos_category "Location";
    String long_name "Source_lon";
    String standard_name "longitude";
    String units "degrees_east";
  }
  source_lat {
    Float32 actual_range 24.4639, 26.19802;
    String long_name "Source_lat";
    String units "degrees_north";
  }
  A_Acer {
    Float32 actual_range 0.00323727, 1.021806;
    String long_name "A_acer";
    String units "Symbiodinium cells per coral cell";
  }
  D_Acer {
    Float32 actual_range 0.02910608, 0.02910608;
    String long_name "D_acer";
    String units "Durusdinium cells per coral cell";
  }
  date_CBASS {
    String long_name "Date_cbass";
    String units "unitless";
  }
  CBASS_ed50 {
    Float32 actual_range 35.05274, 37.61749;
    String long_name "Cbass_ed50";
    String units "degrees Celsius";
  }
 }
  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.920653.1";
    Float64 Easternmost_Easting -80.08746;
    Float64 geospatial_lon_max -80.08746;
    Float64 geospatial_lon_min -82.9052;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-10-06T15:19:31Z (local files)
2024-10-06T15:19:31Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_920653_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/920653";
    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 "The rapid loss of reef-building corals owing to ocean warming is driving the development of interventions such as coral propagation and restoration, selective breeding and assisted gene flow. Many of these interventions target naturally heat-tolerant individuals to boost climate resilience, but the challenges of quickly and reliably quantifying heat tolerance and identifying thermotolerant individuals have hampered implementation. Here, we used coral bleaching automated stress systems to perform rapid, standardized heat tolerance assays on 229 colonies of Acropora cervicornis across six coral nurseries spanning Florida's Coral Reef, USA. Analysis of heat stress dose–response curves for each colony revealed a broad range in thermal tolerance among individuals (approx. 2.5°C range in Fv/Fm ED50), with highly reproducible rankings across independent tests (r = 0.76). Most phenotypic variation occurred within nurseries rather than between them, pointing to a potentially dominant role of fixed genetic effects in setting thermal tolerance and widespread distribution of tolerant individuals throughout the population. The identification of tolerant individuals provides immediately actionable information to optimize nursery and restoration programs for Florida's threatened staghorn corals. This work further provides a blueprint for future efforts to identify and source thermally tolerant corals for conservation interventions worldwide.";
    String title "[Census of heat tolerance among Florida's threatened staghorn corals] - Census of heat tolerance among Florida's threatened staghorn corals from a study of Acropora cervicornis conducted from August to October 2020 (Collaborative Research: Investigating the genomic basis of key performance traits to quantify the evolutionary potential of coral populations under climate change)";
    Float64 Westernmost_Easting -82.9052;
  }
}

 

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