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
Citation
Title 2011 MDEQ Tennessee-Tombigbee Waterway Lidar Survey
publication Date
2013-09-16
presentationForm
LAS
cited responsible party
-
publisher
organisation Name
NOAA's Ocean Service, Office for Coastal Management (OCM)
Contact information
Address
, Charleston, SC
cited responsible party
-
originator
organisation Name
Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office
for Coastal Management (OCM)
cited responsible party
-
originator
organisation Name
Mississippi Department of Environmental Quality (MDEQ)
other Citation Details
Cinergi keyword enhanced at Mon Nov 14 14:31:47 UTC 2016
purpose:
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.
Browse image (thumbnail):
thumbnail file name:
file type: kmz
thumbnail file description:
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
Resource language:
eng; USA
Resource progress code:
completed
Resource Maintenance Information
maintenance or update frequency:
asNeeded
Constraints on resource usage:
Constraints
Use limitation statement:
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.
Constraints on resource usage:
Legal Constraints
use constraint:
otherRestrictions
Other constraints
Use Constraints: 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.
Constraints on resource usage:
Legal Constraints
Access Constraints
otherRestrictions
Other constraints
Access Constraints: None
Spatial representation type code:
vector
Resource extent
Geographic Extent
Geographic Bounding Box
westBoundLongitude
-89.639595
eastBoundLongitude
-87.274625
northBoundLatitude
34.514993
southBoundLatitude
33.372751
Temporal Extent
Additional information on resource:
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: ftp://coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/2560/supplemental/ms2011_mdeq_tenn_tombigbee.KMZ
The MDEQ Tennessee-Tombigbee report may be accessed at: ftp://coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/2560/supplemental/ms2011_mdeq_tenn_tombigbee.pdf
Credits:
Bryan Daniel (Atlantic Group), Josh Helton (Atlantic Group), Patrick Robinson (Atlantic Group), Paul Weyant (Atlantic Group),
Barbara Yassin (MDEQ)
source description
Source Contribution: Delivery of LiDAR data, Contours data, Digital Elevation Model (DEM) data, and Breaklines.Source Type
digital tape media
source citation
Title Tennessee-Tombigbee Study Basin, Northeastern Mississippi
publication Date
2012-07-31T1200
Edition 1
presentationForm
mapDigital
cited responsible party
-
originator
organisation Name
The Atlantic Group
Resource extent
Temporal Extent
2012-07-31T1200
AbsoluteExternalPositionalAccuracy
name Of Measure Horizontal Positional Accuracy Report
evaluation Method Description
LiDAR data horizontal accuracy is met as contracted. The Nominal Point Spacing Value for the final LiDAR is 3.2 ft (0.97 m).
AbsoluteExternalPositionalAccuracy
name Of Measure Horizontal Positional Accuracy
measure Description
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).
Quantitative Result
result value 0.649
value Units
AbsoluteExternalPositionalAccuracy
name Of Measure Vertical Positional Accuracy Report
evaluation Method Description
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.
AbsoluteExternalPositionalAccuracy
name Of Measure Vertical Positional Accuracy
measure Description
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).
Quantitative Result
result value 0.07
value Units
Completeness Commission
evaluation Method Description
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.
Completeness Omission
evaluation Method Description
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.
ConceptualConsistency
measure Description
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.
notes: This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version
FGDC-STD-001-1998) using the 2012-06-20T17:21:00 version of the FGDC RSE to ISO 19115-2 transform.
Metadata contact
-
pointOfContact
organisation Name
NOAA Office for Coastal Management
Contact information
Telephone
Voice 843-740-1202
Address
2234 South Hobson Avenue, Charleston, SC, 29405-2413