2013 MDEQ-FEMA Rankin-Simpson Co. Lidar Survey
OCM Partners
Data Set
(DS)
| ID: 49824
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49824
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2013 MDEQ-FEMA Rankin-Simpson Co. Lidar Survey |
---|---|
Short Name | ms2013_mdeq_fema_rankinsimpson_m2595_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-11-23 |
* » Abstract |
Fugro as a subconsultant to MGI was authorized to undertake this project, as a part of Work Order No. 112, dated November 1, 2012, issued to MGI in accordance with the terms and conditions of the Professional Services Agreement between MGI and the Mississippi Department of Environmental Quality (MDEQ), dated February 17, 2004. This Light Detection and Ranging (LiDAR) dataset is a survey of the Middle Pearl-Strong River Basin in Rankin and Simpson Counties, Mississippi. The project area consists of approximately 973 square miles. |
* Purpose |
The acquisition, processing, and delivery of classified point cloud data, LiDAR intensity data, hydro-flattened breaklines, and bare earth DEM covering Middle Pearl-Strong River Basin, MS was a coordinated effort between Fugro and MGI to support MDEQ's Mississippi Digital Earth Model (MDEM) program. The mission of MDEQ is to safeguard the health, safety, and welfare of present and future generations of Mississippians by conserving and improving our environment and fostering wise economic growth through focused research and responsible regulation. |
Notes |
10468 |
Other Citation Details | |
• Supplemental Information |
A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/supplemental/ms2013_mdeq_fema_rankinsimpson.kmz The Fugro Earthdata reports for Rankin-Simpson County lidar collection are available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/supplemental/ms2013_mdeq_fema_rankinsimpson.pdf & https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/supplemental/ms2013_mdeq_fema_rankinsimpson_accuracy.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Bare Earth |
None | Ground Control |
None | Land Surface |
None | Light Detection and Ranging |
None | Point Cloud |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | lead off |
None | Winter |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | las |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of the following: MDEQ, Fugro, NOAA, the Office for Coastal Management, or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-11-23 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2013-11-23 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2013-11-23 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2013-11-23 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -90.2566139 |
---|---|
* » E° Bound | -89.7281777 |
* » N° Bound | 32.5947464 |
* » S° Bound | 31.9160127 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-06 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-07 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-31 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 4
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-02-01 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2595 ; |
• » Data Access Constraints |
None |
• Data 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2595 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/supplemental/ms2013_mdeq_fema_rankinsimpson.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the extent of the Rankin-Simpson County area survey. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2017-03-20 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
Description |
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. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
LiDAR data horizontal accuracy is met as contracted.; Quantitative Value: 1.0 meters, Test that produced the value: Horizontal Accuracy was not reported as tested. |
Vertical Positional Accuracy |
See accuracy assessment report at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2595/supplemental/ms2013_mdeq_fema_rankinsimpson_accuracy.pdf ; Quantitative Value: 0.08 meters, Test that produced the value: Accuracy assessed on 20130613. Based on the vertical accuracy testing conducted by Fugro Earthdata were able to determine vertical accuracy RMSE of 18.5 cm. Vertical accuracy tested at 95% confidence interval to be 0.27 survey ft. (8.2 cm) under NSSDA calculation standards. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure |
Cloud Cover: 0 |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
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. |
Conceptual Consistency |
LiDAR flight lines have been examined to ensure that there was at least 50% sidelap, there are no gaps between flightlines, and overlapping flightlines have consistent elevation values. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
The technician processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. The technician used commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift- mini project. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the result and made any necessary additional adjustment until it is acceptable for the mini project. Once the boresight angle calculation is complete for the mini project, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technician utilized commercial and proprietary software packages to analyze the matching between flight line overlaps for the entire lift to ensure that systematic errors are minimized for the lift and the results meet project requirements. Once all lifts are completed with boresight adjustment individually, the technician checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The technician ran a final vertical accuracy check of the boresighted flight lines against the surveyed ground control points after the z correction to ensure the accuracy requirement of 18.5cm RMSE was met; see Attachment B: Accuracy Assessment Report for results. Pre-processing. Once boresighting is complete for the project, the project was set up for automatic classification first. The LiDAR data was cut to production tiles. The flight line overlap points, Noise points and Ground points were classified automatically in this process. |
Process Date/Time | 2013-06-13 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Post-processing. Fugro has developed a unique method for processing LiDAR data to identify and re-classify elevation points falling on vegetation, building, and other above ground structures into separate data layers. The steps are as follows: Fugro utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter within local area or was corrected during the manual filtering process. Interactive editing was completed in visualization software which provides manual and automatic point classification tools. Fugro utilized commercial and proprietary software for this process. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. The technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. All LAS tiles went through peer review after the first round of interactive editing was finished. This helps to catch misclassification that may have been missed by the interactive editing. After the manual editing and peer review, and finalization of bare earth filtering, all tiles went through another final automated classification routine. This process ensures only the required classifications are used in the final product (all points classified into any temporary classes during manual editing were then re-classified into the project specified classifications). The classified LiDAR point cloud work tiles went through a water classification routine based on the collected water polygons. Also, during this process, the points originally classified as flight line overlap went through an automated classification to filter ground points and low points inside overlap areas. |
Process Date/Time | 2013-06-13 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
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 West 2302, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid12a 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 West 2302) to a Geographic Coordinate system (NAD83). 2. The topographic laz files' horizontal units were converted from feet to decimal degrees. 3. The topographic laz files were cleaned of erroneous bad elevations. 4. The topographic laz files' were converted from NAVD88 elevations to NAD83 ellipsoidal elevations using Geoid12a 5. Classification 11 was moved to classification 12 due to OCM system requirements (OCM class 11 is reserved for bathymetric points, though these points are truly overlap points, Class 12). |
Process Date/Time | 2013-11-23 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 49824 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:22+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:11+0000 |
Metadata Record Published | 2022-03-16 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|