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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Aquatic Eddy Covariance Processed Measurements] - Processed aquatic eddy
covariance measurements collected under hypoxic conditions from seven eddy
covariance lander deployments made during summer cruises on the Oregon and
Washington mid-shelf in 2018 and 2022 (Environmental consequences of expanded
recruitment of an ecosystem engineer on a hypoxia-influenced continental shelf)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_962251_v1)
Range: longitude = -124.313 to -124.067°E, latitude = 44.571 to 46.45°N, time = 2018-07-03T22:45:00Z to 2022-09-17T04:45:00Z
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: 
Time range:    |<   -       
[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 {
  Elapsed_time {
    Float32 actual_range 0.0, 113399.9;
    String long_name "Elapsed_time";
    String units "seconds";
  }
  Velocity_x {
    Float32 actual_range -27.14431, 23.2525;
    String long_name "Velocity_x";
    String units "cm/s";
  }
  Velocity_y {
    Float32 actual_range -24.605, 22.33124;
    String long_name "Velocity_y";
    String units "cm/s";
  }
  Velocity_z {
    Float32 actual_range -7.10074, 5.60466;
    String long_name "Velocity_z";
    String units "cm/s";
  }
  Dissolved_oxygen {
    Float32 actual_range 12.40219, 87.1641;
    String long_name "Dissolved_oxygen";
    String units "micromoles/L";
  }
  Pressure {
    Float32 actual_range 65.05825, 85.259;
    String long_name "Pressure";
    String units "db";
  }
  Matlab_Datenumber_Local {
    Float32 actual_range 737244.7, 738782.3;
    String long_name "Matlab_datenumber_local";
    String units "unitless";
  }
  Burst {
    Float32 actual_range 1.0, 126.0;
    String long_name "Burst";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5306579e+9, 1.6633899e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  St_ID {
    String long_name "St_id";
    String units "unitless";
  }
  Deployment {
    String long_name "Deployment";
    String units "unitless";
  }
  Oxy_sensor {
    String long_name "Oxy_sensor";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 44.571, 46.45;
    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 -124.313, -124.067;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Heading {
    Float32 actual_range 73.0, 327.89;
    String long_name "Heading";
    String units "degrees";
  }
  Pitch {
    Float32 actual_range -0.41, 0.716;
    String long_name "Pitch";
    String units "degrees";
  }
  Roll {
    Float32 actual_range -0.8, 0.62;
    String long_name "Roll";
    String units "degrees";
  }
  Height {
    Float32 actual_range 26.5, 31.05;
    String long_name "Height";
    String units "cm";
  }
 }
  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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.962251.1";
    Float64 Easternmost_Easting -124.067;
    Float64 geospatial_lat_max 46.45;
    Float64 geospatial_lat_min 44.571;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -124.067;
    Float64 geospatial_lon_min -124.313;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-08-02T17:30:22Z (local files)
2025-08-02T17:30:22Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_962251_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/962251";
    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 46.45;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.571;
    String summary "This dataset includes time-series measurements from seven eddy covariance lander deployments made on the Oregon or Washington continental shelf at mean water depths ranging from 68-84 m in 2018 and 2022. Average dissolved oxygen concentrations during these deployments ranged from 17-75 micro moles per liter allowing assessments of benthic oxygen fluxes under hypoxic or near-hypoxic conditions. Reported are the sensor measurements of velocities (xyz coordinates), dissolved oxygen, and pressure processed and reduced by averaging to 8 Hz by Dr. Clare E. Reimers from Oregon State University.";
    String time_coverage_end "2022-09-17T04:45:00Z";
    String time_coverage_start "2018-07-03T22:45:00Z";
    String title "[Aquatic Eddy Covariance Processed Measurements] - Processed aquatic eddy covariance measurements collected under hypoxic conditions from seven eddy covariance lander deployments made during summer cruises on the Oregon and Washington mid-shelf in 2018 and 2022 (Environmental consequences of expanded recruitment of an ecosystem engineer on a hypoxia-influenced continental shelf)";
    Float64 Westernmost_Easting -124.313;
  }
}

 

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