49820 ms2011_mdeq_tenn_tombigbee_m2560_metadata Data Set Published / External 49401 Lidar - partner (no harvest) Project Completed 2013-09-16 Collect and deliver high-density elevation point data derived from multiple-return light detection and ranging (LiDAR) measurements for use in supporting topographic analysis, including applications such as flood plain mapping. The Nominal Point Spacing Value for the final lidar is 3.2 ft (~1 m). Deliver LiDAR Bare Earth and Contour lines within the areas designated in areas of Clay, Itawamba, Monroe, and Lowndes Counties to aid in visual interpretation of Flood Basin elevations and for addition to the MDEM elevation dataset. Comply with mapping guidelines and specifications as stated in the FEMA Procedure Memorandum No. 61 Updating DFIRM maps, hydrologic modeling, transportation routing, floodplain mapping and assessment of natural hazards. Furthermore, the data sets can be utilized by the general public including engineers, surveyors, appraisers and others interested parties to evaluate transportation and land use planning. 10464 Reflective surface data represents the DEM created by laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the interaction of the surface materials with laser energy at the wavelength transmitted by the sensor. Points are classified as water, bare ground or not bare ground to support creation of a bare earth model from the data. A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.KMZ The MDEQ Tennessee-Tombigbee report may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.pdf Theme ISO 19115 Topic Category elevation Theme Bare Earth Theme Ground Control Theme Land Surface Theme Light Detection and Ranging Theme Point Cloud Temporal Fall Temporal Winter Temporal lead off Office for Coastal Management Charleston SC Data Set As Needed las Any conclusions drawn from the analysis of this information are not the responsibility of the following: MDEQ, The Atlantic Group, NOAA, the Office for Coastal Management, or its partners. Bryan Daniel (Atlantic Group), Josh Helton (Atlantic Group), Patrick Robinson (Atlantic Group), Paul Weyant (Atlantic Group), Barbara Yassin (MDEQ) Data Steward 2013-09-16 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Distributor 2013-09-16 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Metadata Contact 2013-09-16 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Point of Contact 2013-09-16 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Ground Condition -89.639595 -87.274625 34.514993 33.372751 Discrete 2011-03-22 Discrete 2011-03-23 Discrete 2011-03-24 Discrete 2011-03-24 Discrete 2011-03-24 Discrete 2011-04-01 Discrete 2011-04-03 Discrete 2011-04-09 Discrete 2011-04-10 Discrete 2011-04-11 Yes Unclassified This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2560 ; None Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. These data depict the heights at the time of the survey and are only accurate for that time. https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2560 Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/index.html Bulk Download Simple download of data files. https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.KMZ Browse Graphic Browse Graphic kmz This graphic shows the lidar coverage for portions of the following counties in Minnesota: Olmsted County, Wabasha County, Goodhue County, St. Louis County, Fillmore County, Pine County, Kanabec County, Morrison County, Mille Lacs County, Waseca County, Blue Earth County, Steele County, Dodge County, Nicollet County, Sibley County, Freeborn County, Faribault County, Mower County, Isanti County, Anoka County, Ramsey County, Dakota County, Wright County, Scott County, Washington County, Rice County, Hennepin County, Le Sueur County, Carver County, Benton County, Sherburne County, Chisago County, Koochiching County, Itasca County, Crow Wing County, Aitkin County, Carlton County, Winona County, Houston County, Cook County, Lake County https://coast.noaa.gov Online Resource https://coast.noaa.gov/dataviewer Online Resource 2016-05-23 Date that the source FGDC record was last modified. 2017-11-14 Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. 2018-02-08 Partial upload of Positional Accuracy fields only. 2018-03-13 Partial upload to move data access links to Distribution Info. LiDAR data horizontal accuracy is met as contracted. The Nominal Point Spacing Value for the final LiDAR is 3.2 ft (0.97 m).; Quantitative Value: 0.649 meters, Test that produced the value: Horizontal point accuracy is a function of angular origination of the pulse; IMU orientation; the scanner encoder and ranging function and will vary depending on the proposed point density selected for the collection. Statistically, the error is roughly 1/3 of the illuminated foot print on the ground and is a function of the beam divergences. This gives a final horizontal accuracy value of 2.13 feet (0.649 m). LiDAR vertical data accuracy determination shall employ the National Standard for Spatial Data Accuracy (NSSDA).The Nominal Point Spacing Value for the final LiDAR is 3.2 ft.; Quantitative Value: 0.07 meters, Test that produced the value: Based on the vertical accuracy testing conducted by The Atlantic Group, LLC using NSSDA methodology, the dataset tested for vertical accuracy at 95% confidence level in open terrain, based on open terrain. This gives a final vertical accuracy value of 0.24 feet (0.07 m). Cloud Cover: 0 All data is complete to standards as specified. LIDAR raster data is visually inspected for completeness to ensure that any gaps between flight lines of required collection area. LIDAR is self-illuminating and has minimal cloud penetration capability. Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes. Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface. QC/QA process includes review of flight alignments and completeness of supporting data. The MDEQ or its designee may perform additional QC/QA testing. The root mean square error (RMSE) is used to estimate both horizontal and vertical accuracy. RMSE is the square root of the average of the set of squared differences between dataset coordinate values and coordinate values from an independent source. Bare-earth processed data for this acquisition block comply with the following accuracy requirements for Artifact/Feature removal: artifacts - 90%; outliers - 95%; vegetation - 95%; buildings - 98%. All LAS formatted LIDAR data are validated using commercial GIS software to ensure proper formatting and loading before delivery. This validation procedure ensures that data on delivery media is in correct physical format and is readable. Higher accuracy for identical points. If those differences are normally distributed and average zero, 95 percent of any sufficiently large sample should be less than 1.96 times the RMSE. Therefore 9-centimeter RMSE can be referred to as "18-centimeter accuracy at the 95-percent confidence level." Following that convention, the vertical accuracy of any DEM is defined as 1.96 times the RMSE of linearly interpolated elevations in the DEM, as compared with known elevations from high-accuracy test points. DEMs should have a maximum RMSE as specified to meet its required vertical accuracy. Tennessee-Tombigbee Study Basin, Northeastern Mississippi 2012-07-31 Delivery of LiDAR data, Contours data, Digital Elevation Model (DEM) data, and Breaklines. | Source Geospatial Form: vector digital data | Type of Source Media: digital tape media 1 The ABGPS, IMU, and raw Optech LiDAR data are integrated into the Optech post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 formats can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and NAVD88 2004.65 vertical datum. 2011-06-01T00:00:00 2 The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as define by the LAS 1.2 specification. The data was classified as follows: Class 1 = Unclassified. This class includes all non-ground classified points. Class 2 = Ground. Class 7 = Low Points. Class 9 = water. Class 9 = water. Class 10 = Ignored. Class 11 = Overlap Points. 2011-06-01T00:00:00 3 Conversion from Geodetic coordinates NAD83 into Mississippi state plane zone 16 East using NAD83 and conversion from ellipsoid heights (us feet) into orthometric heights using NAVD88 (US Survey Foot). Files are orthogonally tiled based to a 1500m x1500m extent, and labeled with a "Tile_ID" attribute. 2011-06-01T00:00:00 4 The NOAA Office for Coastal Management (OCM) received topographic files in .laz format from the Mississippi Department of Environmental Quality (MDEQ). The files contained lidar elevation measurements. The data were received in Mississippi State Plane East 2301, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic laz files were converted from a Projected Coordinate System (Mississippi State Plane East 2301) to a Geographic Coordinate system (NAD 83). 2. The topographic laz files' horizontal units were converted from feet to decimal degrees. 3. The topographic laz files were cleaned of error points above 535 ft and below 100 ft. 4. The topographic laz files' were converted from NAVD88 elevations to NAD83 ellipsoidal elevations using Geoid03 5. Classification 11 was moved to classification 12 due to OCM system requirements (class 11 is reserved for bathy points, though these points are overlap points, Class 12). 2013-09-16T00:00:00 gov.noaa.nmfs.inport:49820 Anne Ball 2017-11-15T15:22:31 SysAdmin InPortAdmin 2022-08-09T17:11:36 2022-03-16 OCM Partners OCMP 1002 Public No No 2022-03-16 1 Year 2023-03-16