ERDDAP > tabledap > Data Access Form

Dataset Title:	[Dissolved organic carbon lability] - Water column dissolved organic carbon (DOC) reactivity along the York River Estuary (YRE) from surface samples collected in October 2018 and February, April, and July 2019 (Alteration of carbon fluxes by intense phytoplankton blooms in a microtidal estuary)
Institution:	BCO-DMO   (Dataset ID: bcodmo_dataset_946056_v1)
Information:	Summary | License | FGDC | ISO 19115 | Metadata | Background | Files | Make a graph

 

Variable	Optional Constraint #1		Optional Constraint #2		Minimum	Maximum
Site (unitless)	!= =~ <= >= = < >		!= =~ <= >= = < >		"Lower"	"Upper"
latitude (degrees_north)	!= =~ <= >= = < >		!= =~ <= >= = < >		37.2518	37.48011
longitude (Long, degrees_east)	!= =~ <= >= = < >		!= =~ <= >= = < >		-76.7595	-76.44289
Month_Collected (unitless)	!= =~ <= >= = < >		!= =~ <= >= = < >		"April"	"October"
Date_Sampled (unitless)	!= =~ <= >= = < >		!= =~ <= >= = < >		"2018-10-10"	"2019-08-13"
Timepoint_days (days)	!= =~ <= >= = < >		!= =~ <= >= = < >		0	28
DOC_uM (micromolar (umol/l))	!= =~ <= >= = < >		!= =~ <= >= = < >		129.7	882.7

 

Server-side Functions

distinct()

orderBy orderByDescending orderByClosest orderByCount orderByLimit orderByMax orderByMin orderByMinMax orderByMean orderBySum (" Site latitude longitude Month_Collected Date_Sampled Timepoint_days DOC_uM Site latitude longitude Month_Collected Date_Sampled Timepoint_days DOC_uM Site latitude longitude Month_Collected Date_Sampled Timepoint_days DOC_uM Site latitude longitude Month_Collected Date_Sampled Timepoint_days DOC_uM Site latitude longitude Month_Collected Date_Sampled Timepoint_days DOC_uM ")

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .dataTable - A JSON file formatted for use with the Google Visualization client library (Google Charts). .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriCsv - Download a ISO_8859_1 .csv file for ESRI's ArcGIS 9.x and below (separate date and time columns). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .geoJson - Download longitude,latitude,otherColumns data as a UTF-8 GeoJSON .json file. .graph - View a Make A Graph web page. .help - View a web page with a description of tabledap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each response column becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a flat, table-like, NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncCF - Download a NetCDF-3 CF Discrete Sampling Geometries file (Contiguous Ragged Array). .ncCFHeader - View the UTF-8 header (the metadata) for the .ncCF file. .ncCFMA - Download a NetCDF-3 CF Discrete Sampling Geometries file (Multidimensional Array). .ncCFMAHeader - View the UTF-8 header (the metadata) for the .ncCFMA file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download longitude,latitude,time,otherColumns as an ISO-8859-1 ODV Generic Spreadsheet File (.txt). .subset - View an HTML form which uses faceted search to simplify picking subsets of the data. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .kml - View a .kml file, suitable for Google Earth. .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form )
 
Submit (Please be patient. It may take a while to get the data.)

 

---

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Site {
    String long_name "Site";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 37.2518, 37.48011;
    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 -76.7595, -76.44289;
    String axis "X";
    String ioos_category "Location";
    String long_name "Long";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Month_Collected {
    String long_name "Month_collected";
    String units "unitless";
  }
  Date_Sampled {
    String long_name "Date_sampled";
    String units "unitless";
  }
  Timepoint_days {
    Int32 actual_range 0, 28;
    String long_name "Timepoint_days";
    String units "days";
  }
  DOC_uM {
    Float32 actual_range 129.7, 882.7;
    String long_name "Doc_um";
    String units "micromolar (umol/l)";
  }
 }
  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.946056.1";
    Float64 Easternmost_Easting -76.44289;
    Float64 geospatial_lat_max 37.48011;
    Float64 geospatial_lat_min 37.2518;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -76.44289;
    Float64 geospatial_lon_min -76.7595;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-08-15T19:24:04Z (local files)
2025-08-15T19:24:04Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_946056_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/946056";
    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 37.48011;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 37.2518;
    String summary "Data were collected to evaluate spatiotemporal variations in, and environmental controls on, water column dissolved organic carbon (DOC) reactivity along the York River Estuary (YRE), a temperate microtidal sub-estuary of the Chesapeake Bay in southeastern Virginia. Data were also collected as part of the larger, NSF-funded project (NSF BIO-OCE #1737258) entitled \"Alteration of carbon fluxes by intense phytoplankton blooms in a micro tidal estuary.\" Surface water column samples were collected in October 2018 and February, April, and July 2019 from three locations along the YRE estuarine salinity gradient. Filtered water was inoculated and incubated in the dark at in situ York River water temperatures, and sub-sampled at the onset of the experiment (T0), one day following onset (T1), and weekly for 28 days thereafter (T7, T14, T21, T28). Samples were analyzed for DOC concentrations.";
    String title "[Dissolved organic carbon lability] - Water column dissolved organic carbon (DOC) reactivity along the York River Estuary (YRE) from surface samples collected in October 2018 and February, April, and July 2019 (Alteration of carbon fluxes by intense phytoplankton blooms in a microtidal estuary)";
    Float64 Westernmost_Easting -76.7595;
  }
}

 

---

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 Data Access Protocol (DAP) and its selection constraints.

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