The motion of trees in the wind - a collection of multiple data sets

The tree motion data in this repository were collected from multiple sites with different sensors. There are two types of data: (a) 1-hour sample data from 27 sites (/one_hour_samples/*.csv). Each file represents a single tree and contains two columns representing the two horizontal axes of tree motion. These data are uncalibrated and do not have a time-stamp. File names refer to: OwnersInitials_Site_treeID_resolution_SensorType for example TJ_MY_7_4Hz_Strain These filenames match the first column in the 'TreeSummary.csv' table (b) long-term data from 9 data sets (/site_name.zip/) The wind and tree data are stored in separate files for each day of data, labelled with site name, tree ID or wind, year, month, day. For example Kershope_T25_1990_5_23 In each file, the first column is the time and date in format YYYY-MM-DD HH:mm:ss.SSS The following columns are tree motion data or wind data with units in the variable names. Some of the data were calibrated by pulling the tree with a known force, in these cases calibration coefficients are given in the 'TreeSummary' table Wind data for the Australian data set is stored in the folder with data for each tree, because the trees were not close together enough to share a wind measurement. The data for Orange, Storrs and Torrington were collected with inclinometers. The data for all trees is stored together in each daily file. The long-term tree motion data have not been pre-processed because user choices affect the results. Importantly, you will need to remove a varying offset (caused by sensor drift) from the tree motion data. See discussion in the accompanying publication and references therein.

Saved in:
Bibliographic Details
Main Authors: Jackson, Toby, Bunce, Amanda, James, Ken, Wellpott, Axel, Van Bloem, Skip, Achim, Alexis, Gardiner, Barry, Dellwick, Ebba, Angelou, Nikolas, van Emmerik, Tim, Duperat, Marine, Ruel, Jean-Claude, Kane, Brian, Ciruzzi, Dominick, Loheide II, Steven, Burcham, Daniel, Schindler, Dirk, Kolbe, Sven, Wiegmann, Kilian, Rudnicki, Mark, Lieffers, Victor, Selker, John, Gougherty, Andrew, Miesbauer, Jason, Samelson, Roger, Wagner, Jim, Ambrose, Anthony, Detter, Andreas, Rust, Steffen
Format: Dataset biblioteca
Published: University of Cambridge
Subjects:accelerometer, forest ecology, hydrology, inclinometer, risk management, strain gauge, tree motion, wind damage,
Online Access:https://research.wur.nl/en/datasets/the-motion-of-trees-in-the-wind-a-collection-of-multiple-data-set
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The tree motion data in this repository were collected from multiple sites with different sensors. There are two types of data: (a) 1-hour sample data from 27 sites (/one_hour_samples/*.csv). Each file represents a single tree and contains two columns representing the two horizontal axes of tree motion. These data are uncalibrated and do not have a time-stamp. File names refer to: OwnersInitials_Site_treeID_resolution_SensorType for example TJ_MY_7_4Hz_Strain These filenames match the first column in the 'TreeSummary.csv' table (b) long-term data from 9 data sets (/site_name.zip/) The wind and tree data are stored in separate files for each day of data, labelled with site name, tree ID or wind, year, month, day. For example Kershope_T25_1990_5_23 In each file, the first column is the time and date in format YYYY-MM-DD HH:mm:ss.SSS The following columns are tree motion data or wind data with units in the variable names. Some of the data were calibrated by pulling the tree with a known force, in these cases calibration coefficients are given in the 'TreeSummary' table Wind data for the Australian data set is stored in the folder with data for each tree, because the trees were not close together enough to share a wind measurement. The data for Orange, Storrs and Torrington were collected with inclinometers. The data for all trees is stored together in each daily file. The long-term tree motion data have not been pre-processed because user choices affect the results. Importantly, you will need to remove a varying offset (caused by sensor drift) from the tree motion data. See discussion in the accompanying publication and references therein.