BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Longitudinal study NCBI SRA] - NCBI Sequence Read Archive (SRA) accession numbers for fastq sequence files of 16S amplicons from a longitudinal study of SCTLD at St. John, U.S. Virgin Islands from 2020 to 2024 (A multi-scale approach to predicting infectious multi-host disease spread in marine benthic communities)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_986592_v1)
Range:	longitude = -64.7642 to -64.70402°E, latitude = 18.31462 to 18.33797°N
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

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.

Graph Type:

X Axis:

Y Axis:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

Draw land mask:

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

)

Click on the map to specify a new center point.

Zoom:

[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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Experiment_Accession {
    String long_name "Experiment_accession";
    String units "unitless";
  }
  Instrument {
    String long_name "Instrument";
    String units "unitless";
  }
  Study_Accession {
    String long_name "Study_accession";
    String units "unitless";
  }
  Study_Title {
    String long_name "Study_title";
    String units "unitless";
  }
  Sample_Accession {
    String long_name "Sample_accession";
    String units "unitless";
  }
  Library_Name {
    String long_name "Library_name";
    String units "unitless";
  }
  Collection_date {
    String long_name "Collection_date";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 18.31462, 18.33797;
    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 -64.7642, -64.70402;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  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.986592.1";
    Float64 Easternmost_Easting -64.70402;
    Float64 geospatial_lat_max 18.33797;
    Float64 geospatial_lat_min 18.31462;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.70402;
    Float64 geospatial_lon_min -64.7642;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-12-13T14:43:19Z (local files)
2025-12-13T14:43:19Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_986592_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/986592";
    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 18.33797;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 18.31462;
    String summary "In St. John, U.S. Virgin Islands, a longitudinal study of Colpophyllia natans was conducted. Six corals per site (two sites) were tagged and repeatedly sampled from July 2020 through March 2024, during which time, stony coral tissue loss disease (SCTLD) arrived on the reefs. As the tagged corals contracted SCTLD, coral tissue and near-coral seawater (2-5 centimeters from colony surface) were collected. Coral tissue was separated from the coral skeleton, and the seawater was filtered through 0.2-micrometer (µm) filters. DNA was extracted from the tissue and filters, and 16S ribosomal RNA gene sequencing was done to determine the bacteria and archaea communities that live within and near the corals. The goal of the study was to determine how coral-associated microbiomes are affected by the arrival of SCTLD through time. This data set contains the fastq files of the 16S amplicon sequencing of the coral tissue and near-coral seawater communities. National Center for Biotechnology Information (NCBI) SRA: SRP550314; BioProject: PRJNA1194595";
    String title "[Longitudinal study NCBI SRA] - NCBI Sequence Read Archive (SRA) accession numbers for fastq sequence files of 16S amplicons from a longitudinal study of SCTLD at St. John, U.S. Virgin Islands from 2020 to 2024 (A multi-scale approach to predicting infectious multi-host disease spread in marine benthic communities)";
    Float64 Westernmost_Easting -64.7642;
  }
}

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.

ERDDAP, Version 2.22
Disclaimers | Privacy Policy | Contact