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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Percent cover measure of mussel bed succession on rocky shores due to intra-
population variation in dogwhelk drilling] - Percent cover measure of mussel
bed succession on rocky shores due to intra-population variation in dogwhelk
drilling (Coastal mosaics of local adaptation and the eco-evolutionary dynamics
of a marine predator-prey interaction)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_918518_v1)
Range: longitude = -123.0781 to -123.0781°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 {
  Block {
    Int32 actual_range 1, 16;
    String long_name "Block";
    String units "unitless";
  }
  Plot_Number {
    Int32 actual_range 1, 128;
    String long_name "Plot_number";
    String units "unitless";
  }
  Family {
    String long_name "Family";
    String units "unitless";
  }
  Site_Latitude {
    Float32 actual_range 38.32352, 38.32352;
    String long_name "Site_latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -123.0781, -123.0781;
    String axis "X";
    String ioos_category "Location";
    String long_name "Site_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Treatment {
    String long_name "Treatment";
    String units "unitless";
  }
  Family_x_Treatment {
    String long_name "Family_x_treatment";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Check {
    Int32 actual_range 0, 7;
    String long_name "Check";
    String units "unitless";
  }
  Bare_Rock {
    Float32 actual_range 0.0, 75.37025;
    String long_name "Bare_rock";
    String units "percent (%)";
  }
  Acorn_Barnacles {
    Float32 actual_range 0.0, 97.26539;
    String long_name "Acorn_barnacles";
    String units "percent (%)";
  }
  Mussels {
    Float32 actual_range 0.0, 99.36169;
    String long_name "Mussels";
    String units "percent (%)";
  }
  Gooseneck_Barnacles {
    Float32 actual_range 0.0, 97.79703;
    String long_name "Gooseneck_barnacles";
    String units "percent (%)";
  }
  Other_Sessile_Animals {
    Float32 actual_range 0.0, 23.539;
    String long_name "Other_sessile_animals";
    String units "percent (%)";
  }
  Coralline_Algae {
    Float32 actual_range 0.0, 66.76447;
    String long_name "Coralline_algae";
    String units "percent (%)";
  }
  Algae_and_Surfgrass {
    Float32 actual_range 0.0, 21.23678;
    String long_name "Algae_and_surfgrass";
    String units "percent (%)";
  }
 }
  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.918518.1";
    Float64 Easternmost_Easting -123.0781;
    Float64 geospatial_lon_max -123.0781;
    Float64 geospatial_lon_min -123.0781;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T14:34:40Z (local files)
2024-11-08T14:34:40Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_918518_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/918518";
    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 "Despite growing interest of eco-evolutionary dynamics, there have been few experiments that test the importance of these feedbacks in natural ecosystems at the community level. A selection experiment on intra-population variation in dogwhelk (Nucella canaliculata) drilling was performed in the laboratory. Dogwhelks were given one of four early-life diet treatments (thin-shelled Mytilus trossulus mussels, two treatments of M. californianus from two populations known to differ in shell thickness, and acorn barnacles) for the first 3 months of life. Surviving adult dogwhelks were outplanted to field cages at Bodega Marine Reserve to test the ecological consequences of divergent phenotypes. Mussel bed succession was quantified by percent cover of sessile organisms in the plots over the course of approximately one year.";
    String title "[Percent cover measure of mussel bed succession on rocky shores due to intra-population variation in dogwhelk drilling] - Percent cover measure of mussel bed succession on rocky shores due to intra-population variation in dogwhelk drilling (Coastal mosaics of local adaptation and the eco-evolutionary dynamics of a marine predator-prey interaction)";
    Float64 Westernmost_Easting -123.0781;
  }
}

 

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