Lidar - California - Leosphere Windcube 866 (120), Humboldt - Raw Data
공공데이터포털
**Overview** Deployment off the coast of Humboldt, California **Data Details** Windcube Data Files: lidar.z05.00.20200929.000000.gyro.7z lidar.z05.00.20200929.000000.rtd.7z lidar.z05.00.20200929.000000.sta.7z lidar.z05.00.20200929.000000.stdrtd.7z lidar.z05.00.20200929.000000.stdsta.7z The Windcube data is compressed via 7-zip: "sta" files are 10 minute averaged data. "rtd" files are ~1 second data. "gyro" files are buoy movement data. 7z is the new archive format, providing high compression ratio. The main features of 7z format: Open architecture High compression ratio Strong AES-256 encryption Ability of using any compression, conversion or encryption method Supporting files with sizes up to 16000000000 GB Unicode file names Solid compressing Archive headers compressing 7z has open architecture, so it can support any new compression methods. https://www.7-zip.org/7z.html **Data Quality** Additional meta data to follow
Lidar - California - Leosphere Windcube 866 (130), Morro Bay - Raw Data
공공데이터포털
**Overview** Deployment off the coast of Morro Bay, California. **Data Details** Windcube Data Files: lidar.z06.00.20200929.000000.gyro.7z lidar.z06.00.20200929.000000.rtd.7z lidar.z06.00.20200929.000000.sta.7z lidar.z06.00.20200929.000000.stdrtd.7z lidar.z06.00.20200929.000000.stdsta.7z The Windcube data is compressed via 7-zip: "sta" files are 10 minute averaged data. "rtd" files are ~1 second data. "gyro" files are buoy movement data. 7z is the new archive format, providing high compression ratio. The main features of 7z format: Open architecture High compression ratio Strong AES-256 encryption Ability of using any compression, conversion or encryption method Supporting files with sizes up to 16000000000 GB Unicode file names Solid compressing Archive headers compressing 7z has open architecture, so it can support any new compression methods. https://www.7-zip.org/7z.html **Data Quality** Additional meta data to follow. PNNL recommends adding 180 degrees to the lidar wind directions at Morro Bay, as there is a directional issue associated with GPS cables being swapped on the buoy during buoy commissioning. The 180 degrees offset is going to be very close to our final post-processed data, that will be uploaded at the end of the campaign in September or November 2021. Please email Alicia Gorton with any questions by clicking on her name under Contacts. (alicia.gorton@pnnl.gov)
Lidar - California - Leosphere Windcube 866 (130), Morro Bay - Processed Data
공공데이터포털
**Overview** The purpose of this dataset is to provide preliminary filtered, averaged lidar data and standardize the data format of various data streams from the buoy into NetCDF. The attached Lidar Buoy Data Dictionary provides further details on the various instruments mounted on the buoys, parameters measured by each instrument, and the frequency of data collection. **Data Details** The lidar wind directions from the raw data were corrected by adding 180 degrees, due to a field error in connecting the Global Positioning System (GPS) leads to the lidar unit. **Data Quality** Standard filtering thresholds on the averaged data were applied and several data format issues of the raw data were streamlined to create a standardized NetCDF format data. **Uncertainty** The uncertainty of lidar data has not been analyzed, but it is not expected to deviate from instrument technical specifications.
Lidar - ND Halo Scanning Doppler, Boardman - Raw Data
공공데이터포털
**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.