BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Houston Galveston Bay Carbonate] - Carbonate chemistry data from water samples collected aboard the R/V Trident in Galveston Bay, Northwestern Gulf of Mexico from October 2017 to September 2018 (RAPID: Capturing the Signature of Hurricane Harvey on Texas Coastal Lagoons)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_943994_v1)
Range:	longitude = -94.931 to -94.752°E, latitude = 29.358 to 29.61°N, depth = 0.1 to 5.0m
Information:	Summary \| License \| FGDC \| ISO 19115 \| 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:

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:

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 {
  Station {
    Int32 actual_range 1, 5;
    String long_name "Station";
    String units "unitless";
  }
  Sample {
    String long_name "Sample";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 29.358, 29.61;
    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 -94.931, -94.752;
    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 0.1, 5.0;
    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 8.01, 30.93;
    String long_name "Temp";
    String units "decrees Celsius";
  }
  Sonde_Salinity {
    Float32 actual_range 1.97, 35.08;
    String long_name "Sonde_salinity";
    String units "unitless";
  }
  DO_percentage {
    Float32 actual_range 57.0, 122.9;
    String long_name "Do_percentage";
    String units "unitless";
  }
  DO {
    Float32 actual_range 3.69, 23.95;
    String long_name "Do";
    String units "milligrams per liter";
  }
  DIC {
    Float32 actual_range 1482.9, 2147.0;
    String long_name "Dic";
    String units "micromol per kg";
  }
  Alkalinity {
    Float32 actual_range 1512.4, 2383.3;
    String long_name "Alkalinity";
    String units "micromol per kg";
  }
  pH_Spec {
    Float32 actual_range 7.642, 8.461;
    String long_name "Ph_spec";
    String units "unitless";
  }
  Lab_Salinity {
    Float32 actual_range 1.96, 34.59;
    String long_name "Lab_salinity";
    String units "unitless";
  }
  Calcium {
    Float32 actual_range 3.77, 9.64;
    String long_name "Calcium";
    String units "micromol per kg";
  }
  Aragonite_saturation_state_CO2SYS {
    Float32 actual_range 0.43, 4.12;
    String long_name "Aragonite_saturation_state_co2sys";
    String units "unitless";
  }
  Corrected_aragonite_saturation_state {
    Float32 actual_range 0.58, 4.41;
    String long_name "Corrected_aragonite_saturation_state";
    String units "unitless";
  }
  pCO2 {
    Float32 actual_range 100.6, 999.6;
    String long_name "Pco2";
    String units "microatm";
  }
  pH_at_in_situ_Temp {
    Float32 actual_range 7.714, 8.596;
    String long_name "Ph_at_in_situ_temp";
    String units "unitless";
  }
  Notes {
    String long_name "Notes";
    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.943994.1";
    Float64 Easternmost_Easting -94.752;
    Float64 geospatial_lat_max 29.61;
    Float64 geospatial_lat_min 29.358;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -94.752;
    Float64 geospatial_lon_min -94.931;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 5.0;
    Float64 geospatial_vertical_min 0.1;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-09-02T12:10:42Z (local files)
2026-09-02T12:10:42Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_943994_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/943994";
    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 29.61;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 29.358;
    String summary "Quantifying the direction and magnitude of CO2 flux in estuaries is necessary to constrain the global carbon cycle, yet carbonate systems and CO2 flux in subtropical and urbanized estuaries are not yet fully determined. To estimate the CO2 flux for Galveston Bay, a subtropical estuary located in the northwestern Gulf of Mexico proximal to the Houston-Galveston metroplex, monthly cruises were conducted along a transect extending from the Houston ship channel to the mouth of Galveston Bay and Gulf of Mexico from October 2017 to September 2018.  On these cruises, discrete water samples were collected for laboratory analyses of total alkalinity (TA), total dissolved inorganic carbon (DIC), and pH, and aragonite saturation state (ΩAr) was calculated. Mean Bay water TA was 2062.0 ± 213.2 µmol kg-1, DIC was 1863.7 ± 160.9 µmol kg-1, pH was 8.09 ± 0.17, and ΩAr was 2.43 ± 0.96. When compared to theoretical river-ocean mixing scenarios, TA values fell above the mixing line in winter and summer, indicating production, while DIC values displayed more spatial variability that included both production and consumption in different seasons.  A large freshwater inflow event in spring was followed by a period of dilution (low salinity, TA, and DIC) and enhanced primary production (low pCO2, water, CO2 uptake, and high chlorophyll-a levels). Carbonate chemistry in Galveston Bay was regulated by an interaction between hydrology and biogeochemistry. The carbonate chemistry and CO2 uptake patterns of Galveston Bay differ from those that are common in temperate estuaries, which reiterates the need for further research in subtropical estuaries.";
    String title "[Houston Galveston Bay Carbonate] - Carbonate chemistry data from water samples collected aboard the R/V Trident in Galveston Bay, Northwestern Gulf of Mexico from October 2017 to September 2018 (RAPID: Capturing the Signature of Hurricane Harvey on Texas Coastal Lagoons)";
    Float64 Westernmost_Easting -94.931;
  }
}

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