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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [St. Joseph Bay Urchin Surveys - 2016 and 2019] - Herbivorus green sea urchin
counts from surveys conducted in St. Joseph Bay, Florida, USA in May 2016 and
August 2019 (RAPID: Species on the Move: Tropicalization of Western Atlantic
Seagrass Beds)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_958329_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 UID (unitless) ?          1    195
 Year (unitless) ?          "2016"    "2019"
 MMDD (unitless) ?          "0517"    "0828"
 Date (unitless) ?          "2016-05-17"    "2019-08-28"
 site (unitless) ?          "10PSJ06"    "16PSJ24"
 planned_lat (degrees_north) ?          29.69444    29.79403
 planned_long (degrees_east) ?          -85.40142    -85.30408
 latitude (Visited_lat, degrees_north) ?          29.69446    29.79413
  < slider >
 longitude (Visited_long, degrees_east) ?          -85.40144    -85.30408
  < slider >
 surveyor (unitless) ?          "AR"    "DBD/WS"
 urchin_count (number of individuals per 0.5m x 0.5m quadrat) ?          0    13
 urchins_m2 (number of indviduals/m2) ?          0    52
 
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.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 {
  UID {
    Int32 actual_range 1, 195;
    String long_name "Uid";
    String units "unitless";
  }
  Year {
    String long_name "Year";
    String units "unitless";
  }
  MMDD {
    String long_name "Mmdd";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  site {
    String long_name "Site";
    String units "unitless";
  }
  planned_lat {
    Float32 actual_range 29.69444, 29.79403;
    String long_name "Planned_lat";
    String units "degrees_north";
  }
  planned_long {
    Float32 actual_range -85.40142, -85.30408;
    String long_name "Planned_long";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 29.69446, 29.79413;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Visited_lat";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -85.40144, -85.30408;
    String axis "X";
    String ioos_category "Location";
    String long_name "Visited_long";
    String standard_name "longitude";
    String units "degrees_east";
  }
  surveyor {
    String long_name "Surveyor";
    String units "unitless";
  }
  urchin_count {
    Int32 actual_range 0, 13;
    String long_name "Urchin_count";
    String units "number of individuals per 0.5m x 0.5m quadrat";
  }
  urchins_m2 {
    Int32 actual_range 0, 52;
    String long_name "Urchins_m2";
    String units "number of indviduals/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.958329.1";
    Float64 Easternmost_Easting -85.30408;
    Float64 geospatial_lat_max 29.79413;
    Float64 geospatial_lat_min 29.69446;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -85.30408;
    Float64 geospatial_lon_min -85.40144;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-08-15T23:18:30Z (local files)
2025-08-15T23:18:30Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_958329_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/958329";
    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 29.79413;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 29.69446;
    String summary 
"The herbivorus green sea urchin (Lytechinus variegatus) was surveyed across the southern part of St. Joseph Bay at 16 sites spaced approximately 1 nautical mile apart. Initial surveys were performed in May 2016 as part of a prior study of seagrass coverage, reproduction, and herbivore intensity. Using RAPID funds, the same survey was conducted in August 2019, 11 months after Hurricane Michael, an extremely powerful category 5 tropical cyclone, made landfall nearby with devastating effects. Densities were recorded by snorkelers in 5 replicate, haphazardly thrown 0.25-m2 quadrats at each site. 

Comparing pre- and post-hurricane urchin densities allows for estimates of how Hurricane Michael's passage impacted resident urchin densities. These data were collected by Dorothy Byron and Alexandra Rodriguez of the Dauphin Island Sea Lab.";
    String title "[St. Joseph Bay Urchin Surveys - 2016 and 2019] - Herbivorus green sea urchin counts from surveys conducted in St. Joseph Bay, Florida, USA in May 2016 and August 2019 (RAPID: Species on the Move: Tropicalization of Western Atlantic Seagrass Beds)";
    Float64 Westernmost_Easting -85.40144;
  }
}

 

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