{"action":"create","ckan_id":null,"date_created":"Wed, 06 Aug 2025 04:55:59 GMT","date_finished":null,"harvest_job_id":"5871908a-b1fb-4808-b4a9-f0c5cd9afb74","harvest_source_id":"7b1004d7-9ccd-4bfa-91fc-d37e32ddef6b","id":"5beebc1f-f0a9-4a94-afe3-9b476efc256a","identifier":"http://www.pasda.psu.edu/metadata/harvest/2020_ERDC_PA.xml","parent_identifier":null,"source_hash":"55b66577c167a19084c8f39521ff15a6d66e1f80c453b779f1b6f25cefa9c7f6","source_raw":"2020 USACE ERDC Topobathy Lidar: Allegheny River, Pennsylvaniaremote-sensing imagehttp://coast.noaa.gov/dataviewerUSACE 2020https://www.pasda.psu.edu/-79.441241-79.37747741.70317241.549278These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided \"as is\" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.Resource constraints\r\nLegal constraints\r\nOther constraints\r\nThese data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.\r\nLimitations of use\r\nThese data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.\r\n Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362Area of Interest: Allegheny River, 15 miles, north of Clarion County, in Forest and Warren counties\r\nThese files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system and topographic lidar elevations generated from data collected using a Teledyne ALTM Galaxy PRIME sensor. 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 generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 National Adjustment of 2011 (NAD83 (2011). Vertical positions are referenced to the NAD83 (2011) ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12B model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data are sub-divided into a series of LAS files, which are tiled into 1-km by 1-km boxes defined by the Military Grid Reference System. The LAS file index is provided by the shape files, \"MGRS_1km_17T.shp \", and the numbers used to identify files are in the \"Box\" field of the shape file. The data file naming convention is based on the year, effort, area, \"Box\" number and data product type. An example file name is \"2020_ERDC_PA_17TPF2793_1mGrid.tif\", where 2020 is the year of data collection, ERDC is the effort under which data were collected, PA is the area of data collection, 17TPF2793 is the \"Box\" number and 1mGrid is the data product type.This data was collected by the USACE in support of USACE Engineer Research and Development Center's Environmental Labratory forfor inland Bathymetry research. Paid for by the US Army Engineer Reseach and Development Center's Ecosystem Managment and Restoration Research Program, https://emrrp.el.erdc.dren.mil/ For More Information See: https://www.pasda.psu.edu/download/usace/2020_ERDC_PA/ancillaryJALBTCXData Production Managermailing and physical address
7225 Stennis Airport Rd., STE 100
KilnMS39556UNITED STATES228-252-1131JALBTCX@usace.army.mil2020ISO 19115 Topic Category imageryBaseMapsEarthCoverRasterPixel3400001000000.9996-81.00.0500000.00.0coordinate pair0.0000000022200241645009560.000000002220024164500956meterD North American 1983GRS 19806378137.0298.25722210120231129FGDC Content Standard for Digital Geospatial MetadataFGDC-STD-001-1998local timePennsylvania Spatial Data Access (PASDA)mailing and physical address
115 Land and Water building
University ParkPennsylvania16802United States(814) 865 - 8792pasda@psu.eduThese files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system and topographic lidar elevations generated from data collected using a Teledyne ALTM Galaxy PRIME sensor. 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 generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 National Adjustment of 2011 (NAD83 (2011). Vertical positions are referenced to the NAD83 (2011) ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12B model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data are sub-divided into a series of LAS files, which are tiled into 1-km by 1-km boxes defined by the Military Grid Reference System. The LAS file index is provided by the shape files, \"MGRS_1km_17T.shp \", and the numbers used to identify files are in the \"Box\" field of the shape file. The data file naming convention is based on the year, effort, area, \"Box\" number and data product type. An example file name is \"2020_ERDC_PA_17TPF2793_1mGrid.tif\", where 2020 is the year of data collection, ERDC is the effort under which data were collected, PA is the area of data collection, 17TPF2793 is the \"Box\" number and 1mGrid is the data product type.2020 USACE ERDC Topobathy Lidar: Allegheny River,Pennsylvania<DIV STYLE=\"text-align:Left;\"><DIV><DIV><P><SPAN>None</SPAN></P></DIV></DIV></DIV>202311291159050015000000050001.0FGDCPennsylvania Spatial Data Access (PASDA)mailing and physical address
115 Land and Water building
University ParkPennsylvania16802United States(814) 865 - 8792pasda@psu.edu The USER shall indemnify, save harmless, and, if requested, defend those parties involved with the development and distribution of this data, their officers, agents, and employees from and against any suits, claims, or actions for injury, death, or property damage arising out of the use of or any defect in the FILES or any accompanying documentation. Those parties involved with the development and distribution excluded any and all implied warranties, including warranties or merchantability and fitness for a particular purpose and makes no warranty or representation, either express or implied, with respect to the FILES or accompanying documentation, including its quality, performance, merchantability, or fitness for a particular purpose. The FILES and documentation are provided \"as is\" and the USER assumes the entire risk as to its quality and performance. Those parties involved with the development and distribution of this data will not be liable for any direct, indirect, special, incidental, or consequential damages arising out of the use or inability to use the FILES or any accompanying documentation.\r\n","source_transform":null,"status":"error"}