**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** 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** Long-range scanning Doppler lidar located on Gordon Ridge. The WindTracer provides high-resolution, long-range lidar data for use in the WFIP2 program. **Data Details** The system is configured to take data in three different modes. All three modes take 15 minutes to complete and are started at 00, 15, 30, and 45 minutes after the hour. *The first nine minutes of the period are spent performing two high-resolution, long-range Plan Position Indicator (PPI) scans at 0.0 and -1.0 degree elevation angles (tilts). These data have file names annotated with HiResPPI noted in the "optional fields" of the file name; for example: lidar.z09.00.20150801.150000.HiResPPI.prd. *The next six minutes are spent performing higher altitude PPI scans and Range Height Indicator (RHI) scans. The PPI scans are completed at 6.0- and 30.0-degree elevations, and the RHI scans are completed from below the horizon (down into valleys, as able), up to 40 degrees elevation at 010-, 100-, 190-, and 280-degree azimuths. These files are annotated with PPI-RHI noted in the optional fields of the file name; for example: lidar.z09.00.20150801.150900.PPI-RHI.prd *The last minute is spent measuring a high-altitude vertical wind profile. Generally, this dataset will include data from near ground level up to the top of the planetary boundary layer (PBL), and higher altitude data when high-level cirrus or other clouds are present. The Velocity Azimuth Display (VAD) is measured using six lines of sight at an elevation angle of 75 degrees at azimuth angles of 000, 060, 120, 180, 240, and 300 degrees from True North. The files are annotated with VAD in the optional fields of the file name; for example: lidar.z09.00.20150801.151400.VAD.prd. LMCT does have a data format document that can be provided to users who need programming access to the data. This document is proprietary information but can be supplied to anyone after signing a non-disclosure agreement (NDA). To initiate the NDA process, please contact **Keith Barr** at keith.barr@lmco.com. The data are not proprietary, only the manual describing the data format. **Data Quality** Lockheed Martin Coherent Technologies (LMCT) has implemented and refined data quality analysis over the last 14 years, and this installation uses standard data-quality processing procedures. Generally, filtered data products can be accepted as fully data qualified. Secondary processing, such as wind vector analysis, should be used with some caution as the data-quality filters still are "young" and incorrect values can be encountered. **Uncertainty** Uncertainty in the radial wind measurements (the system's base measurement) varies slightly with range. For most measurements, accuracy of the filtered radial wind measurements have been shown to be within 0.5 m/s with accuracy better than 0.25 m/s not uncommon for ranges less than 10 km. **Constraints** Doppler lidar is dependent on aerosol loading in the atmosphere, and the signal can be significantly attenuated in precipitation and fog. These weather situations can reduce range performance significantly, and, in heavy rain or thick fog, range performance can be reduced to zero. Long-range performance depends on adequate aerosol loading to provide enough backscattered laser radiation so that a measurement can be made.

**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** 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 dataset includes 15-minute average wind speed and direction records from 30 m to 330 m above ground level (AGL) in 10-m range gates. Data were collected by a Scintec MFAS wind profiler installed at the Decker Ranch in Oregon, about 4.4 km southeast of Kent, Ore., and are intended for validating WFIP2 model improvements. **Data Details** Instrument location: * N 45°09'54.42" (N 45.165117) * W120°39'20.87" (W 120.655799) Instrument clock and computer system time set to UTC. **Data Quality** The Scintec MFAS wind profiler instrument installed at the Decker Ranch is capable of measuring at heights up to 1000 m. For this study, the maximum height was set to 330 m. The instrument was oriented to true north, so no corrections to the wind direction should be made. Scintec wind profilers come with the APRun software package, which performs data collection and quality control (QC), among other functions. Version 1.46 of APRun was used in this study. The APRun manual states: *The primary results are checked against local signal quality criteria, combined signal quality criteria and two-dimensional spatial/temporal consistency tests. Any data that does not pass all quality control tests is devalidated and removed*. Devalidation means replacing the value with an error value, usually a series of ‘9’s, such as 99.99 or 999.99. Not all devalidated data are actually removed from the *.mnd files, so the user must filter them out. There are some error flags that indicate the type of error, but these are not included in the *.mnd files, and we have no access to them. Because QC already has been performed by APRun, our QC procedures consisted of removing samples with error values and performing a visual inspection of the data to see if larger patterns indicated any kind of problem. There are 623 gaps of two hours or less and 61 gaps of more than two hours. The longest gap is 15.31 days, from 2016-12-07 03:00Z to 2016-12-22 10:30Z. All gaps that exceed two hours are listed in file: Decker_Ranch_gaps.txt.

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