The LiDAR_Data_Download script looks at the URL that contains your county or municipality data, collects all of the URLs ,and downloads each file. The program utilizes threading and in turn uses the multiple processors of your pc to download several items at the same time, it will take several hours. What you will need to do is:1. Go to https://gis1.oit.ohio.gov/ZIPARCHIVES_III/ELEVATION/3DEP/LIDAR/ in a browser find the link for your data, right click it and select 'Copy link address'2. Go to line 23 in the program and paste the hyperlink between the quotes of the url variable replacing the text 'Paste Hyperlink Here'3. Update the savePath variable on line 38, to where on your system you'd like the data saved. When I did this for Belmont County the resulting folder ended up being over 350 GB, so make sure you have sufficient hard drive space. Comments in the code should guide you through the process. I wrote & ran this in Python 3.12, but any version of Python 3 should work.Submitted By: Anthony Atkins

The data consist of point clouds containing 3D spatial coordinates (eastings, northings, and heights) and intensities (a measure of the strength of the backscattered laser pulse) in the American Society for Photogrammetry and Remote Sensing (ASPRS) LAS file format: http://www.asprs.org/wp-content/uploads/2019/03/LAS_1_4_r14.pdf. The locations for which data were collected include: 1) Intersection of HWY 99W and Newberg-Dundee Bypass, Dundee, OR (collected during construction of the bypass); 2) McNary field on the Oregon State University campus; and 3) NE 45th Street and Mary Gates Memorial Dr NE, Seattle, WA. The data are intended for research purposes. The data were collected using two different lidar systems: 1) Velodyne VLP-16 (Newberg-Dundee and OSU McNary field sites), and 2) Phoenix Lidar Systems MiniRanger, incorporating Riegl miniVUX-1UAV lidar (Seattle site). The Velodyne VLP-16 data were georeferenced using a combination of OxTS RT Post Process and custom MATLAB scripts, which are described in the project report. The Phoenix Lidar Systems MiniRanger data were georeferenced by first post-processing the trajectory using Inertial Explorer and then generating the point clouds using Phoenix LiDAR Systems SpatialExplorer v4.0.3. Additional metadata are provided in the “metadata.txt” files available on the FTP site.

Hurricane Maria induced about 70,000 landslides throughout Puerto Rico, USA (Hughes and others, 2019, https://doi.org/10.5066/P9BVMD74). Data in this project pertain to two areas situated in Puerto Rico’s rugged Cordillera Central range. Combined, these areas account for more than half of the hurricane-induced landslides. One of these areas encloses two neighboring municipalities, Lares Municipio, and Utuado Municipio, and the second area encloses Naranjito Municipio. These data include one-meter (1-m) resolution raster grids derived from post-hurricane light detection and ranging (lidar) digital elevation models (DEM) available at https://apps.nationalmap.gov/lidar-explorer/#/. The elevation data as well as slope and flow accumulation grids derived from them were the primary inputs for soil-depth models and slope-stability models. We used outputs from these models to map susceptibility to landslide initiation and evaluate future landslide impacts from storms like Hurricane Maria for these three municipalities. The data accompany an interpretive paper that is currently under review. The area covering Lares and Utuado is divided into four overlapping tiles. A fifth tile covers Naranjito. Digital elevation model (DEM) tiles extend far enough into neighboring tiles and municipalities to allow assessment of flow accumulation as well as landslide runout and debris-flow inundation in watersheds that straddle boundaries. The raster grids are grouped into zip archives according to their associated tiles and each zip archive contains a complete set of nine 1-m resolution input and output grids of the following data types and naming conventions, in which the "" identifies the tile location as well as selected model options: pm.tif - 1m- lidar-derived digital elevation model (DEM), with elevation in meters nar1mfloacc.tif or larutufloacc.tif - D8 flow accumulation raster, used as input for soil depth estimates Zn.tif - input-parameter-zone codes (unitless) to define geologic terrane, used as input for soil depth and slope-stability estimates RG_slope.tif - slope of the ground surface (degrees) computed using REGOLITH 1.0 (https://doi.org/10.5066/P9U2RDWJ) and used as input for slope-stability analysis RG_NASD_smo_.tif - soil depth (meters) estimates computed using REGOLITH 1.0 (https://doi.org/10.5066/P9U2RDWJ) and used as input for slope-stability analysis TRfs_min_.tif- 1d factor of safety (unitless) computed using TRIGRS 2.1 (https://doi.org/10.5066/F7M044QS) TRp_at_fs_min_.tif- 1d pressure head (meters) computed using TRIGRS 2.1 (https://doi.org/10.5066/F7M044QS) and used as input for 3D slope-stability analysis SL3_fs3d_.tif - quasi-three-dimensional (3D) factor of safety (unitless) for trial surface centered at each grid cell computed using Slabs3D 1.0 (https://doi.org/10.5066/P9G4I8IU) SL3_fs3dmn_.tif - minimum 3D factor of safety (unitless) for any trial surface intersecting each grid cell computed using Slabs3D 1.0 (https://doi.org/10.5066/P9G4I8IU) Each tile has six asociated metadata files. Parameter inputs to and outputs from the programs REGOLITH 1.0, TRIGRS 2.1, and Slabs3D 1.0 are grouped into corresponding metadata files for each tile. The metadata files have the following naming convention, in which the "" is a code that identifies the tile ("larutu1," or "a1," "larutu2," or "a2," "larutu3," or "a3," and "larutu4," or "a4," for the Lares and Utuado tiles and "nar" for the Naranjito tile): pm.xml - 1m-lidar-derived DEM floacc.xml - D8 flow accumulation raster Zn.xml - input-parameter-zone raster RG.xml - REGOLITH 1.0 parameter input file, slope output raster and soil-depth output raster TR_.xml - TRIGRS 2.1 parameter input file, pressure head output raster and local factor of safety output raster SL3_.xml - Slabs3D 1.0 parameter input file, 3D factor of safety output rasters Parameter input files accompany this data release, with the following naming convention, in which the "" is a code that identifies the tile ("a1," "a2," "a3," and "a4" in Lares and Utuado or "nar" for Naranjito): rg_in_.txt - REGOLITH 1.0 input parameters tr_in_.txt - TRIGRS 2.1 input parameters slabs3d_in_.txt - Slabs3D 1.0 input parameters