This dataset contains eddy-covariance measurements in the ablation period of 2014-2016. Measurements were taken from two turbulence towers over a long-lasting snow patch, which are 5 m apart from each other (2014 and 2015). The turbulence towers were equipped with two YOUNG ultrasonic anemometers mounted 0.7 m (in 2014) and 3.3 m (in 2015) above snow-free ground, two ultrasonic anemometers (CSAT3, Campbell Scientific, Inc.) mounted at 2.6 m (in 2014) and 2.2 m (in 2015) above snow-free ground and one anemometer (DA-600, Kaijo Denki) mounted at 0.3 m above snow surface.
The measurement setup changed in 2016 and includes a measurement above the snow-free ground in upwind direction (Swiss coordinates: 790191/176689). The measurement tower is equipped with one ultrasonic anemometer (CSAT3, Campbell Scientific, Inc.) in 3.3 m above the snow-free ground. Additionally, one measurement tower is installed above the long-Lasting snow patch and equipped with the same setup as 2015.
Turbulence data were sampled at a frequency of 20 Hz. The processing of the data to quality controlled fluxes has been done with the Biomicrometeorology flux software (Thomas et al., 2009). The program applies plausibility tests and a despiking test after Vickers and Mahrt (1997) on the measured data. The routine further applies a time-lag correction and considers the deployment (e.g. the sonic azimuth). A frequency response correction (Moore, 1986) is done and a three-dimensional rotation is performed. Finally, quality assurance/quality control (QA/QC) flags after Foken et al., (2004) are issued and fast Fourier transform power and co-spectra are calculated. The change in snow height is considered in the post-processing for every measurement day. The turbulence data were averaged to 30 minute intervals.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.