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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Antillogorgia americana Branch Variation] - Number and size of eggs found in
five different branches from a single Antillogorgia americana from a study site
in the San Blas Islands, Panama from July 1990 to August 1991 (Collaborative
Research: Pattern and process in the abundance and recruitment of Caribbean
octocorals) Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_918002_v1)
Range: longitude = -78.9583 to -78.9583°E
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 {
  Branch {
    Int32 actual_range 1, 5;
    String long_name "Branch";
    String units "unitless";
  }
  Side {
    Int32 actual_range 1, 2;
    String long_name "Side";
    String units "unitless";
  }
  tip_base {
    Int32 actual_range 1, 2;
    String long_name "Tip_base";
    String units "unitless";
  }
  Branchlet {
    Int32 actual_range 1, 10;
    String long_name "Branchlet";
    String units "unitless";
  }
  polyp {
    Int32 actual_range 1, 10;
    String long_name "Polyp";
    String units "unitless";
  }
  count {
    Int32 actual_range 0, 6;
    String long_name "Count";
    String units "unitless";
  }
  AvgDiam {
    Float32 actual_range 0.26, 0.84;
    String long_name "Avgdiam";
    String units "millimeters (mm)";
  }
  TotVol {
    Float32 actual_range 0.0, 0.43;
    String long_name "Totvol";
    String units "cubic millimeters (mm^3)";
  }
  Diam1 {
    Float32 actual_range 0.16, 0.84;
    String long_name "Diam1";
    String units "millimeters (mm)";
  }
  Diam2 {
    Float32 actual_range 0.0, 0.8;
    String long_name "Diam2";
    String units "millimeters (mm)";
  }
  Diam3 {
    Float32 actual_range 0.0, 0.72;
    String long_name "Diam3";
    String units "millimeters (mm)";
  }
  Diam4 {
    Float32 actual_range 0.0, 0.6;
    String long_name "Diam4";
    String units "millimeters (mm)";
  }
  Diam5 {
    Float32 actual_range 0.0, 0.36;
    String long_name "Diam5";
    String units "millimeters (mm)";
  }
  Diam6 {
    Float32 actual_range 0.0, 0.44;
    String long_name "Diam6";
    String units "millimeters (mm)";
  }
  Latitude {
    Float32 actual_range 9.5486, 9.5486;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -78.9583, -78.9583;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Month {
    String long_name "Month";
    String units "unitless";
  }
  Year {
    String long_name "Year";
    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.918002.1";
    Float64 Easternmost_Easting -78.9583;
    Float64 geospatial_lon_max -78.9583;
    Float64 geospatial_lon_min -78.9583;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-01T06:36:44Z (local files)
2024-11-01T06:36:44Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_918002_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/918002";
    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 
"The reproductive biology of the branching octocoral Antillogorgia americana was studied at a site on the Caribbean coast of Panama in 1990-1991. Eleven colonies were tagged and monthly samples were collected over a 14-month period. Colonies were gonochoric and the samples included 6 females and 4 females. Ten polyps were examined from each sample and the number and size of gonads were determined.  An additional 4 branches were sampled from a female colony in January 1991 and fecundity was determined relative to the branch, position of branchlet on the branch, and position of the polyp on the branchlet. The lack of synchrony among colonies on the scale of months may reflect less need for all colonies to spawn in a single event among abundant species that release large numbers of gametes. Such a strategy also spreads the risk of reproductive failure due to environmental conditions during any single month. Multiple spawning episodes can also drive reproductive isolation of populations and may reflect the presence of cryptic species within the taxon. Studies of reproductive timing can be an important adjunct in identifying variation in life history strategies as well as assessing the validity of species boundaries. 

This dataset describes branch variation, including the number and size of eggs found in five different branches from a single Antillogorgia americana. Ten polyps were sampled from four branchlets and two positions on the branchlets of each branch.";
    String title "[Antillogorgia americana Branch Variation] - Number and size of eggs found in five different branches from a single Antillogorgia americana from a study site in the San Blas Islands, Panama from July 1990 to August 1991 (Collaborative Research: Pattern and process in the abundance and recruitment of Caribbean octocorals)";
    Float64 Westernmost_Easting -78.9583;
  }
}

 

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