Turbulence Dataset

This record provides the datasets used in the study**“Proposal of a Laplace Turbulence Index Based on the Non-Gaussianity of Temporal Wind Velocity Increments.”** The archive contains synchronized wind measurements from:- **Drone-mounted ultrasonic anemometer (TriSonica)**: short segments used for the temporal increment analysis.- **Pole-mounted ultrasonic anemometer (ULSA PRO, 10 Hz)**: fixed reference measurements and selected segments corresponding to drone operations. Folder overview- `raw/drone_Trisonica/` Drone wind data (CSV). Main analysis segments correspond to hovering/near-collocated measurements.- `raw/pole_ULSA_PRO/ULSA_PRO_10hz_20251207_20251218/` Continuous pole wind time series at 10 Hz (daily CSV files).- `raw/pole_ULSA_PRO/ULSA_PRO_10hz_select/` Pole wind segments (CSV) extracted to match the drone operation periods used in the paper.- `raw/drone_flight/` DJI flight logs exported from Airdata (CSV) for flight context (time, altitude, etc.).- `raw/drone_kml/` KML flight tracks exported from Airdata (for visualization). Reference-only data (not used in the paper)The following folders are provided for transparency and future work; they are **not** analyzed nor reported in the associated manuscript:- `raw/drone_Trisonica/climb_high/`- `raw/drone_Trisonica/land_besideULSAPRO/`- `raw/drone_flight/`- `raw/drone_kml/` Sensors and sampling ### Drone wind (TriSonica) - Format: CSV, 10 Hz (typical) - Key fields: wind speed/direction and 3D wind components (U,V,W), plus temperature, humidity, pressure and attitude/heading fields. ### Pole wind (ULSA PRO) - Format: CSV, 10 Hz (daily files + selected segments) - Key fields: wind direction, wind speed magnitude, headwind component, sonic/virtual temperature, validity flag. ### Flight context (Airdata) - Format: CSV (~5 Hz typical) - Includes GPS position, altitude/height fields, battery and RC inputs, and attitude/heading. ## Time fields Different files use different time conventions: - **TriSonica** (`raw/drone_Trisonica/*.csv`) - `timestamp` is a string like `YYYY-MM-DD HH:MM:SS.sss` - Time zone is not explicitly encoded; in this campaign the file naming follows local time (JST). - **ULSA PRO 10 Hz** (`wind_YYYY-MM-DD.csv`, `pole_*.csv`) - `ts` is `YYYY-MM-DD HH:MM:SS.sss` - Time zone is not explicitly encoded; file naming follows local time (JST). - **ULSA PRO 1 Hz long-term file** - `_time` is ISO 8601 with trailing `Z` (UTC), e.g. `2025-01-13T00:51:02Z`. - **Airdata** - `datetime(utc)` is UTC. - `time(millisecond)` is elapsed time from the start of the log. For synchronization across sources, using `datetime(utc)` (Airdata) and converting other sources to UTC is recommended. Variables A machine-readable dictionary is provided in: - `data_dictionary.csv` It lists each column, unit, and a short description for: - TriSonica wind files - ULSA PRO wind files (10 Hz and 1 Hz) - Airdata flight logs Notes / known quirks - The ULSA PRO 1 Hz file may contain duplicate timestamps (e.g., two rows with the same `_time`). Users may wish to de-duplicate by keeping the first occurrence. - Airdata exports may include leading spaces in some column names (e.g., ` xSpeed(mph)`). Consider cleaning column names (e.g., `rename_with(trimws)` or `janitor::clean_names()`). - `winddir` in ULSA PRO is defined relative to the sensor nose/heading (0° = wind coming from the sensor nose). Converting to a meteorological direction requires the installation azimuth (offset). Citation and licensePlease cite this Zenodo record (DOI: 10.5281/zenodo.17988010) and the associated paper.License: **[CC-BY 4.0]**Contact: **[Koji Ito /J. F. Oberlin University / [e-mail]]**