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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [California sediment porosity data] - Sediment porosity collected from R/V
Oceanus cruise OC1906A and R/V Sikuliaq cruise SKQ202016S off the coast of
California in 2019 and 2020 (Collaborative Research: Peptide Deamination as a
Source of Refractory Dissolved Organic Matter in Marine Sediments)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_959217_v1)
Range: longitude = -122.1861 to -118.6°E, latitude = 33.3005 to 36.1126°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 {
  Ship {
    String long_name "Ship";
    String units "unitless";
  }
  Cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  St_ID {
    String long_name "St_id";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 33.3005, 36.1126;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Station_latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -122.1861, -118.6;
    String axis "X";
    String ioos_category "Location";
    String long_name "Station_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Sa_ID {
    String long_name "Sa_id";
    String units "unitless";
  }
  Core {
    String long_name "Core";
    String units "unitless";
  }
  samp {
    String long_name "Samp";
    String units "unitless";
  }
  Depth {
    Float32 actual_range 0.5, 291.9;
    String long_name "Depth";
    String units "centimeters (cm)";
  }
  Err {
    Float32 actual_range 0.5, 31.0;
    String long_name "Err";
    String units "centimeters (cm)";
  }
  Porosity {
    Float32 actual_range 0.0, 0.912;
    String long_name "Porosity";
    String units "cubic centimeters of porewater per cubic centimeters of total sediment (cm3pore water/cm3­total sediment)";
  }
 }
  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.959217.1";
    Float64 Easternmost_Easting -118.6;
    Float64 geospatial_lat_max 36.1126;
    Float64 geospatial_lat_min 33.3005;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -118.6;
    Float64 geospatial_lon_min -122.1861;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-11T04:37:48Z (local files)
2025-05-11T04:37:48Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_959217_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/959217";
    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 36.1126;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 33.3005;
    String summary "Sediment porosity was determined in cores collected at several stations off the coast of California: at a site in Catalina Basin ('Cat'; latitude: 33.301, longitude: -118.6; water depth, 1310 m); sites K and D off the coast of central California south of Monterey Bay ('K'; latitude: 35.375, longitude: -121.501; water depth, 1000 m; 'D'; latitude: 36.113, longitude: -122.186; water depth, 1440 m). The Cat cores were collected in June 2019, while the site K and D cores were collected in December 2020. Sediment cores were sectioned on-board the ship, and wet sediment was placed in pre-weighed scintillation vials. The vials were frozen and returned to the shore-based lab at Old Dominon University (ODU) where the samples were dried to constant weight and wet-to-dry sediment ratios were converted to porosity values. These samples were collected as part of a larger project examining deaminated peptides and organic matter cycling in the sediments at these sites.";
    String title "[California sediment porosity data] - Sediment porosity collected from R/V Oceanus cruise OC1906A and R/V Sikuliaq cruise SKQ202016S off the coast of California in 2019 and 2020 (Collaborative Research: Peptide Deamination as a Source of Refractory Dissolved Organic Matter in Marine Sediments)";
    Float64 Westernmost_Easting -122.1861;
  }
}

 

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