BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Houston Galveston Bay Underway Temp and Sal] - Temperature and salinity data from in situ underway sensors 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_944425_v1)
Range:	time = 2010-06-03T03:37:10Z to 2018-11-13T07:54:28Z
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 {
  DOY_UTC {
    Float32 actual_range 14.612, 345.8834;
    String long_name "Doy_utc";
    String units "unitless";
  }
  Temp {
    Float32 actual_range 8.2398, 42.7217;
    String long_name "Temp";
    String units "degrees Celcius";
  }
  Cond {
    Float32 actual_range 0.0, 34.8851;
    String long_name "Cond";
    String units "S m-1";
  }
  Sal {
    Float32 actual_range 4.0e-4, 5.8997;
    String long_name "Sal";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.27553623007e+9, 1.54209566835e+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";
  }
  TSG_ID {
    String long_name "Tsg_id";
    String units "unitless";
  }
  Source_File {
    String long_name "Source_file";
    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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.944425.1";
    String history 
"2026-09-02T12:10:42Z (local files)
2026-09-02T12:10:42Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_944425_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/944425";
    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 "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. Underway pCO2 measurements were recorded using a Shipboard Underway pCO2 Environmental Recorder (SUPER-CO2) system. CO2flux was calculated for 0.025° x 0.025° latitude increments along the transect and total CO2 flux for the Bay was estimated. Mean Bay water pCO2 was 384.2 ± 56.7 µatm. 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). CO2 flux exhibited large seasonal and spatial variability, likely primarily due to seasonality in photosynthesis and variability of freshwater inflow events.  Overall, Galveston Bay was a sink for CO2, with a mean air-sea CO2 flux of -8.3 ± 17.3 mmol m-2 d-1, and 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 time_coverage_end "2018-11-13T07:54:28Z";
    String time_coverage_start "2010-06-03T03:37:10Z";
    String title "[Houston Galveston Bay Underway Temp and Sal] - Temperature and salinity data from in situ underway sensors 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)";
  }
}

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