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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Depth profiles of lipid biomarkers KM1314] - Depth profiles of lipid
biomarkers from R/V Kilo Moana KM1314 in the North Pacific Ocean (Seattle to
Honolulu, Line P, Station ALOHA), Aug-Sept 2013 (Significance of nitrification
in shaping planktonic biodiversity in the ocean) Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_997800_v1)
Range: longitude = -150.0 to -134.6803°E, latitude = 30.0 to 50.0°N, depth = 0.0 to 300.0m, time = 2013-08-14T13:05:19Z to 2013-08-29T14:50:20Z
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.376485519e+9, 1.37778782e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime_of_sampling";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 30.0, 50.0;
    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 -150.0, -134.6803;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Station_ID {
    Int32 actual_range 5, 13;
    String long_name "Station_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 0, 300;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth_m";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  insitu_T_degC {
    Float32 actual_range 3.78, 26.24;
    String long_name "Insitu_t_degc";
    String units "degrees Celsius (°C)";
  }
  TEX86_derived_temperature_degC {
    Float32 actual_range -2.27, 29.81;
    String long_name "Tex86_derived_temperature_degc";
    String units "degrees Celsius (°C)";
  }
  Isoprenoid_ng_per_L {
    Float32 actual_range 0.11, 630.42;
    String long_name "Isoprenoid_ng_per_l";
    String units "nano gram per liter (ng/L)";
  }
 }
  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.997800.1";
    Float64 Easternmost_Easting -134.6803;
    Float64 geospatial_lat_max 50.0;
    Float64 geospatial_lat_min 30.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -134.6803;
    Float64 geospatial_lon_min -150.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 300.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-07-24T07:37:29Z (local files)
2026-07-24T07:37:29Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_997800_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/997800";
    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 50.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 30.0;
    String summary "This dataset contains in situ temperature (°C), TEX86-derived temperature (°C), and isoprenoid concentrations (ng L−1) measured from 0 to 300 m depth at Stations 5, 8, and 13 in the Northeastern Pacific Ocean during the R/V Kilo Moana cruise KM1314 in August 2013. Samples were collected to characterize vertical variations in archaeal lipid biomarkers and evaluate the relationship between TEX86 paleotemperature estimates and ambient water column temperature. In situ temperatures were obtained from CTD measurements, TEX86 values were calculated from the relative abundances of GDGT-1, GDGT-2, GDGT-3, and the crenarchaeol regioisomer, and TEX86-derived temperatures were reconstructed using a published calibration equation. These data were generated to assess how environmental gradients influence archaeal lipid distributions and the accuracy of TEX86 temperature reconstructions in the upper ocean.";
    String time_coverage_end "2013-08-29T14:50:20Z";
    String time_coverage_start "2013-08-14T13:05:19Z";
    String title "[Depth profiles of lipid biomarkers KM1314] - Depth profiles of lipid biomarkers from R/V Kilo Moana KM1314 in the North Pacific Ocean (Seattle to Honolulu, Line P, Station ALOHA), Aug-Sept 2013 (Significance of nitrification in shaping planktonic biodiversity in the ocean)";
    Float64 Westernmost_Easting -150.0;
  }
}

 

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