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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Kāneʻohe Bay halos - vegetation surveys] - Vegetation surveys at artificial
reefs in Kāneʻohe Bay, Oʻahu conducted in 2022 and 2023 as part of a reef halo
dynamics study (CAREER: Decoding seascape-scale vegetation patterns on coral
reefs to understand ecosystem health: Integrating research and education from
organismal to planetary scales)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_987227_v1)
Range: longitude = -157.8068 to -157.8064°E, latitude = 21.46401 to 21.46428°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 {
  ImageName {
    String long_name "Imagename";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Month {
    Int32 actual_range 1, 12;
    String long_name "Month";
    String units "unitless";
  }
  Year {
    Int32 actual_range 2022, 2023;
    String long_name "Year";
    String units "unitless";
  }
  Day {
    Int32 actual_range 4, 30;
    String long_name "Day";
    String units "unitless";
  }
  Reef {
    String long_name "Reef";
    String units "unitless";
  }
  Transect {
    String long_name "Transect";
    String units "unitless";
  }
  DistanceTransect {
    String long_name "Distancetransect";
    String units "unitless";
  }
  BinNumber {
    String long_name "Binnumber";
    String units "unitless";
  }
  NumberAlgae {
    Int32 actual_range 0, 20;
    String long_name "Numberalgae";
    String units "count";
  }
  NumberSand {
    Int32 actual_range 0, 20;
    String long_name "Numbersand";
    String units "count";
  }
  QuadratSize {
    String long_name "Quadratsize";
    String units "unitless";
  }
  Notes {
    String long_name "Notes";
    String units "unitless";
  }
  DominantVegetation {
    String long_name "Dominantvegetation";
    String units "unitless";
  }
  Analyzer {
    String long_name "Analyzer";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 21.46401, 21.46428;
    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 -157.8068, -157.8064;
    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.987227.1";
    Float64 Easternmost_Easting -157.8064;
    Float64 geospatial_lat_max 21.46428;
    Float64 geospatial_lat_min 21.46401;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -157.8064;
    Float64 geospatial_lon_min -157.8068;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-11-25T17:55:02Z (local files)
2025-11-25T17:55:02Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_987227_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/987227";
    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 21.46428;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 21.46401;
    String summary "The goal of this dataset was to quantify substrate cover (vegetation or sand) of the benthos surrounding artificial reefs in Kāneʻohe Bay, Oʻahu, Hawaiʻi from August 2022-2023. These surveys were done monthly. We recorded three 5-meter-long video transects, spaced evenly around each artificial reef, starting from each of the three top-layer cinder blocks of the artificial reef, positioned perpendicularly to the cinder block and going outwards into the seagrass meadow. On each video transect, photos were taken continuously starting at the artificial reef. Each photo was imported into ImageJ, where the scale was set based on a 10 cm measure on the transect, and then a virtual 20x20 cm quadrat was laid directly on the right side of the transect. Virtual quadrats were laid consecutively every 20 cm (e.g., a quadrat from each of 0-20 cm, 20-40 cm, 40-60 cm, etc. Then, 20 random points were generated inside each distance bin and classified as sand or vegetation.";
    String title "[Kāneʻohe Bay halos - vegetation surveys] - Vegetation surveys at artificial reefs in Kāneʻohe Bay, Oʻahu conducted in 2022 and 2023 as part of a reef halo dynamics study (CAREER: Decoding seascape-scale vegetation patterns on coral reefs to understand ecosystem health: Integrating research and education from organismal to planetary scales)";
    Float64 Westernmost_Easting -157.8068;
  }
}

 

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