Dataset Listing

El Verde Instrumented hillslope - Soil Biogeochemistry - Iron and carbon cycling (2016)

Hot spots and hot moments of soil moisture explain fluctuations in iron and carbon cycling in a humid tropical forest soil

Variables:  silicon, aluminium, iron, calcium, magnesium, sodium, potassium, titanium, manganese, barium, cerium, chromium, caesium, dysprosium, Erbium, europium, gallium, gadolinium, hafnium, holmium, lanthanum, Lutetium, niobium, neodymium, praseodymium, rubidium, samarium, tin, strontium, tantalum, terbium, thorium, thulium, uranium, vanadium, tungsten, yttrium, Ytterbium, zirconium, ferric ion, ferrous ion

Standard Variables:  Silicon|Aluminum|Iron|Calcium|Magnesium|Sodium, dissolved|Potassium, dissolved|Titanium|Manganese|Barium, dissolved|Cerium|Chromium, total|Rare-earth elements|Niobium, total|Rubidium|Strontium, dissolved|Zirconium

Date Range:  (2016-2016)

Dataset Creators/Authors:  Diego Barcellos; Christine S. O'Connell; Whendee Silver; Christof Meile; Aaron Thompson

Contact:  Miguel Leon, Miguel.Leon@unh.edu

Field Area:   El Verde Field Station

Description
Keywords & XML
Citation
Publications
  • Description

    Soils from humid forests undergo spatial and temporal variations in moisture and oxygen (O2) in response to rainfall, and induce changes in iron (Fe) and carbon (C) biogeochemistry. We hypothesized that high rainfall periods stimulate Fe and C cycling, with the greatest effects in areas of high soil moisture. To test this, we measured Fe and C cycling across three catenas at valley, slope, and ridge positions every two days for a two-month period in a rainforest in Puerto Rico. Over 12 days without rain, soil moisture, FeII, rapidly reducible Fe oxides (FeIIIRR), and dissolved organic C (DOC) declined, but Eh and O2 increased; conversely, during a 10-day period of intense rain (290 mm), we observed the opposite trends. Mixed-effects models suggest precipitation predicted soil moisture, soil redox potential (Eh), and O2, which in turn influenced Fe reduction/oxidation, C dissolution, and mineralization processes. The approximate turnover time for HCl-extractable FeII was four days for both production and consumption, and may be driven by fluctuations in FeIIIRR, which ranged from 42% to 100% of citrate–ascorbate-extractable FeIII (short-range order (SRO)-FeIII) at a given site. Our results demonstrated that periods of high precipitation (hot moments) influenced Fe and C-cycling within day-to-week timescales, and were more pronounced in humid valleys (hot spots).
  • Keywords

    iron reduction; dissolved organic carbon; soil moisture; redox processes

    XML Metadata

    criticalzone.org/luquillo/data/xml-metadata-test/7164/

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

  • Citation for This Dataset

    Diego Barcellos, Christine S. O’Connell, Whendee Silver, Christof Meile, Aaron Thompson. LCZO - Soil Biogeochemistry - Iron and Carbon cycling - El Verde (2016). https://doi.org/10.3390/soilsystems2040059

    Citation for This Webpage

    Diego Barcellos; Christine S. O'Connell; Whendee Silver; Christof Meile; Aaron Thompson (2016). "CZO Dataset: El Verde Instrumented hillslope - Soil Biogeochemistry (2016) - Iron and carbon cycling." Retrieved 19 Oct 2019, from http://criticalzone.org/luquillo/data/dataset/7164/

  • Publications

    Primary Publications

    2018

    Hot Spots and Hot Moments of Soil Moisture Explain Fluctuations in Iron and Carbon Cycling in a Humid Tropical Forest Soil . Diego Barcellos, Christine S. O’Connell, Whendee Silver, Christof Meile, Aaron Thompson (2018): Soil Systems

Data

El Verde Instrumented hillslope - Iron and carbon cycling

(nt=1)   Data Level 2

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 http://www.datacite.org/whycitedata). 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 http://www.datacite.org/whycitedata.

Explore Further

data |

Explore Further