Dataset Listing

Calhoun CZO - Stream Water Chemistry (2014-2018)

Variables:  Sample location, Date, Flow/No flow, EC (S/m), pH, TC (mg/L), TN (mg/L), Fluoride (mg/L), Chloride (mg/L), Nitrite (mg/L), Bromide (mg/L), Sulfate (mg/L), Nitrate (mg/L), Phosphate (mg/L), Ammonium (mg/L), Alkalinity (meq/L CaCO3), Lithium(mg/L), K(mg/L), Mg(mg/L), Ca(mg/L), Mn(mg/L), Na(mg/L), Fe57(umol_l), Al(umol_l), Mn_umol_l, K_ueq_l, Mg_ueql_l, Ca_ueq_l, Na_ueq_l, Fe57_ueq_l, Al_ueq_l, Mn_ueq_l, H+, Alkalinity_CaCO3_ueq_l, F_ueq_l, Cl_ueq_l, NO2_ueq_l, Br_ueq_l, SO4_ueq_l, NO3_ueq_l, PO4_ueq_l, sum-anions, sum-cations_ICP, sum-cations_IC, error_ICP, error_IC

Standard Variables:  Alkalinity, carbonate|Aluminum|Nitrogen, NH4|Bromide|Calcium, dissolved|Chloride|Electrical conductivity|Iron|Discharge|Fluoride|Potassium, dissolved|Magnesium, dissolved|Manganese, dissolved|Sodium, dissolved|Nitrogen, nitrate (NO3)|Nitrogen, nitrite (NO2)|pH|Phosphorus, phosphate (PO4)|Recorder code|Sulfate|Carbon, total|Nitrogen, total

Date Range:  (2014-07-18 to 2018-12-12. monthly)

Dataset Creators/Authors:  Foroughi, M.; Cook, Charles W.; Heine, P.; Richter, Daniel deB.

Contact:  Maryam Foroughi, University of Georgia

Field Area:   Calhoun Experimental Forest and Eco-hydrology Experiments

Keywords & XML
  • Description

    This is water chemistry data for stream samples collected monthly from July 2014-December 2018 within the Tyger River and Enoree River watersheds, including Holcombe’s Branch, Padgett’s Creek, Isaac Creek, Johns Creek, and Sparks Creek. These grab samples were obtained by dipping new 50mL polypropylene (PP) tubes into the stream channel. Care was taken to sample upstream of any disturbance caused by entering stream channel. Three tubes were filled at each sampling location and returned to the lab for filtration and analysis. Beginning in 2015, pH and conductivity were measured directly when collecting samples. In the lab, the 3 tubes from each sampling location were composited for vacuum filtration using Whatman Nuclepore 0.4 um polycarbonate membranes. The filtered sample was divided into 3 new PP tubes and stored at 4C prior to analysis. To analyze: 1) Dispense 20mLs of sample into glass tube; 2) Allow sample to reach equilibrium with room temp; 3) Calibrate temperature correction on YSI Model 32 Conductance Meter using 0.0001N, 0.0005N, and 0.001N KCl; 4) Immerse conductivity cell into sample, and swirl to eliminate air pockets; 5) Check range and temperature correction for each sample, adjust if necessary; 6) Allow reading to stabilize, record result in uS after stable for 30 sec; 7) Remove cell, place stir bar in tube, place tube on stir plate and mix for at least 15 minutes to allow sample to reach equilibrium with atmospheric CO2; 8) After calibrating pH meter (Brinkmann Model Phi 360) on pH 4 and 7 buffers, immerse pH electrode; 9) Reading may take several minutes to stabilize; 10) Record pH when change in value is less than 0.02 units on successive readings; 11) While continuously stirring, place titrator (Metrohm Model 665 Dosimat) dispensing tip in tube; 12) End of tip should align with bulb of electrode without touching; 13) Dispense titrant (0.005N HCl) until pH 5.00, 4.5, and 4.2 are reached; 14) Record volume when endpoint is stable for 15 sec; 15) Convert volume to meq/L alkalinity. 16) Measure Anions and cations of filtered samples by ion chromatography (IC) and inductively coupled mass spectrometry (ICP). 17) Measure TOC/TN by TOC-V CSH/CSN (Shimadzu).
  • Keywords

    stream water chemistry, conductivity, pH, alkalinity,

    XML Metadata

    XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.

  • Citation for This Webpage

    Foroughi, M.; Cook, Charles W.; Heine, P.; Richter, Daniel deB. (2018). "CZO Dataset: Calhoun CZO - Stream Water Chemistry (2014-2018)." Retrieved 07 Dec 2019, from


Calhoun CZO - Stream Water pH & Alkalinity 2014-2015

(xlsx)   Data Level 1

Calhoun CZO - Stream Water Chemistry 2014-2017

(xlsx)   Data Level 1

Data Use Policy
Data Sharing Policy
  • Data Use Policy

    DRAFT v.0.4.0

    1. Use our data freely. All CZO Data Products* except those labelled Private** are released to the public and may be freely copied, distributed, edited, remixed, and built upon under the condition that you give acknowledgement as described below. Non-CZO data products — like those produced by USGS or NOAA — have their own use policies, which should be followed.

    2. Give proper citation and acknowledgement. Publications, models and data products that make use of these datasets must include proper citation and acknowledgement. Most importantly, provide a citation in a similar way as a journal article (i.e. author, title, year of publication, name of CZO “publisher”, edition or version, and URL or DOI access information. See Also include at least a brief acknowledgement such as: “Data were provided by the NSF-supported Southern Sierra Critical Zone Observatory” (replace with the appropriate observatory name).

    3. Let us know how you will use the data. The dataset creators would appreciate hearing of any plans to use the dataset. Consider consultation or collaboration with dataset creators.

    *CZO Data Products.  Defined as a data collected with any monetary or logistical support from a CZO.

    **Private. Most private data will be released to the public within 1-2 years, with some exceptionally challenging datasets up to 4 years. To inquire about potential earlier use, please contact us.

  • Data Sharing Policy

    DRAFT v.0.2.5

    All CZO investigators and collaborators who receive material or logistical support from a CZO agree to:

    1. Share data privately within 1 year. CZO investigators and collaborators agree to provide CZO Data Products* — including data files and metadata for raw, quality controlled and/or derived data — to CZO data managers within one year of collection of samples, in situ or experimental data. By default, data values will be held in a Private CZO Repository**, but metadata will be made public and will provide full attribution to the Dataset Creators†.

    2. Release data to public within 2 years. CZO Dataset Creators will be encouraged after one year to release data for public access. Dataset Creators may chose to publish or release data sooner.

    3. Request, in writing, data privacy up to 4 years. CZO PIs will review short written applications to extend data privacy beyond 2 years and up to 4 years from time of collection. Extensions beyond 3 years should not be the norm, and will be granted only for compelling cases.

    4. Consult with creators of private CZO datasets prior to use. In order to enable the collaborative vision of the CZO program, data in private CZO repositories will be available to other investigators and collaborators within that CZO. Releasing or publishing any derivative of such private data without explicit consent from the dataset creators will be considered a serious scientific ethics violation.

    * CZO Data Products. Defined as data collected with any monetary or logistical support from a CZO. Logistical support includes the use of any CZO sensors, sampling infrastructure, equipment, vehicles, or labor from a supported investigator, student or staff person. CZO Data Products can acknowledge multiple additional sources of support.

    ** Private CZO Repository. Defined as a password-protected directory on each CZO’s data server. Files will be accessible by all investigators and collaborators within the given CZO and logins will be maintained by that local CZO’s data managers. Although data values will not be accessible by the public or ingested into any central data system (i.e. CUAHSI HIS), metadata will be fully discoverable by the public. This provides the dual benefit of giving attribution and credit to dataset creators and the CZO in general, while maintaining protection of intellectual property while publications are pending.

    † Dataset Creators. Defined as the people who are responsible for designing, collecting, analyzing and providing quality assurance for a dataset. The creators of a dataset are analogous to the authors of a publication, and datasets should be cited in an analogous manner following the emerging international guidelines described at

Explore Further

data |

Explore Further