Morrison, R.; Cooper, H.; Cumming, A.; Scarlett, P. ; Thornton, J.; Winterbourn, J.B.

Eddy covariance measurements of carbon dioxide, energy and water fluxes at an organically managed grassland, Berkshire, UK, 2017 to 2019

https://doi.org/10.5285/5a93161f-0124-4650-a2c9-7e8aaea7e6bb Cite this dataset

This dataset contains time series observations of surface-atmosphere exchanges of net ecosystem carbon dioxide exchange (NEE), sensible heat (H) and latent heat (LE), and momentum (τ) measured at an area of organically managed grassland located on the Berkshire Downs, UK. Turbulent flux densities were monitored using the micrometeorological eddy covariance (EC) technique between 1st January 2017 and 31st July 2019. The dataset includes ancillary weather and soil physics observations, as well as variables describing atmospheric turbulence and the quality of the turbulent flux observations.

This work was supported by the Natural Environment Research Council award number NE/R016429/1 as part of the UK-SCAPE programme delivering National Capability.

Publication date: 2019-12-04

Format

Comma-separated values (CSV)

Spatial information

Study area
Spatial representation type: Raster
Spatial reference system: WGS 84

Temporal information

Temporal extent: 2017-01-01 to 2019-11-16

Provenance & quality

Eddy covariance (EC) and micrometeorological observations were made using an open-path eddy covariance system. Ancillary meteorological and soil physics observations were obtained from a co-located COSMOS-UK station.

Turbulent flux densities were calculated from the raw EC data using the EddyPRO® Flux Calculation Software Version 6.1.

Quality Control of EC data involved removal of statistical outliers and tests that theoretical requirements for the successful application of the EC technique were not violated significantly. Data gaps in EC data (NEE, LE, H) and the partitioning of NEE into gross ecosystem production and total ecosystem production were performed using the REddyProc Package for R (Reichstein et al., 2019).

Further details are available in the supporting documentation.