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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Post-hurricane Sponge Volume] - Sponge volume from repeated surveys in St.
Thomas, U.S. Virgin Islands, before and after the 2017 hurricane season (RAPID:
Collaborative Research: Sponge resilience in the face of multiple stressors)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_889972_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";
  }
  Latitude {
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  quadrat {
    String long_name "Quadrat";
    String units "unitless";
  }
  sponge_volume {
    Float32 actual_range 7.98, 12221.4;
    String long_name "Sponge_volume";
    String units "centimeters cubed per square meter (cm3/m2)";
  }
 }
  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.889972.1";
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-16T13:57:46Z (local files)
2024-11-16T13:57:46Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_889972_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/889972";
    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 
"Prior to the 2017 hurricanes, six shallow (8-15 meter depth) reef sites had been selected from the Virgin Islands Territorial Coral Reef Monitoring Program's (TCRMP) permanent monitoring sites to study variation in sponge communities - Black Point (BP), Coculus Rock (CR), and Magens Bay (MB), which are in embayments with heavily developed watersheds. Buck Island (BI) and Savana Island (SI) are located near undeveloped offshore cays. Botany Bay (BB) is a nearshore site in a bay with a low level of watershed development.

This dataset represents sponge volume from these repeated surveys before and after the 2017 hurricane season. We used three randomly selected transects out of the six permanently established 10-meter TCRMP transects at each site. The same three transects at each site were re-surveyed repeatedly in August 2016 (pre-hurricanes), December 2017 (10 weeks post-hurricanes), March 2018 (24 weeks post-hurricanes), November 2018 (61 weeks post-hurricanes), and July 2019 (93 weeks post-hurricanes).";
    String title "[Post-hurricane Sponge Volume] - Sponge volume from repeated surveys in St. Thomas, U.S. Virgin Islands, before and after the 2017 hurricane season (RAPID: Collaborative Research: Sponge resilience in the face of multiple stressors)";
  }
}

 

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