데이터셋 상세
미국
Lidar - ESRL WindCube 200s, Wasco Airport - Processed Data
**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.
데이터 정보
연관 데이터
Lidar - ESRL WindCube 200s, Arlington Airport - Reviewed Data
공공데이터포털
**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.
Lidar - CU WindCube V1 Profiler, Wasco Airport - Reviewed Data
공공데이터포털
**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.
Lidar - CU WindCube V1 Profiler, Troutdale - Reviewed Data
공공데이터포털
**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.
Lidar - CU WindCube V2 Profiler, Gordons Ridge - Reviewed Data
공공데이터포털
**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.
Radar - ESRL Wind Profiler with RASS, Wasco Airport - Reviewed Data
공공데이터포털
**Overview** Wind Profiler with Radio Acoustic Sounding System (RASS) data. **Data Quality** Automatic quality control (QC) followed by visual manual QC.
Lidar - ND Halo Scanning Doppler, Boardman - Derived Data
공공데이터포털
**Overview** The University of Notre Dame (ND) scanning LiDAR dataset used for the WFIP2 Campaign is provided. The LiDAR is a Halo Photonics Stream Line Scanning Doppler LiDAR. **It is highly recommended to discuss any planned use of these data with University of Notre Dame scientists**. For more information refer to the attached "WFIP2 Project (lidar.z07)" Readme file. **Data Details** Refer to the attached "WFIP2 Project (lidar.z07)" Readme file. Wind Direction is from Geographic North. **Data Quality** Quality-controlled data (lidar.z07.a0) and relative products (lidar.z07.c0) are provided by the ND team following the Quality Control (QC) procedure described in the attached "WFIP2 Project (lidar.z07)" Readme file, which also includes a detailed description of the variables present in the data files. **Uncertainty** Refer to the attached "WFIP2 Project (lidar.z07)" Readme file. **Constraints** Refer to the attached "WFIP2 Project (lidar.z07)" Readme file.
Sodar - NREL Scintec MFAS Wind Profiler, Decker Ranch Airstrip - Raw Data
공공데이터포털
**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.
Lidar - ND Halo Scanning Doppler, Boardman - Reviewed Data
공공데이터포털
**Overview** The University of Notre Dame (ND) scanning LiDAR dataset used for the WFIP2 Campaign is provided. The LiDAR is a Halo Photonics Stream Line Scanning Doppler LiDAR. **It is highly recommended to discuss any planned use of these data with University of Notre Dame scientists**. For more information refer to Section 4.c) in the updated version of the "WFIP2 Project (lidar.z07)" Readme file, where the lidar.z07.b0 dataset is fully explained. **Data Details** Refer to the attached updated version of the "WFIP2 Project (lidar.z07)" Readme file. **Data Quality** Reviewed, quality-controlled second-order products (lidar.z07.b0) are provided by the ND team following the Quality Control (QC) procedure described in the updated version of the "WFIP2 Project (lidar.z07)" Readme file, which also includes a detailed description of the variables present in the data files. **Uncertainty** Refer to the attached updated version of the "WFIP2 Project (lidar.z07)" Readme file. **Constraints** Refer to the attached updated version of the "WFIP2 Project (lidar.z07)" Readme file.
Microbarograph - ESRL Hi-Res Microbarograph, Wasco Airport - Raw Data
공공데이터포털
**Overview** High-precision barometers (Paroscientific 6000-16B-IS) are combined with Nishiyama-Bedard Quad Disk pressure probes, measuring pressure (mb) at the surface, nominally 2 m above ground level. Data are sampled at 20 Hz for potential studies of turbulence. The sensors' high accuracy makes them useful for determining horizontal pressure gradients and their relation to wind ramp events, as well as the temporal variability of pressure associated with mountain wakes and waves. **Note different ASCII file formats for Goldendale (z04) and Walla Walla (z09) sites.** **Data Details** **ASCII Format** * Field 1: DataloggerID * Field 2: Year * Field 3: Julian Day * Field 4: Hour and Min (UTC) * Field 5: Seconds Decimal (UTC) * Field 6: GPS Lock Identifier (A = Locked Signal; V=Insufficient Satellite Coverage) * Field 7: GPS Clock String (UTC) * Field 8: Pressure (mb) Example of data file: 101,2016,243,000,0.04,0001A,2016/08/29 23:59:58.150,913.314500 101,2016,243,000,0.09,0001A,2016/08/29 23:59:58.200,913.315652 101,2016,243,000,0.14,0001A,2016/08/29 23:59:58.250,913.313351 101,2016,243,000,0.19,0001A,2016/08/29 23:59:58.300,913.315626 101,2016,243,000,0.24,0001A,2016/08/29 23:59:58.350,913.315255 101,2016,243,000,0.29,0001A,2016/08/29 23:59:58.400,913.315267 101,2016,243,000,0.34,0001A,2016/08/29 23:59:58.450,913.315430 101,2016,243,000,0.39,0001A,2016/08/29 23:59:58.500,913.312698 101,2016,243,000,0.44,0001A,2016/08/29 23:59:58.550,913.315139 101,2016,243,000,0.49,0001A,2016/08/29 23:59:58.600,913.314793 101,2016,243,000,0.54,0001A,2016/08/29 23:59:58.650,913.317083 101,2016,243,000,0.59,0001A,2016/08/29 23:59:58.700,913.316959 101,2016,243,000,0.64,0001A,2016/08/29 23:59:58.750,913.312730 101,2016,243,000,0.69,0001A,2016/08/29 23:59:58.800,913.315043 101,2016,243,000,0.74,0001A,2016/08/29 23:59:58.850,913.318476 101,2016,243,000,0.79,0001A,2016/08/29 23:59:58.900,913.312417 101,2016,243,000,0.84,0001A,2016/08/29 23:59:58.950,913.317606 101,2016,243,000,0.89,0001A,2016/08/29 23:59:59.000,913.316681 101,2016,243,000,0.94,0001A,2016/08/29 23:59:59.050,913.314978 101,2016,243,000,0.99,0001A,2016/08/29 23:59:59.100,913.318996 **Goldendale (z04) and Walla Walla (z09) ASCII Format** * Field 1: GPS Clock String (UTC) * Field 2: Pressure (mb) Example of data file: 2016/08/29 23:59:58.150,913.314500 2016/08/29 23:59:58.200,913.315652 2016/08/29 23:59:58.250,913.313351 2016/08/29 23:59:58.300,913.315626 2016/08/29 23:59:58.350,913.315255 2016/08/29 23:59:58.400,913.315267 2016/08/29 23:59:58.450,913.315430 2016/08/29 23:59:58.500,913.312698 2016/08/29 23:59:58.550,913.315139 2016/08/29 23:59:58.600,913.314793 2016/08/29 23:59:58.650,913.317083 2016/08/29 23:59:58.700,913.316959 2016/08/29 23:59:58.750,913.312730 2016/08/29 23:59:58.800,913.315043 2016/08/29 23:59:58.850,913.318476 2016/08/29 23:59:58.900,913.312417 2016/08/29 23:59:58.950,913.317606 2016/08/29 23:59:59.000,913.316681 2016/08/29 23:59:59.050,913.314978 2016/08/29 23:59:59.100,913.318996 **Data Quality** No special data quality control is needed. **Uncertainty** * 0.0001% Resolution * ±0.08 hPa Accuracy * Stability better than 0.1 hPa per year.
Microwave Radiometer - ESRL Radiometrics MWR, Wasco Airport - Raw Data
공공데이터포털
**Overview** These data monitor real-time profiles of temperature (K), water vapor (gm-3), relative humidity (%), and liquid water (gm-3) up to 10 km. **Data Details** All output files are named automatically using the following format: yyyy-mm-dd_hh-mm-ss_xxx.csv, where yyyy is the year when the file was started, mm is the month of the year, dd is the day of the month, hh is the hour of the day, mm is the minute of the hour, ss is the second of the minute, and xxx defines the output file type as follows: - xxx=lv0 level0 file - xxx=lv1 level1 file - xxx=lv2 level2 file All output files contain a sequential record number in the first field, starting with the number 1. All output files contain a date/time stamp in the second field of all records that contain time-dependent data. lv0 files contain raw, unprocessed data in engineering units. lv0 files contain 100 percent of the information needed to reprocess the raw data with alternative calibration information or algorithms. lv1 files contain real-time brightness temperatures (TB) for each channel specified in the configuration file. Real-time level1 files are produced from contemporaneous level0 data and calibration information in the configuration file. lv2 files contain records of real-time retrievals of temperature (K), water vapor (gm-3), relative humidity (%), and liquid water (gm-3) profiles. The retrievals are produced using the contemporaneous level1 data and the neural network files specified in the configuration file. **Data Quality** **NOAA/PSD: Wasco OR and Troutdale OR** Microwave radiometers (MWRs) must be calibrated periodically, both for the K-band and V-band. The calibration is needed to convert measured voltages/counts into brightness temperatures (TB). Two types of calibrations are possible: the liquid nitrogen (LN2), or cold target one, and tipping curve calibration (TCC). All microwave channels (K-band and V-band) can be calibrated using LN2 as a cold absolute standard. The disadvantage of the LN2 calibration is that it requires several people onsite to perform. Conversely, the advantage of a TCC is that it can be performed remotely. However, a successful TCC requires a non-optically thick atmosphere at the frequency at stake. At approximately sea level, only K-band channels are transparent enough to be calibrated via this method. For this reason, trips to perform LN2 calibrations are scheduled approximately every six months. Also, after the LN2 calibrations have been performed, radiosonde were launched for sanity checks and will be used to test the calibrations' accuracy. TCC calibrations also have been scheduled to occur remotely (more often than LN2 calibrations, approximately 1-2 months). This schedule for LN2 and TCC calibrations should ensure the quality and reliability of data collected with the MWRs because it depends on the instrument's thermal stability, noise level, and calibration accuracy (Solheim et al. 1998a). MWRs retrieve vertical profiles of atmospheric variables using historic radiosondes and a regression method or neural network (Solheim et al. 1998a, 1998b; Ware et al. 2003). The algorithm, based on a radiative transfer model (Rosenkranz 1998), was trained for all WFIP2-deployed MWRs by the Radiometrics staff on a multi-year radiosonde climatology from the sites' proximity. All MWRs are equipped with surface observations of temperature, pressure, and relative humidity, which also were calibrated prior to the WFIP2 campaign. These surface observations are important because they serve as a boundary condition for the neural network approach. One quality control (QC) approach involves monitoring the good functioning of the surface sensor (comparing to collocated surface measurements from other met stations) and identifying periods of possible malfunctions. If this happens, the retrieved atmospheric profiles most likely would not be accurate, However, the level0 files (where the TB are saved) will be post-reprocessed (using software from