**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-wascolidar-readme.docx." **Data Quality** Refer to the attached "noaa-esrl-wascolidar-readme.docx" Readme file. **Uncertainty** Refer to the attached "noaa-esrl-wascolidar-readme.docx" Readme file. **Constraints** Refer to the attached "noaa-esrl-wascolidar-readme.docx" Readme file.

**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 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.

**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** 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** 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** 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.