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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [16S rRNA amplicon sequence metadata from water samples and biofilms] - 16S
rRNA gene amplicon sequences metadata collected from water samples and biofilms
on mineral substrates deployed in the Lau Basin (Tonga) during R/V Thompson
cruise TN401 from Mar to Apr 2022 (RUI: Collaborative Research: The impact of
symbiont-larval interactions on species distributions across southwestern
Pacific hydrothermal vents)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_964227_v1)
Range: longitude = -176.57 to -71.48°E, latitude = -21.99 to 41.39°N, depth = 1877.0 to 2725.0m
Information:  Summary ? | License ? | FGDC | ISO 19115 | 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: 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Sample_ID {
    String long_name "Sample_id";
    String units "unitless";
  }
  Bioproject_accession {
    String long_name "Bioproject_accession";
    String units "unitless";
  }
  Biosample_accession {
    String long_name "Biosample_accession";
    String units "unitless";
  }
  Collection_date {
    String long_name "Collection_date";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -21.99, 41.39;
    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 -176.57, -71.48;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 1877, 2725;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Sample_type {
    String long_name "Sample_type";
    String units "unitless";
  }
  Colonizer_No {
    Int32 actual_range 1, 15;
    String long_name "Colonizer_no";
    String units "unitless";
  }
  SRA_Study {
    String long_name "Sra_study";
    String units "unitless";
  }
  SRA_accession {
    String long_name "Sra_accession";
    String units "unitless";
  }
  Sequencing_technologies {
    String long_name "Sequencing_technologies";
    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.964227.1";
    Float64 Easternmost_Easting -71.48;
    Float64 geospatial_lat_max 41.39;
    Float64 geospatial_lat_min -21.99;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -71.48;
    Float64 geospatial_lon_min -176.57;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 2725.0;
    Float64 geospatial_vertical_min 1877.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-08-09T08:04:32Z (local files)
2025-08-09T08:04:32Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_964227_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/964227";
    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 41.39;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -21.99;
    String summary "16S rRNA gene amplicon sequences were generated from biofilms present on crushed substrates deployed at Lau Basin hydrothermal vents for approximately two weeks during R/V Thompson cruise TN401 from March to April 2022, typically in diffuse fluid flow. 16S rRNA gene amplicon sequences were generated from seawater or hydrothermal fluid samples collected on to filters via ROV deployed instruments. This dataset contains NCBI accession metadata and sample collection information.";
    String title "[16S rRNA amplicon sequence metadata from water samples and biofilms] - 16S rRNA gene amplicon sequences metadata collected from water samples and biofilms on mineral substrates deployed in the Lau Basin (Tonga) during  R/V Thompson cruise TN401 from Mar to Apr 2022 (RUI: Collaborative Research: The impact of symbiont-larval interactions on species distributions across southwestern Pacific hydrothermal vents)";
    Float64 Westernmost_Easting -176.57;
  }
}

 

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