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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Effect of lionfish densities on native coral-reef fishes from Lee Stocking
Island, Bahamas during 2009-2012 (Biodiversity Loss Effects Lionfish project)
  RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_655301)
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
    Int16 _FillValue 32767;
    Int16 actual_range 2011, 2011;
    String description "Year of survey; YYYY";
    String ioos_category "Time";
    String long_name "Year";
    String units "unitless";
  }
  reef_type {
    String description "ART = Artificial; all observations conducted on an artificial reef";
    String ioos_category "Unknown";
    String long_name "Reef Type";
    String units "unitless";
  }
  month {
    Byte _FillValue 127;
    Byte actual_range 6, 8;
    String description "Month of survey; mm";
    String ioos_category "Time";
    String long_name "Month";
    String units "unitless";
  }
  visit_number {
    Byte _FillValue 127;
    Byte actual_range 1, 9;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "Visit number; typically one visit per reef per week";
    String ioos_category "Statistics";
    String long_name "Visit Number";
    String units "unitless";
  }
  day {
    Byte _FillValue 127;
    Byte actual_range 1, 31;
    String description "Day of survey; dd";
    String ioos_category "Time";
    String long_name "Day";
    String units "unitless";
  }
  reef_number {
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "Reef id number";
    String ioos_category "Statistics";
    String long_name "Reef Number";
    String units "unitless";
  }
  time_start {
    String description "Time that census began; HH:MM";
    String ioos_category "Time";
    String long_name "Time Start";
    String units "unitless";
  }
  time_end {
    String description "Time that census ended; HH:MM";
    String ioos_category "Time";
    String long_name "Time End";
    String units "unitless";
  }
  lionfish_density_initial {
    Byte _FillValue 127;
    Byte actual_range 0, 14;
    String description "Initial number of lionfish that were transplanted to each reef; each reef measured 1 square meters so lionfish density = number of lionfish on the reef";
    String ioos_category "Physical Oceanography";
    String long_name "Lionfish Density Initial";
    String units "count per meter squared";
  }
  lionfish_density_mean {
    Byte _FillValue 127;
    Byte actual_range 0, 14;
    String description "Average lionfish density (rounded to the nearest fish) on each reef throughout the experiment";
    String ioos_category "Physical Oceanography";
    String long_name "Lionfish Density Mean";
    String units "count per meter squared";
  }
  species {
    String description "First 2 letters of genus and first 2 letters of species; see species key dataset for full species names.";
    String ioos_category "Taxonomy";
    String long_name "Species";
    String units "unitless";
  }
  length_max_1 {
    Byte _FillValue 127;
    Byte actual_range 0, 12;
    String description "Number of individuals that were between 0-1 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 1";
    String units "count";
  }
  length_max_2 {
    Byte _FillValue 127;
    Byte actual_range 0, 31;
    String description "Number of individuals that were between 1.1-2 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 2";
    String units "count";
  }
  length_max_3 {
    Byte _FillValue 127;
    Byte actual_range 0, 42;
    String description "Number of individuals that were between 2.1-3 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 3";
    String units "count";
  }
  length_max_4 {
    Byte _FillValue 127;
    Byte actual_range 0, 25;
    String description "Number of individuals that were between 3.1-4 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 4";
    String units "count";
  }
  length_max_5 {
    Byte _FillValue 127;
    Byte actual_range 0, 12;
    String description "Number of individuals that were between 4.1-5 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 5";
    String units "count";
  }
  length_max_10 {
    Byte _FillValue 127;
    Byte actual_range 0, 25;
    String description "Number of individuals that were between 5.1-10 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 10";
    String units "count";
  }
  length_max_15 {
    Byte _FillValue 127;
    Byte actual_range 0, 50;
    String description "Number of individuals that were between 10.1-15 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 15";
    String units "count";
  }
  length_max_20 {
    Byte _FillValue 127;
    Byte actual_range 0, 50;
    String description "Number of individuals that were between 15.1-20 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 20";
    String units "count";
  }
  length_max_25 {
    Byte _FillValue 127;
    Byte actual_range 0, 20;
    String description "Number of individuals that were between 20.1-25 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 25";
    String units "count";
  }
  length_max_30 {
    Byte _FillValue 127;
    Byte actual_range 0, 15;
    String description "Number of individuals that were between 25.1-30 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 30";
    String units "count";
  }
  length_max_35 {
    Byte _FillValue 127;
    Byte actual_range 0, 3;
    String description "Number of individuals that were between 30.1-35 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 35";
    String units "count";
  }
  length_max_40 {
    Byte _FillValue 127;
    Byte actual_range 0, 2;
    String description "Number of individuals that were between 35.1-40 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 40";
    String units "count";
  }
  length_max_45 {
    Byte _FillValue 127;
    Byte actual_range 0, 1;
    String description "Number of individuals that were between 40.1-45 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 45";
    String units "count";
  }
  length_max_50 {
    Byte _FillValue 127;
    Byte actual_range 0, 0;
    String description "Number of individuals that were between 45.1-50 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 50";
    String units "count";
  }
  length_max_100 {
    Byte _FillValue 127;
    Byte actual_range 0, 1;
    String description "Number of individuals that were between 50.1-100 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 100";
    String units "count";
  }
  length_max_150 {
    Byte _FillValue 127;
    Byte actual_range 0, 1;
    String description "Number of individuals that were between 100.1-150 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 150";
    String units "count";
  }
  invert_count {
    Byte _FillValue 127;
    Byte actual_range 0, 13;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String description "Abundance of invertebrates surveyed; sizes were not estimated. See species key dataset for full species names.";
    String ioos_category "Statistics";
    String long_name "Invert Count";
    String units "count";
  }
  notes {
    String description "Notes on observations";
    String ioos_category "Unknown";
    String long_name "Notes";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"This was a field experiment conducted on artificial patch reefs to test for
effects of\\u00a0invasive red lionfish density on native coral-reef fishes.
Four reefs were used as 0-lionfish control reefs and there was one reef per
remaining lionfish treatment (2, 4, 6, 8, 10, and 12 lionfish/m2). Using SCUBA
and handnets, we collected lionfish ranging in initial size from 40 to 71mm
total length [TL] from nearby reefs.\\u00a0 Each lionfish was given a unique
elastomer tag (Northwest Marine Technology Inc., Shaw Island, WA, USA) to
differentiate between lionfish at the start of the experiment and any new
immigrants over the course of the study and to monitor demographic rates as
part of another study (see related files and references). Treatments were
started on all reefs within a 2-week period. To maintain treatments, we
monitored lionfish density during weekly visits and removed any new lionfish
recruits (total of 15 throughout experiment) and immigrants (total of 5
throughout experiment). In addition, we removed resident native piscivores and
standardized the number of Nassau grouper (Epinephelus striatus) and
territorial damselfishes (Stegastes spp.) weekly to mitigate any confounding
effects of these strong interactors on fish recruitment. Of the lionfish
initially placed on the reefs, only 6 out of 40 disappeared. To account for
the small changes in lionfish density throughout the experiment, we averaged
the weekly lionfish densities on each reef over the course of the experiment
(1, 2, 4, 7, 10, and 12 lionfish/m2).
 
Following the establishment of lionfish density treatments, a pair of divers
using SCUBA censused the entire fish community on each reef weekly for 7
weeks, recording the species, abundance, and body size (TL estimated to the
nearest centimeter) of all fish present both on the reefs and within a 1-m
radius around the reefs. Divers slowly approached the reefs and first counted
all planktivorous and active species hovering above the reefs from a distance
of approximately 3 m. From a distance of 1 m, the divers slowly circled the
reefs and counted all other species, using dive lights to count cryptic
species in holes.";
    String awards_0_award_nid "561016";
    String awards_0_award_number "OCE-1233027";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1233027";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "Dr David  L. Garrison";
    String awards_0_program_manager_nid "50534";
    String cdm_data_type "Other";
    String comment 
"Effects on Native Fishes - Census Data 
   Lead PI: Mark Hixon 
   Sub-Project Lead: Casey Benkwitt 
   Version 12 August 2016 
 Species codes are first two letters of genus and species; See species key.";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.2d  13 Jun 2019";
    String date_created "2016-08-22T19:05:26Z";
    String date_modified "2019-05-14T20:45:06Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.655301.1";
    String history 
"2019-06-25T09:26:00Z (local files)
2019-06-25T09:26:00Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_655301.das";
    String infoUrl "https://www.bco-dmo.org/dataset/655301";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, chemical, count, data, dataset, day, density, dmo, end, erddap, initial, invert, invert_count, length, length_max_1, length_max_10, length_max_100, length_max_15, length_max_150, length_max_2, length_max_20, length_max_25, length_max_3, length_max_30, length_max_35, length_max_4, length_max_40, length_max_45, length_max_5, length_max_50, lionfish, lionfish_density_initial, lionfish_density_mean, management, max, mean, month, notes, number, oceanography, office, physical, physical oceanography, preliminary, reef, reef_number, reef_type, species, start, statistics, taxonomy, time, time_end, time_start, type, visit, visit_number, year";
    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 metadata_source "https://www.bco-dmo.org/api/dataset/655301";
    String param_mapping "{'655301': {}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/655301/parameters";
    String people_0_affiliation "University of Hawaii";
    String people_0_person_name "Dr Mark Hixon";
    String people_0_person_nid "51647";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Oregon State University";
    String people_1_affiliation_acronym "OSU";
    String people_1_person_name "Dr Cassandra E Benkwitt";
    String people_1_person_nid "51706";
    String people_1_role "Contact";
    String people_1_role_type "related";
    String people_2_affiliation "Woods Hole Oceanographic Institution";
    String people_2_affiliation_acronym "WHOI BCO-DMO";
    String people_2_person_name "Hannah Ake";
    String people_2_person_nid "650173";
    String people_2_role "BCO-DMO Data Manager";
    String people_2_role_type "related";
    String project "Mechanisms and Consequences of Fish Biodiversity Loss on Atlantic Coral Reefs Caused by Invasive Pacific Lionfish";
    String projects_0_acronym "BiodiversityLossEffects_lionfish";
    String projects_0_description 
"The Pacific red lionfish (Pterois volitans), a popular aquarium fish, was introduced to the Atlantic Ocean in the vicinity of Florida in the late 20th century. Voraciously consuming small native coral-reef fishes, including the juveniles of fisheries and ecologically important species, the invader has undergone a population explosion that now ranges from the U.S. southeastern seaboard to the Gulf of Mexico and across the greater Caribbean region. The PI's past research determined that invasive lionfish (1) have escaped their natural enemies in the Pacific (lionfish are much less abundant in their native range); (2) are not yet controlled by Atlantic predators, competitors, or parasites; (3) have strong negative effects on populations of native Atlantic fishes; and (4) locally reduce the diversity (number of species) of native fishes. The lionfish invasion has been recognized as one of the major conservation threats worldwide.
The Bahamas support the highest abundances of invasive lionfish globally. This system thus provides an unprecedented opportunity to understand the direct and indirect effects of a major invader on a diverse community, as well as the underlying causative mechanisms. The PI will focus on five related questions: (1) How does long-term predation by lionfish alter the structure of native reef-fish communities? (2) How does lionfish predation destabilize native prey population dynamics, possibly causing local extinctions? (3) Is there a lionfish-herbivore-seaweed trophic cascade on invaded reefs? (4) How do lionfish modify cleaning mutualisms on invaded reefs? (5) Are lionfish reaching densities where natural population limits are evident?�";
    String projects_0_end_date "2016-07";
    String projects_0_geolocation "Three Bahamian sites: 24.8318, -076.3299;  23.8562, -076.2250; 23.7727, -076.1071; Caribbean Netherlands: 12.1599, -068.2820";
    String projects_0_name "Mechanisms and Consequences of Fish Biodiversity Loss on Atlantic Coral Reefs Caused by Invasive Pacific Lionfish";
    String projects_0_project_nid "561017";
    String projects_0_project_website "http://hixon.science.oregonstate.edu/content/highlight-lionfish-invasion";
    String projects_0_start_date "2012-08";
    String publisher_name "Hannah Ake";
    String publisher_role "BCO-DMO Data Manager(s)";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables "year, reef_type, length_max_50";
    String summary "Effect of lionfish densities on native coral-reef fishes from Lee Stocking Island, Bahamas during 2009-2012 (Biodiversity Loss Effects Lionfish project)";
    String title "Effect of lionfish densities on native coral-reef fishes from Lee Stocking Island, Bahamas during 2009-2012 (Biodiversity Loss Effects Lionfish project)";
    String version "1";
    String xml_source "osprey2erddap.update_xml() v1.5-beta";
  }
}

 

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 1.82
Disclaimers | Privacy Policy | Contact