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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Abalone and Urchin Recruitment Modules] - Number and sizes of abalone and
urchin recorded during dive surveys at specially designed recruitment
modules (RMs) deployed at rocky subtidal reef at Van Damme State Park,
Mendocino County, California, USA from August 2001 to August
2023 (Collaborative Research: The effects of marine heatwaves on reproduction,
larval transport and recruitment in sea urchin metapopulations)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_929812_v1)
Range: longitude = -123.7933 to -123.7933°E, latitude = 39.27069 to 39.27069°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | 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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
[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 {
  ARM_Num {
    String long_name "Arm_num";
    String units "unitless";
  }
  Year {
    String long_name "Year";
    String units "unitless";
  }
  No_ARMs {
    Int32 actual_range 9, 13;
    String long_name "No_arms";
    String units "unitless";
  }
  SpeciesID {
    String long_name "Speciesid";
    String units "unitless";
  }
  CommonName {
    String long_name "Commonname";
    String units "unitless";
  }
  ScientificName {
    String long_name "Scientificname";
    String units "unitless";
  }
  Size {
    String long_name "Size";
    String units "millimeters (mm)";
  }
  LT_21 {
    Int32 actual_range 1, 1;
    String long_name "Lt_21";
    String units "unitless";
  }
  LT_51 {
    Int32 actual_range 1, 1;
    String long_name "Lt_51";
    String units "unitless";
  }
  GT_50 {
    Int32 actual_range 1, 1;
    String long_name "Gt_50";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 39.27069, 39.27069;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -123.7933, -123.7933;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  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.929812.1";
    Float64 Easternmost_Easting -123.7933;
    Float64 geospatial_lat_max 39.27069;
    Float64 geospatial_lat_min 39.27069;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -123.7933;
    Float64 geospatial_lon_min -123.7933;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-01-15T19:37:37Z (local files)
2025-01-15T19:37:37Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_929812_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/929812";
    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.";
    Float64 Northernmost_Northing 39.27069;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.27069;
    String summary 
"An important facet of the Kelp Forest Monitoring project is sampling recruitment of juvenile abalone and sea urchins. Specially designed recruitment modules (RMs) made of stainless steel and filled with ½ concrete cinder blocks as habitat were bolted to the rocky subtidal reef at Van Damme State Park, Mendocino County, California. Twelve RMs were deployed at 10 to 12 meters depth in three groups of four in August of 2000. They were allowed to season for a year before surveys began in August 2001.

Each August, SCUBA dive teams collected and measured the organisms inside the modules. The data associated with this dataset are the number and sizes of red abalone (Haliotis rufescens), pinto abalone (H. kamtschatkana), flat abalone (H. walallensis), red sea urchins (Mesocentrotus franciscanus), and purple sea urchins (Strongylocentrotus purpuratus). Data are presented in tabular format with a row for each RM each year.";
    String title "[Abalone and Urchin Recruitment Modules] - Number and sizes of abalone and urchin recorded during dive surveys at specially designed recruitment modules (RMs) deployed at rocky subtidal reef at Van Damme State Park, Mendocino County, California, USA from August 2001 to August 2023 (Collaborative Research: The effects of marine heatwaves on reproduction, larval transport and recruitment in sea urchin metapopulations)";
    Float64 Westernmost_Easting -123.7933;
  }
}

 

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