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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Shell thickness of mussel recruits] - Shell thickness of mussel recruits
quantified in two species, Mytilus trossulus and Mytilus californianus (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_918420_v1)
Range: longitude = -124.1136 to -121.9291°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 {
  Mussel_Number {
    Int32 actual_range 1, 179;
    String long_name "Mussel_number";
    String units "unitless";
  }
  Mussel_Type {
    String long_name "Mussel_type";
    String units "unitless";
  }
  Site_Latitude {
    Float32 actual_range 36.44758, 44.24401;
    String long_name "Site_latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -124.1136, -121.9291;
    String axis "X";
    String ioos_category "Location";
    String long_name "Site_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Weight {
    Float32 actual_range 8.66e-5, 0.0517971;
    String long_name "Weight";
    String units "grams (g)";
  }
  Magnification {
    String long_name "Magnification";
    String units "unitless";
  }
  Length_L {
    Float32 actual_range 0.91, 7.545;
    String long_name "Length_l";
    String units "millimeters (mm)";
  }
  Length_R {
    Float32 actual_range 0.87, 7.559;
    String long_name "Length_r";
    String units "millimeters (mm)";
  }
  Area_L {
    Float32 actual_range 0.461, 25.197;
    String long_name "Area_l";
    String units "square millimeters (mm^2)";
  }
  Area_R {
    Float32 actual_range 0.552, 25.268;
    String long_name "Area_r";
    String units "square millimeters (mm^2)";
  }
  Total_Area {
    Float32 actual_range 1.093, 50.234;
    String long_name "Total_area";
    String units "square millimeters (mm^2)";
  }
  Shell_Thickness {
    Float32 actual_range 8.36e-5, 9.173e-4;
    String long_name "Shell_thickness";
    String units "grams per square millimeter (g/(mm^2))";
  }
  Notes {
    String long_name "Notes";
    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.918420.1";
    Float64 Easternmost_Easting -121.9291;
    Float64 geospatial_lon_max -121.9291;
    Float64 geospatial_lon_min -124.1136;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-18T08:22:03Z (local files)
2024-11-18T08:22:03Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_918420_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/918420";
    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 "Mussels are common on rocky shores along the west coast of North America and are prey to a number of species, including the Channeled Dogwhelk, Nucella canaliculata. When N. canaliculata hatch, they are dependent on a supply of newly recruited prey that are variable in abundance. To determine the strength of selection that early-life diet may impose on juvenile dogwhelks, recruit mussel shell thickness was quantified for two mussel species, Mytilus trossulus and Mytilus californianus. In addition, recruit M. californianus were collected from two locations, Bodega Marine Reserve and Soberanes Point, known to differ in the thickness of adult M. californianus.";
    String title "[Shell thickness of mussel recruits] - Shell thickness of mussel recruits quantified in two species, Mytilus trossulus and Mytilus californianus (Coastal mosaics of local adaptation and the eco-evolutionary dynamics of a marine predator-prey interaction)";
    Float64 Westernmost_Easting -124.1136;
  }
}

 

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