Data Access Form

Dataset Title:	[AUV_MontereyBay_Makai_CTD] - Autonomous Underwater Vehicle Monterey Bay Time Series - AUV Makai CTD (Center for Microbial Oceanography: Research and Education)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_644012_v1)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Files \| Make a graph

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable	Minimum	Maximum
time (Iso_datetime_utc, UTC)	2016-02-03T08:52:57Z	2016-02-04T21:26:10Z

latitude (degrees_north)	36.78374	36.83383

longitude (degrees_east)	-121.8878	-121.8284

depth (m)	1.001	33.414

temp (degrees Celsius)	11.989	13.71
sal (dimensionless)	32.269	33.665
chl_a_fluor (micrograms/liter)	0.3927	3.5705

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

File type: (more information)

(Documentation / Bypass this form )

(Please be patient. It may take a while to get the data.)

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.454489577e+9, 1.45462117e+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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 36.78374, 36.83383;
    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 -121.8878, -121.8284;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.001, 33.414;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  temp {
    Float32 actual_range 11.989, 13.71;
    String long_name "Temp";
    String units "degrees Celsius";
  }
  sal {
    Float32 actual_range 32.269, 33.665;
    String long_name "Sal";
    String units "dimensionless";
  }
  chl_a_fluor {
    Float32 actual_range 0.3927, 3.5705;
    String long_name "Chl_a_fluor";
    String units "micrograms/liter";
  }
 }
  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.644012.1";
    Float64 Easternmost_Easting -121.8284;
    Float64 geospatial_lat_max 36.83383;
    Float64 geospatial_lat_min 36.78374;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -121.8284;
    Float64 geospatial_lon_min -121.8878;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 33.414;
    Float64 geospatial_vertical_min 1.001;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-23T17:24:13Z (local files)
2024-11-23T17:24:13Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_644012_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/644012";
    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.83383;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 36.78374;
    String summary "Autonomous Underwater Vehicle Monterey Bay Time Series - AUV Makai CTD";
    String time_coverage_end "2016-02-04T21:26:10Z";
    String time_coverage_start "2016-02-03T08:52:57Z";
    String title "[AUV_MontereyBay_Makai_CTD] - Autonomous Underwater Vehicle Monterey Bay Time Series - AUV Makai CTD (Center for Microbial Oceanography: Research and Education)";
    Float64 Westernmost_Easting -121.8878;
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.