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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Bacterivory] - Specific daily growth of heterotrophic bacteria and grazing
mortality on bacteria by microzooplankton from R/V Roger Revelle KIWI6, KIWI7,
KIWI8, KIWI9 cruises in the Southern Ocean, 1997-1998 (U.S. JGOFS AESOPS
project) (U.S. JGOFS Antarctic Environment and Southern Ocean Process Study)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_943333_v1)
Range: longitude = -174.73 to -165.92°E, latitude = -70.4 to -52.97°N, depth = 7.0 to 55.0m
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 {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  Event {
    Int32 actual_range 1170226, 12260200;
    String long_name "Event";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -70.4, -52.97;
    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 -174.73, -165.92;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Station {
    Int32 actual_range 1, 23;
    String long_name "Station";
    String units "unitless";
  }
  Cast {
    Int32 actual_range 1, 6;
    String long_name "Cast";
    String units "unitless";
  }
  Cast_type {
    String long_name "Cast_type";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 7, 55;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Bact_growth {
    Float32 actual_range 0.025, 0.991;
    String long_name "Bact_growth";
    String units "per day (d-1)";
  }
  Microzoo_graz {
    Float32 actual_range 0.0, 0.826;
    String long_name "Microzoo_graz";
    String units "per day (d-1)";
  }
 }
  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.943333.1";
    Float64 Easternmost_Easting -165.92;
    Float64 geospatial_lat_max -52.97;
    Float64 geospatial_lat_min -70.4;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -165.92;
    Float64 geospatial_lon_min -174.73;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 55.0;
    Float64 geospatial_vertical_min 7.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-16T08:50:15Z (local files)
2024-11-16T08:50:15Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_943333_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/943333";
    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 -52.97;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -70.4;
    String summary "This dataset is from dilution experiments conducted on 1997-98 cruises KIWI6, KIWI7, KIWI8, and KIWI9 on R/V Roger Revelle as part of the US JGOFS AESOPS Program in the Southern Ocean. Rate estimates are specific daily growth of heterotrophic bacteria (d-1) and grazing mortality on bacteria by microzooplankton (d-1).";
    String title "[Bacterivory] - Specific daily growth of heterotrophic bacteria and grazing mortality on bacteria by microzooplankton from R/V Roger Revelle KIWI6, KIWI7, KIWI8, KIWI9 cruises in the Southern Ocean, 1997-1998 (U.S. JGOFS AESOPS project) (U.S. JGOFS Antarctic Environment and Southern Ocean Process Study)";
    Float64 Westernmost_Easting -174.73;
  }
}

 

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