**Overview** These profiling lidar datasets collect profiles of wind speed and wind direction from nominally 40 m above the surface to 220 m above the surface, depending on visibility. **Data Quality** Only data points with CNR -22 dB are included in these 2-min averaged files.

**Overview** Wind and lidar turbulence profiles from 40 m to 220 m above the surface. **Data Quality** These two-minute-averaged data files consider the 1 Hz line-of-sight measurements that pass the -22 dB CNR quality control threshold. **Uncertainty** Line-of-sight measurements are converted to horizontal wind speed by assuming horizontal homogeneity in the measurement volume (as discussed in several publications, including Rhodes and Lundquist 2013 and Lundquist et al. 2015). In inhomogeneous flow, this assumption may not be valid. These instruments were sited to avoid breaking the horizontal inhomogeneity assumption, although the Gordon's Ridge sight may be problematic in this respect.

**Overview** Wind and lidar turbulence profiles from 40 m to 220 m above the surface. **Data Quality** These two-minute-averaged data files consider the 1 Hz line-of-sight measurements that pass the -22 dB CNR quality control threshold. **Uncertainty** Line-of-sight measurements are converted to horizontal wind speed by assuming horizontal homogeneity in the measurement volume (as discussed in several publications, including Rhodes and Lundquist 2013 and Lundquist et al. 2015). In inhomogeneous flow, this assumption may not be valid. These instruments were sited to avoid breaking the horizontal inhomogeneity assumption, although the Gordon's Ridge sight may be problematic in this respect.

**Overview** These profiling lidar datasets collect profiles of wind speed and wind direction from nominally 40 m above the surface to 220 m above the surface, depending on visibility. **Data Quality** Only data points with CNR -22 dB are included in these 2-min averaged files.

**Overview** Wind and lidar turbulence profiles from 40 m to 220 m above the surface. **Data Quality** These two-minute-averaged data files consider the 1 Hz line-of-sight measurements that pass the -22 dB CNR quality control threshold. **Uncertainty** Line-of-sight measurements are converted to horizontal wind speed by assuming horizontal homogeneity in the measurement volume (as discussed in several publications, including Rhodes and Lundquist 2013 and Lundquist et al. 2015). In inhomogeneous flow, this assumption may not be valid. These instruments were sited to avoid breaking the horizontal inhomogeneity assumption, although the Gordon's Ridge sight may be problematic in this respect.

**Overview** Data submission for WFIP2 at Vansycle Ridge (Oregon). Vertical-profiling lidar data from a Wind Cube v2, included 10-minute averages of wind speed and wind direction up to 200 m. Data collected during WFIP2. **Data Details** Z-wind has the following notation: negative = upward positive = downward probe volume is +/- 20 m at all heights **Data Quality** Other than the Quality Assurance (QA) procedures implemented by the lidar during data processing, no other quality procedures are applied. These data include a carrier-to-noise ratio (CNR) threshold of -23. CNR below this threshold result in -9999 for all data points

**Overview** The University of Notre Dame (ND) scanning lidar dataset used for the WFIP2 Campaign is provided. The raw dataset contains the radial velocity and backscatter measurements along with the beam location and other lidar parameters in the header. **Data Details** 1) A Halo photonics scanning lidar, owned by ND, was deployed and operated from 12/17/2015 to 02/09/2016. On 02/09/2016, this lidar was replaced by a Halo photonics scanning lidar owned by the Army Research Lab (ARL). 2) For information on the scanning patterns, refer to attached "ReadMe" file. 3) Data Period from 12/15/2015 to 02/09/2016: One data file per day (24 hours). File name of each daily data file has {boardman} as {optionalfields}. For example: lidar.z07.00.20150414.143000.boardman.csm. 4) Data Period after 02/09/2016: One scan file every 15 minutes, one stare file, and one background file every hour. File names have the following {optionalfields}: {background_boardman} for background files; {scan_boardman} for scan files; and {stare_boardman} for stare files. For example: - lidar.z07.00.20150414.143000.background_boardman - lidar.z07.00.20150414.143000.scan_boardman - lidar.z07.00.20150414.143000.stare_boardman 5) Site information: - Site: Boardman, OR - Latitude: 45.816185° N - Longitude: 119.811766° W - Elevation (meters): 112.0 **Data Quality** Raw data: no quality control (QC) is applied. **Uncertainty** The lidar measurements' uncertainty varies with the range of the measurements. Please refer to Pearson et al. (2009) for more details. **Constraints** 1) Because of the change of lidars, the data were downloaded in different formats. Hence, the raw data (unfiltered) primarily are in two formats: *.csm and *.hpl. 2) The data were downloaded every one hour or 15 minutes. Hence, the datasets are not concatenated for continuous scans. 3) A lidar offset of +195 deg (to True North) was added to the azimuthal angles from the ND scanning lidars, spanning 12/17/2015 until 02/09/2016. Later, this was corrected for the data from 02/09/2016 as the lidar aligned to True North.

**Overview** The available "readme" file introduces the basics of the Doppler lidar data and offers a detailed description of the variables present in the data files. For those with any further questions about the data and its interpretation, contact either Alan Brewer () or Sunil Baidar (). It is highly recommended to discuss any planned use of the data with National Oceanic and Atmospheric Administration-Chemical Sciences Division (NOAA-CSD) scientists. For more information, refer to the Readme file: "noaa-esrl-arlingtonlidar-readme-1.pdf." **Data Quality** Refer to the attached "noaa-esrl-arlingtonlidar-readme-1.pdf" Readme file. **Uncertainty** Refer to the attached "noaa-esrl-arlingtonlidar-readme-1.pdf" Readme file. **Constraints** Refer to the attached "noaa-esrl-arlingtonlidar-readme-1.pdf" Readme file.

**Overview** The WindCube v2 is a pulsed LIDAR and uses four beams sent in succession in the four cardinal directions along a 28°scanning cone angle to measure horizontal velocity and wind direction. A fifth beam is sent in the vertical direction to measure vertical velocity. Measurement heights are user-programmed and range from 40 m to 200 m. During HilFlowS, the WindCube v2 was programmed to measure from 40 m to 150 m at 10-m intervals. The data sampling rate was 1 s, wind speed accuracy was 0.1 m/s, and direction accuracy was 1.5° for the instrument. The data were averaged across 10-min. averaging intervals. **Data Details** Data Begins: 2019-07-03\ Data Ends: 2019-09-23 Additional Information, files begin with:\ Timestamp (end of interval)\ Wiper count Available at each level (40 m - 150 m):\ Wind Speed (m/s)\ Wind Speed Dispersion or Standard Devation (m/s) \ Wind Speed min (m/s)\ Wind Speed max (m/s)\ Wind Direction (deg)\ Z-wind or Vertical Wind Speed (m/s)\ Z-wind Dispersion or Standard Deviation (m/s)\ carrier-to-noise ratio (CNR), specified in decibels (dB)\ CNR min (dB)\ Dopp Spect Broad (m/s)\ Data Availability (%)

**Overview** The available "readme" file introduces the basics of the Doppler lidar data and offers a detailed description of the variables present in the data files. If you have any further questions about the data and its interpretation, contact either Alan Brewer () or Sunil Baidar (). It is highly recommended to discuss any planned use of the data with NOAA-CSD scientists. For more information, refer to the attached readme. **Data Quality** Refer to attached readme file. **Uncertainty** Refer to attached readme file. **Constraints** Refer to attached readme file.