Data Access Form

Dataset Title:	[Porites post-settlement experiment] - Results of an experiment on post- settlement survival for Porites corals in Palau (Collaborative Research: How do selection, plasticity, and dispersal interact to determine coral success in warmer and more variable environments?)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_997511_v1)
Information:	Summary \| License \| Metadata \| Background \| Files \| Make a graph

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable	Minimum	Maximum
T (unitless)	"0"	"7"
Days (unitless)	0	14
DM (unitless)	"Delayed"	"Prompt"
Temperature (degrees Celsius (°C))	30	33
Light (unitless)	"Ambient"	"High"
Abbrev (unitless)	"T0D30A"	"T7P33H"
Slide (unitless)	1	91
Survival (unitless)	0.0	1.0

Server-side Functions

distinct()

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 {
  T {
    String long_name "T";
    String units "unitless";
  }
  Days {
    Int32 actual_range 0, 14;
    String long_name "Days";
    String units "unitless";
  }
  DM {
    String long_name "Dm";
    String units "unitless";
  }
  Temperature {
    Int32 actual_range 30, 33;
    String long_name "Temperature";
    String units "degrees Celsius (°C)";
  }
  Light {
    String long_name "Light";
    String units "unitless";
  }
  Abbrev {
    String long_name "Abbrev";
    String units "unitless";
  }
  Slide {
    Int32 actual_range 1, 91;
    String long_name "Slide";
    String units "unitless";
  }
  Survival {
    Float32 actual_range 0.0, 1.0;
    String long_name "Survival";
    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.997511.1";
    String history 
"2026-05-25T00:07:55Z (local files)
2026-05-25T00:07:55Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_997511_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/997511";
    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 early life-history stages of marine invertebrates, including corals, are subject to high mortality. Numerous environmental and biological factors serve as bottlenecks, restricting recruitment and connectivity of populations. We conducted a lab experiment to determine the influence of temperature and light on post-settlement mortality of massive Porites corals in April 2023. Adult massive Porites corals were collected from six sites in Palau immediately prior to their spawning season. Collected corals were held in individual plastic containers (4.2 L; 17 x 13 x 19 cm) in ambient unfiltered flow-through seawater tanks at the Palau International Coral Reef Center (PICRC). Three days post fertilization, larvae were settled on glass microscope slides with crushed crustose coralline algae used as a settlement cue.  Slides were randomly distributed among two temperature treatments (30° C, 33° C) and two light levels (ambient, high) in a 2-way crossed design. Immediately after settlement and every two days throughout the experiment, slides were photographed individually using a Nikon D850 camera with a macro lens. Living settlers were counted in each image to track settler survival over time. Temperature and light level in each treatment were logged using Hobo pendants (Onset, Wareham, USA).";
    String title "[Porites post-settlement experiment] - Results of an experiment on post-settlement survival for Porites corals in Palau (Collaborative Research: How do selection, plasticity, and dispersal interact to determine coral success in warmer and more variable environments?)";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.