This dataset consists of classified LiDAR (Light Detection and Ranging) elevation points produced by the PAMAP Program. PAMAP data are organized into blocks, which do not have gaps or overlaps, that represent 10,000 feet by 10,000 feet on the ground. The coordinate system for blocks in the northern half of the state is Pennsylvania State Plane North (datum:NAD83, units: feet); blocks in the sou...
The Dauphin County, PA 2016 QL2 LiDAR project called for the planning, acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011) State Plane Pennsylvania South Zone, US survey feet; NAVD1988 (Geoid 12B), US survey feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to 711 individual 5,000-foot x 5,000-foot tiles. Tile names use the following naming schema: "YYYYXXXXPAd" where YYYY is the first 3 characters of the tile's upper left corner Y-coordinate, XXXX - the first 4 characters of the tile's upper left corner X-coordinate, PA = Pennsylvania, and d = 'N' for North or 'S' for South. Corresponding 2.5-foot gridded hydro-flattened bare earth raster tiled DEM files and intensity image files were created using the same 5,000-foot x 5,000-foot schema. Hydro-flattened breaklines were produced in Esri file geodatabase format. Continuous 2-foot contours were produced in Esri file geodatabase format. Ground Conditions: LiDAR collection began in Spring 2016, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 84 control points (24 calibration control points and 60 QC checkpoints). These were used to calibrate the LIDAR to known ground locations established throughout the project area.
description: Digital Elevation Model (DEM) dataset current as of 2006. This dataset, produced by the PAMAP Program, consists of a raster digital elevation model with a horizontal ground resolution of 3.2 feet. The model was constructed from PAMAP LiDAR (Light Detection and Ranging) elevation points. PAMAP data a.; abstract: Digital Elevation Model (DEM) dataset current as of 2006. This dataset, produced by the PAMAP Program, consists of a raster digital elevation model with a horizontal ground resolution of 3.2 feet. The model was constructed from PAMAP LiDAR (Light Detection and Ranging) elevation points. PAMAP data a.
These contour lines were derived and delivered for Pennsylvania from the PAMAP Quality Level 3 (QL3) LIDAR data collection between 2006 and 2008. Some post-processing has been done to the original deliverables, including merging, line smoothing, and eliminating duplicate (overlapping) data between collections. This dataset renders the contour lines with the following scale-dependent visibility: 100 foot increments between 1:200,000 and 1:100,000 | 50 foot increments between 1:100,000 and 1:30,000 | 20 foot increments between 1:30,000 and 1:5,000 | 10 foot increments between 1:5,000 and 1:1,000 | and 2 foot increments between 1:1,000 and 1:10. The lines have been smoothed using the ArcGIS Pro 3.3 Smooth Line geoprocessing tool via the Polynomial Approximation with Exponential Kernal (PAEK) and setting a 10 ft smoothing tolerance distance. The extent of this data extends slightly beyond the Pennsylvania boundary into all surrounding states to ensure complete coverage of Pennsylvania. Duplicate (overlapping) contour data between collection years and north/south state plane zones has been eliminated by splitting the data from adjacent collects at county boundaries to ensure a seamless product with no duplication or overlapping data. The contour line geometries along the county boundaries that separate different years of PAMAP data collection (2006, 2007, and 2008) do not always connect properly.
These files contain classified topo/bathy lidar data generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is not gen...
These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the NOAA Lake Level Viewer. It depicts potential lake level rise and fall and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at lake level change, coastal flooding impacts, and exposed lakeshore. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The NOAA Lake Level Viewer may be accessed at: https://coast.noaa.gov/llv. This metadata record describes the Lake Michigan digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Lake Level Viewer described above. This DEM includes the best available lidar, US Army Corps of Engineer dredge surveys, and National Park Service multibeam data known to exist at the time of DEM creation that met project specifications. This DEM includes data for Allegan, Antrim, Benzie, Berrien, Charlevoix, Delta, Emmet, Grand Traverse, Leelanau, Mackinac, Manistee, Mason, Menominee, Muskegon, Oceana, Ottawa, Schoolcraft, and Van Buren counties in Michigan; Lake, La Porte, and Porter Counties in Indiana, Cook and Lake Counties in Illinois, and Brown, Door, Kenosha, Kewaunee, Manitowoc, Marinette, Milwaukee, Oconto, Ozaukee, Racine, and Sheboygan Counties in Wisconsin. The DEM was produced from the following lidar data sets: 1. 2016 NOAA Topobathy Lidar: Upper Lake Michigan Islands 2. 2015 FEMA Marinette County 3. 2013 Indiana Statewide Lidar Collection: Lake, La Porte, Tippecanoe, Newton, Jasper and Porter County Buy-Up 4. 2013 Muskegon County, Michigan Lidar Co-Op 5. 2013 USACE NCMP Topobathy Lidar: Lake Michigan North (MI) 6. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (MI,WI) 7. 2012 USACE NCMP Topobathy Lidar: Lake Michigan (IL,IN,MI,WI) 8. 2010 Brown County Lidar 9. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IN) 10. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (WI) 11. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (IL) 12. 2008 USACE NCMP Topobathy Lidar: Lake Michigan (MI) 13. 2007 USACE NCMP Topobathy BE Lidar: Lake Michigan (MI) and Lake Erie (PA) 14. 2007 ARRA Lidar: Lake County (IL) 15. 2006 USACE NCMP Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) The DEM was produced from the following sonar data sets: 16. 2015 USACE Detroit District, Port Washington Harbor, WI 17. 2015 USACE Detroit District, South Haven Harbor, MI 18. 2015 USACE Detroit District, Washington Island (Detroit Harbor), WI 19. 2015 USACE Detroit District, Washington Island (Jackson Harbor), WI 20. 2015 USACE Detroit District, Grand Haven Harbor, MI 21. 2015 USACE Detroit District, Pentwater Harbor, MI 22. 2015 USACE Detroit District, Pensaukee Harbor, WI 23. 2015 USACE Detroit District, St. Joseph Harbor, MI 24. 2015 USACE Detroit District, Manistee Harbor, MI 25. 2015 USACE Detroit District, Green Bay Harbor, WI 26. 2015 USACE Detroit District, Saugatuck Harbor, MI 27. 2015 USACE Detroit District, Oconto Harbor, WI 28. 2015 USACE Detroit District, White Lake Harbor, MI 29. 2015 USACE Detroit District, Manistique Harbor, MI 30. 2014 USACE Detroit District, Milwaukee Harbor, WI 31. 2014 USACE Detroit District, Frankfort Harbor, MI 32. 2014 USACE Detroit District, St. Joseph Harbor, MI 33. 2014 USACE Detroit District, Holland Harbor, MI 34. 2014 USACE Chicago District, Burns Waterway Harbor, IN 35. 2014 USACE Chicago District, Burns Small Boat Harbor, IN 36. 2014 USACE Chicago District, Michigan City, IN 37. 2014 USACE Chicago District, Waukegan Harbor, IL 38. 2014 USACE Chicago District, Calumet River, IL 39. 2014 USACE Detroit District, Menominee Harbor, MI/WI The DEM was produced from the following NPS multibeam sonar data sets: 40. 2011, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar 41. 2012, National Park Service, Sleeping Bear Dunes National Lakeshore Multibeam Sonar The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 3 meters.
These contour lines were derived and delivered for Pennsylvania from the PAMAP Quality Level 3 (QL3) LIDAR data collection between 2006 and 2008. Some post-processing has been done to the original deliverables, including merging, line smoothing, and eliminating duplicate (overlapping) data between collections. This dataset renders the contour lines with the following scale-dependent visibility: 100 foot increments between 1:200,000 and 1:100,000 | 50 foot increments between 1:100,000 and 1:30,000 | 20 foot increments between 1:30,000 and 1:5,000 | 10 foot increments between 1:5,000 and 1:1,000 | and 2 foot increments between 1:1,000 and 1:10. The lines have been smoothed using the ArcGIS Pro 3.3 Smooth Line geoprocessing tool via the Polynomial Approximation with Exponential Kernal (PAEK) and setting a 10 ft smoothing tolerance distance. The extent of this data extends slightly beyond the Pennsylvania boundary into all surrounding states to ensure complete coverage of Pennsylvania. Duplicate (overlapping) contour data between collection years and north/south state plane zones has been eliminated by splitting the data from adjacent collects at county boundaries to ensure a seamless product with no duplication or overlapping data. The contour line geometries along the county boundaries that separate different years of PAMAP data collection (2006, 2007, and 2008) do not always connect properly.
Original Dataset Geographic Extent: This data set covers approximately 3260 square miles over the Philadelphia Metro area, comprised of of 8 contiguous counties located in the states of Pennsylvania and New Jersey. The counties are: Pennsylvania - Bucks, Delaware, Montgomery, Philadelphia; New Jersey - Burlington, Camden, Gloucester, Mercer.
Original Dataset Description: Delaware Valley 20...
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
These ZIP files contains lidar derivatives including a Digital Elevation Map, Slope Analysis, and Hillshade individually encompassing Pennsylvania State Game Lands 161-200 as well as a one kilometer buffer around each region. These files were derived from lidar data provided by the state of Pennsylvania and processed using LAStools and QGIS through Project Kappa (https://zenodo.org/record/4573004). When unzipped, this file is approximately 43.2 GB in size.
For additional information, please see https://zenodo.org/record/4766351.
The Dauphin County, PA 2016 QL2 LiDAR project called for the planning, acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011) State Plane Pennsylvania South Zone, US survey feet; NAVD1988 (Geoid 12B), US survey feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to 711 individual 5,000-foot x 5,000-foot tiles. Tile names use the following naming schema: "YYYYXXXXPAd" where YYYY is the first 3 characters of the tile\'s upper left corner Y-coordinate, XXXX - the first 4 characters of the tile\'s upper left corner X-coordinate, PA = Pennsylvania, and d = \'N\' for North or \'S\' for South. Corresponding 2.5-foot gridded hydro-flattened bare earth raster tiled DEM files and intensity image files were created using the same 5,000-foot x 5,000-foot schema. Hydro-flattened breaklines were produced in Esri file geodatabase format. Continuous 2-foot contours were produced in Esri file geodatabase format. Ground Conditions: LiDAR collection began in Spring 2016, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 84 control points (24 calibration control points and 60 QC checkpoints). These were used to calibrate the LIDAR to known ground locations established throughout the project area.
Lake Erie Watershed 2015 Ortho/LiDAR/Hydro Project To better understand one of the state's most vital natural resources and accurately plan for the future, the Pennsylvania Department of Environmental Protection (PADEP), through grant funding provided to the Pennsylvania Sea Grant (PASG) College Program, partnered with Woolpert to acquire imagery and lidar data for the entire Pennsylvania Lake...
MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://lidar.geodata.md.gov/imap/rest/services/Kent/MD_kent_shadedRelief_RGB/ImageServer
This dataset provides 30-meter gridded estimates of aboveground biomass (AGB), forest canopy height, and canopy coverage for Maryland, Pennsylvania, and Delaware in 2011. Leaf-off LiDAR data were combined with high-resolution leaf-on agricultural imagery in a model-based stratification that was used to select 848 sampling sites for AGB estimation. Field-based estimates were then related to LiDAR height and volume metrics through random forest regression models across three physiographic regions. Spatial errors were estimated at the pixel level using standard prediction intervals to assess the accuracy of the modeling approach. Estimates of biomass were further validated against the permanent network of FIA plots and compared with existing coarse resolution national biomass maps.
Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information
These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the Sea Level Rise and Coastal Flooding Impacts Viewer. It depicts potential sea level rise and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at sea level rise and coastal flooding impacts. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The Sea Level Rise and Coastal Flooding Impacts Viewer may be accessed at: https://coast.noaa.gov/slr. This metadata record describes the Maryland, West digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer described above. This DEM includes the best available lidar known to exist at the time of DEM creation that met project specifications. This DEM includes data for Anne Arundel, Baltimore, Calvert, Howard, and Prince George's Counties and Baltimore City. The DEM was produced from the following lidar data sets: 1. 2011 Anne Arundel County, MD Lidar 2. 2015 Sandy Supplemental MD/PA QL2 Lidar (Baltimore City) 3. 2015 Baltimore County, MD Lidar 4. 2011 Calvert County, MD Lidar 5. 2011 Howard County, MD Lidar 6. 2014 USGS Hurricane Sandy Supplemental for National Capital Region (NCR) The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88, Geoid12B) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 3 meters.
Original Dataset Geographic Extent: This data set is part of a larger collection of the Delaware Valley project that covers approximately 3260 square miles over the Philadelphia Metro area, comprised of of 8 contiguous counties located in the states of Pennsylvania and New Jersey. This data set was a re-flight, flown on November 25, 2015, after the initial collection of the larger data set in A...
Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information
MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://lidar.geodata.md.gov/imap/rest/services/Talbot/MD_talbot_slope_m/ImageServer
The storm-induced Coastal Change Hazards component of the National Assessment of Coastal Change Hazards (NACCH) project focuses on understanding the magnitude and variability of extreme storm impacts on sandy beaches. Light detection and ranging (lidar)-derived beach morphologic features such as dune crest, toe and shoreline help define the vulnerability of the beach to storm impacts. This dataset defines the elevation and position of the seaward-most dune crest and toe and the mean high-water shoreline derived from the 2001 Gulf Coast National Oceanic and Atmospheric Administration/U.S. Geological Survey/National Aeronautics and Space Administration (NOAA/USGS/NASA) Airborne Topographic Mapper (ATM) lidar survey. Beach width is included and is defined as the distance between the dune toe and shoreline along a cross-shore profile. The beach slope is calculated using this beach width and the elevation of the shoreline and dune toe.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
Terrain data includes digital elevation models, LIDAR derived contours, LIDAR three-dimensional spot elevations and breaklines, field surveyed ground elevations and data tables for this study area.
This dataset consists of classified LiDAR (Light Detection and Ranging) elevation points produced by the PAMAP Program. PAMAP data are organized into blocks, which do not have gaps or overlaps, that represent 10,000 feet by 10,000 feet on the ground. The coordinate system for blocks in the northern half of the state is Pennsylvania State Plane North (datum:NAD83, units: feet); blocks in the sou...