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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Censuses of the native prey fish populations during lionfish surveys in
Eleuthera, Bahamas from July to August in 2012
  RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_653816)
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 2012, 2012;
    String description "Year of survey; yyyy";
    String ioos_category "Time";
    String long_name "Year";
    String units "unitless";
  }
  time_period {
    String description "Time of observation; classified as either dawn midday or dusk";
    String ioos_category "Time";
    String long_name "Time Period";
    String units "unitless";
  }
  month {
    Byte _FillValue 127;
    Byte actual_range 7, 8;
    String description "Month of survey; mm";
    String ioos_category "Time";
    String long_name "Month";
    String units "unitless";
  }
  day {
    Byte _FillValue 127;
    Byte actual_range 1, 31;
    String description "Day of the month survey took place; dd";
    String ioos_category "Time";
    String long_name "Day";
    String units "unitless";
  }
  time_start {
    String description "Time that the census began; HH:MM";
    String ioos_category "Time";
    String long_name "Time Start";
    String units "unitless";
  }
  time_end {
    String description "Time that the census ended; HH:MM";
    String ioos_category "Time";
    String long_name "Time End";
    String units "unitless";
  }
  reef {
    String description "Name of main reef where survey took place";
    String ioos_category "Unknown";
    String long_name "Reef";
    String units "unitless";
  }
  species {
    String description "First 2 letters of genus and first 2 letters of species (with the exception of UNJA = unidentified jawfish; SHIRMP = mysid shrimp; UNID = unidentified)";
    String ioos_category "Taxonomy";
    String long_name "Species";
    String units "unitless";
  }
  length_max_1 {
    Byte _FillValue 127;
    Byte actual_range 0, 11;
    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, 50;
    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, 75;
    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, 75;
    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, 81;
    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_6 {
    Byte _FillValue 127;
    Byte actual_range 0, 80;
    String description "Number of individuals that were between 5.1-6 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 6";
    String units "count";
  }
  length_max_7 {
    Byte _FillValue 127;
    Byte actual_range 0, 9;
    String description "Number of individuals that were between 6.1-7 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 7";
    String units "count";
  }
  length_max_8 {
    Byte _FillValue 127;
    Byte actual_range 0, 5;
    String description "Number of individuals that were between 7.1-8 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 8";
    String units "count";
  }
  length_max_9 {
    Byte _FillValue 127;
    Byte actual_range 0, 14;
    String description "Number of individuals that were between 8.1-9 cm total length";
    String ioos_category "Unknown";
    String long_name "Length Max 9";
    String units "count";
  }
  length_max_10 {
    Byte _FillValue 127;
    Byte actual_range 0, 5;
    String description "Number of individuals that were between 9.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, 1;
    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, 3;
    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, 2;
    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, 2;
    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, 1;
    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, 1;
    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, 0;
    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, 0;
    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, 0;
    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";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"This was an observational field study conducted from June - August 2012 to
determine whether lionfish behavior and movements change at different local
lionfish and prey fish densities. \\u00a0The study was conducted on sixteen
reefs in Rock Sound, Elethera, The Bahamas.\\u00a0 All reefs were at least 300
m from any reef on which lionfish removals had occurred, and were selected to
encompass a range of natural lionfish densities and reef sizes. \\u00a0
 
A pair of divers visited each reef at three times of day: within 2 hours of
sunrise (\\u2018dawn\\u2019), greater than 3 hours from sunrise or sunset
(\\u2018midday\\u2019), and within 2 hours of sunset (\\u2018dusk\\u2019).\\u00a0
Upon arriving at a reef, observers counted the number of lionfish present by
conducting lionfish-focused searches.\\u00a0 For each lionfish, observers
recorded the size (total length, visually estimated to the nearest cm),
behavior, and location the moment it was sighted.\\u00a0 Behaviors were
categorized as resting (sitting on the substrate, not moving), hovering (in
the water column oriented parallel to the bottom, but not moving), swimming
(actively moving), or hunting (oriented head down with pectoral fins
flared).\\u00a0 Location was categorized as the microhabitat on which lionfish
were observed (e.g. under a ledge, on top of the reef, in the surrounding
seagrass) and later divided into two major categories: sheltering (hidden
under structure) or exposed (on top of reef or in surrounding area).\\u00a0
Then, 10-minute focal observations were conducted on two randomly-selected
lionfish or a single lionfish when there was only one individual present per
reef.\\u00a0 During focal observations, a trained observer recorded the
behavior of lionfish at 30-second intervals for 10 minutes using the same
categories as above.\\u00a0 The observers also noted any strikes at prey,
successful kills, and obviously aggressive interactions (chases, posturing)
between lionfish or between lionfish and other species.\\u00a0 Throughout the
entire visit to each reef, divers noted the time when any lionfish departed
from or arrived at the reef and its behavior.\\u00a0 A lionfish was defined as
departing from the reef if it traveled at least 10 m from the reef.\\u00a0 A
lionfish was considered arriving at a reef if it swam in from the surrounding
areas and had not been previously observed at that reef during that
observation period.\\u00a0 At the conclusion of the focal observations, the
divers re-counted the number of lionfish present while conducting a survey of
resident native fishes.\\u00a0 Divers recorded the abundance and body size (TL)
of all fish 1 - 15 cm TL, native mesopredators that are ecologically similar
to lionfish (e.g. Cephalopholis cruentata [graysby grouper]), and top
predators (e.g. Epinephelus striatus [Nassau grouper]) on and within 1 m of
the reef.";
    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 
"Behavior and Movement - Native Fish Survey 
   Lead PI: Mark Hixon 
   Sub-Project Lead: Casey Benkwitt 
   Version 10 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-11T18:27:30Z";
    String date_modified "2019-05-22T18:19:28Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.653816.1";
    String history 
"2019-07-20T23:52:38Z (local files)
2019-07-20T23:52:38Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_653816.das";
    String infoUrl "https://www.bco-dmo.org/dataset/653816";
    String institution "BCO-DMO";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, day, dmo, end, erddap, 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, length_max_6, length_max_7, length_max_8, length_max_9, management, max, month, oceanography, office, period, preliminary, reef, species, start, taxonomy, time, time_end, time_period, time_start, 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/653816";
    String param_mapping "{'653816': {}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/653816/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, length_max_45, length_max_50, length_max_100, length_max_150";
    String summary "Censuses of the native prey fish populations during lionfish surveys in Eleuthera, Bahamas from July to August in 2012";
    String title "Censuses of the native prey fish populations during lionfish surveys in Eleuthera, Bahamas from July to August in 2012";
    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