BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Organic Alkalinity Discrete Data] - Organic alkalinity data from estuary transects in Coastal Gulf of Maine (Pleasant, Maine; St. John, New Brunswick) in May and October of 2018 and 2019 (Collaborative Research: Organic Alkalinity: Impacts of the [OTHER] Alkalinity on Estuary and Coastal Ocean Chemistry)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_918545_v1)
Range:	longitude = -67.764 to -66.001°E, time = 2018-05-15T14:23:00Z to 2019-10-24T15:21:20Z
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

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.

Graph Type:

X Axis:

Y Axis:

Color:

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.

Graph Settings

Marker Type:

Size:

Color:

Color Bar:

Continuity:

Scale:

Minimum:

Maximum:

N Sections:

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

)

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  ID {
    String long_name "Id";
    String units "unitless";
  }
  Collection_Date {
    String long_name "Collection_date";
    String units "unitless";
  }
  Collection_Time {
    Int32 actual_range 111030, 203520;
    String long_name "Collection_time";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.52639418e+9, 1.57193048e+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 {
    Float32 actual_range 44.48, 45.941;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -67.764, -66.001;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Salinity {
    Float32 actual_range 0.0, 32.46;
    String long_name "Salinity";
    String units "unitless";
  }
  In_Situ_Water_Temperature {
    Float32 actual_range 5.12, 15.32;
    String long_name "In_situ_water_temperature";
    String units "degrees Celcius";
  }
  pHT {
    Float32 actual_range 3.976, 7.754;
    String long_name "Pht";
    String units "unitless (total scale)";
  }
  pH_Method {
    String long_name "Ph_method";
    String units "unitless";
  }
  pCO2 {
    Float32 actual_range 378.07, 1656.27;
    String long_name "Pco2";
    String units "microatmospheres";
  }
  DOC {
    Float32 actual_range 74.57, 1944.27;
    String long_name "Doc";
    String units "micromoles carbon per liter";
  }
  T_Alk {
    Float32 actual_range -92.2, 2193.8;
    String long_name "T_alk";
    String units "micromoles per kilogram";
  }
  DIC {
    Float32 actual_range 123.06, 2136.4;
    String long_name "Dic";
    String units "micromoles per kilogram";
  }
  OrgAlk_from_Endpoint_Titration {
    Float32 actual_range 3.65, 55.39;
    String long_name "Orgalk_from_endpoint_titration";
    String units "micromoles per kilogram";
  }
  OrgAlk_from_Second_Gran_Titration {
    Float32 actual_range -31.9, 110.13;
    String long_name "Orgalk_from_second_gran_titration";
    String units "micromoles per kilogram";
  }
  SiO2 {
    Float32 actual_range 0.83, 89.74;
    String long_name "Sio2";
    String units "micromoles per liter";
  }
  PO4 {
    Float32 actual_range 0.03, 4.56;
    String long_name "Po4";
    String units "micromoles per liter";
  }
  X1T {
    Float32 actual_range 6.29e-6, 2.34e-4;
    String long_name "X1t";
    String units "moles per kilogram";
  }
  K1org {
    Float32 actual_range 5.21e-8, 0.001;
    String long_name "K1org";
    String units "unitless";
  }
  X2T {
    Float32 actual_range 1.7e-13, 1.85e-4;
    String long_name "X2t";
    String units "moles per kilogram";
  }
  K2org {
    Float32 actual_range 4.91e-9, 0.001;
    String long_name "K2org";
    String units "unitless";
  }
  X3T {
    Float32 actual_range 6.64e-5, 0.00108;
    String long_name "X3t";
    String units "moles per kilogram";
  }
  K3org {
    Float32 actual_range 1.08e-9, 1.63e-8;
    String long_name "K3org";
    String units "unitless";
  }
 }
  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.918545.1";
    Float64 Easternmost_Easting -66.001;
    Float64 geospatial_lon_max -66.001;
    Float64 geospatial_lon_min -67.764;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-23T15:25:05Z (local files)
2024-09-23T15:25:05Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_918545_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/918545";
    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.";
    String sourceUrl "(local files)";
    String summary 
"Four organic alkalinity estuary transects, in May and October of 2018 and 2019, were completed in the Pleasant (Maine, USA) and St. John (New Brunswick, Canada) estuaries.  Discrete samples were collected at intervals of salinity along each estuary.  An underway measurements system was also operated during each transect (see \"Related Datasets\" section).  Discrete samples were analyzed via a number of methods described below.  Underway measurements were collected using the procedures described in Hunt et al. (2013).

Organic alkalinity is a poorly understood component of the estuarine and coastal ocean acid-base system.  This lack of understanding makes assessment of ocean acidification vulnerability and inorganic carbon dynamics more difficult.  However, the methods used to quantify organic alkalinity and its effects on the acid-base system are not standardized.  In this work we examined several approaches for the measurement of organic alkalinity, and their application to inorganic carbon dynamics.";
    String time_coverage_end "2019-10-24T15:21:20Z";
    String time_coverage_start "2018-05-15T14:23:00Z";
    String title "[Organic Alkalinity Discrete Data] - Organic alkalinity data from estuary transects in Coastal Gulf of Maine (Pleasant, Maine; St. John, New Brunswick) in May and October of 2018 and 2019 (Collaborative Research: Organic Alkalinity: Impacts of the [OTHER] Alkalinity on Estuary and Coastal Ocean Chemistry)";
    Float64 Westernmost_Easting -67.764;
  }
}

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.

ERDDAP, Version 2.22
Disclaimers | Privacy Policy | Contact