**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** 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** 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 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 dataset includes 15-minute average wind speed and direction records from 10 m to 250 m above ground level (AGL) in 5-m range gates. Data were collected by a Scintec SFAS wind profiler installed at the Condon State Airport in Oregon, about 1.8 km northeast of the center of Condon, Ore., and are intended for validating WFIP2 model improvements. **Data Details** Instrument location: * N 45° 14’ 41.58” (N 45.244885) * W 120° 10’ 06.58” (W 120.168495) Instrument clock and computer system time set to UTC. **Data Quality** The Scintec SFAS wind profiler instrument installed at the Decker Ranch is capable of measuring at heights up to 500 m. For this study, the maximum height was set to 250 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 515 gaps of two hours or less and 26 gaps of more than two hours. The longest gaps are: * 47.78 days, from 2016-03-16 18:00Z to 2016-05-03 12:45Z * 40.20 days, from 2016-06-04 13:15Z to 2016-07-14 18:00Z All gaps that exceed two hours are listed in file: Condon_gaps.txt.

**Data Details** UMBC Lidar: Water Tank: lat(40.041) lon(-105) alt(1602) 20150410-20150416 NW Pad: lat(40.051) lon(-105) alt(1578) 20150416-20150428 Visitor's Center: lat(40.045) lon(-105) alt(1587) 20150428 - 20150502

**Overview** Wind Profiler with Radio Acoustic Sounding System (RASS) data. **Data Quality** Automatic quality control (QC) followed by visual manual QC.

**Overview** This dataset contains measurements from eight different Vaisala Triton Wind Profiler instruments. The Triton Wind Profiler is a sodar wind profiler that measures wind speed, direction, and turbulence intensity at heights from 30 m to 200 m above ground every 10 minutes. The eight Tritons are located at various sites around the WFIP2 study area. **Data Details** Regarding the minimum requirements for the site description, a Keyhole Markup Language (KML) file is attached with all of the AON Triton locations. Unfortunately, there are no photos of the sites. The layout of each site is simple. At all locations, the Triton Wind Profiler is placed on the ground with the solar panel facing due south. Each unit is solar powered and communicates its data via satellite, so there are no cables of any kind. Also, the specified start and end dates are for the entire AON network. Some individual units start later or end earlier. All start/end dates for the individual units are given as follows: AON1 (z17): 10/1/2015 -- 7/31/2017 AON2 (z14): 10/1/2015 -- 7/31/2017 AON3 (z18): 10/1/2015 -- 7/31/2017 AON4 (z12): 12/5/2015 -- 7/31/2017 AON5 (z06): 10/1/2015 -- 7/31/2017 AON6 (z05): 10/1/2015 -- 7/31/2017 (w/gap 2016-08-01 -- 2016-09-28) AON7 (z02): 10/1/2015 -- 7/31/2017 (w/gap 2016-07-01 -- 2016-11-18) AON8 (z01): 12/7/2015 -- 4/9/2016 AON9 (z20): 11/19/2016 -- 7/31/2017 **Data Quality** The Triton firmware has a quality assessment algorithm that assigns a quality factor (“quality”) to each time/height measurement of wind, expressed as a percent value in the range 0-100. In addition, the upward Doppler velocity (“vert”) is measured and can be used as an indicator of falling precipitation, which negatively affects data quality. Two automated procedures are applied in real time as these data (level 00) are sent to the DAP. Data are set to a missing value (null in the CSV file) when either “quality” < 90% or “vert” < -1.5 m/s. Because the data level is from a real-time feed, no manual quality control (QC) has been performed. Periods of missing data are likely due to real-time glitches, many of which will be filled in once the final data retrieval and QC process are performed (level b0). Finally, for the first few months of the study, the variables provided in the real-time (level "00") files differ slightly than what is specified on this metadata web page. The header line in the earlier CSV files is fairly self-explanatory in defining the variables and units. **Uncertainty** When compared to nearby towers instrumented with cup anemometers and wind vanes, the root mean square (RMS) difference in 10-minute wind speed between the Triton and met tower typically is around 0.5 m s-1. When tested at 30 different sites in a recent validation study, the RMS difference in long-term mean wind speed between the Triton and met tower is 1.3%. **Constraints** Various meteorological and environmental conditions can lead to either weaker returns or enhanced noise, resulting in a poor measurement. The higher the target point, the more difficult it is to retrieve a strong signal. Hence, a common situation is that good data will be obtained up to some height yet not above it. The percentage of time that good data are recovered at a particular height is the data recovery rate. In a recent validation study, data recovery rates were around 98% at lower heights, slowly dropping off to 96% at 100 m, 83% at 160 m, and 70% at 200 m.

**Overview** This dataset contains measurements from eight different Vaisala Triton Wind Profiler instruments. The Triton Wind Profiler is a sodar wind profiler that measures wind speed, direction, and turbulence intensity at heights from 30 m to 200 m above ground every 10 minutes. The eight Tritons are located at various sites around the WFIP2 study area. **Data Details** Regarding the minimum requirements for the site description, a Keyhole Markup Language (KML) file is attached with all of the AON Triton locations. Unfortunately, there are no photos of the sites. The layout of each site is simple. At all locations, the Triton Wind Profiler is placed on the ground with the solar panel facing due south. Each unit is solar powered and communicates its data via satellite, so there are no cables of any kind. Also, the specified start and end dates are for the entire AON network. Some individual units start later or end earlier. All start/end dates for the individual units are given as follows: AON1 (z17): 10/1/2015 -- 7/31/2017 AON2 (z14): 10/1/2015 -- 7/31/2017 AON3 (z18): 10/1/2015 -- 7/31/2017 AON4 (z12): 12/5/2015 -- 7/31/2017 AON5 (z06): 10/1/2015 -- 7/31/2017 AON6 (z05): 10/1/2015 -- 7/31/2017 (w/gap 2016-08-01 -- 2016-09-28) AON7 (z02): 10/1/2015 -- 7/31/2017 (w/gap 2016-07-01 -- 2016-11-18) AON8 (z01): 12/7/2015 -- 4/9/2016 AON9 (z20): 11/19/2016 -- 7/31/2017 **Data Quality** The Triton firmware has a quality assessment algorithm that assigns a quality factor (“quality”) to each time/height measurement of wind, expressed as a percent value in the range 0-100. In addition, the upward Doppler velocity (“vert”) is measured and can be used as an indicator of falling precipitation, which negatively affects data quality. Two automated procedures are applied in real time as these data (level 00) are sent to the DAP. Data are set to a missing value (null in the CSV file) when either “quality” < 90% or “vert” < -1.5 m/s. Because the data level is from a real-time feed, no manual quality control (QC) has been performed. Periods of missing data are likely due to real-time glitches, many of which will be filled in once the final data retrieval and QC process are performed (level b0). Finally, for the first few months of the study, the variables provided in the real-time (level "00") files differ slightly than what is specified on this metadata web page. The header line in the earlier CSV files is fairly self-explanatory in defining the variables and units. **Uncertainty** When compared to nearby towers instrumented with cup anemometers and wind vanes, the root mean square (RMS) difference in 10-minute wind speed between the Triton and met tower typically is around 0.5 m s-1. When tested at 30 different sites in a recent validation study, the RMS difference in long-term mean wind speed between the Triton and met tower is 1.3%. **Constraints** Various meteorological and environmental conditions can lead to either weaker returns or enhanced noise, resulting in a poor measurement. The higher the target point, the more difficult it is to retrieve a strong signal. Hence, a common situation is that good data will be obtained up to some height yet not above it. The percentage of time that good data are recovered at a particular height is the data recovery rate. In a recent validation study, data recovery rates were around 98% at lower heights, slowly dropping off to 96% at 100 m, 83% at 160 m, and 70% at 200 m.

**Overview** **Winds** A radar wind profiler measures the Doppler shift of electromagnetic energy scattered back from atmospheric turbulence and hydrometeors along 3-5 vertical and off-vertical point beam directions. Back-scattered signal strength and radial-component velocities are remotely sensed along all beam directions and combined to derive the horizontal wind field over the radar. These data typically are sampled and averaged hourly and usually have 6-m and/or 100-m vertical resolutions up to 4 km for the 915 MHz and 8 km for the 449 MHz systems. **Temperature** To measure atmospheric temperature, a radio acoustic sound system (RASS) is used in conjunction with the wind profile. These data typically are sampled and averaged for five minutes each hour and have a 60-m vertical resolution up to 1.5 km for the 915 MHz and 60-m up to 3.5k m for the 449 MHz. **Data Details** Spectra data are stored in two daily files, a header (file names contain "H") and a data (file names contain "D") file. The (H)eader files are made up of binary data records containing information about the operational parameters of the profiler, while (D)ata files, also composed of binary data records, contain the spectra data collected by the profiler, i.e. spectral values for each spectral bin for every range gate. **Data Quality** Various quality control (QC) algorithms developed over the years process data in real time on the radar software layer. These algorithms, which run in real time, act on time-series, spectra, moment, and consensus data layers that are persisted in various forms. For a detailed description, refer to the attached QC document: *915 and 449 MHz Radar Wind Profilers and RASS QC*. **Uncertainty** The uncertainty is defined by the spacing of the spectral bin.