2009-2010 USACE Vicksburg District Lidar: Mississippi Phase II
OCM Partners
Data Set
(DS)
| ID: 49818
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49818
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2009-2010 USACE Vicksburg District Lidar: Mississippi Phase II |
---|---|
Short Name | ms20092010_usace_phaseII_m2600_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-12-20 |
* » Abstract |
Phase two will consist of post processing of the data collected. Aeroquest Optimal, Inc. shall process the digital elevation data from a precision airborne (LIDAR) survey within the entire project area. The proposed project area is approximately 6.3 million acres. The purpose of the survey is to obtain measurements of the bare ground surface, as well as top surface feature elevation data for providing geometry input to USACE hydraulic modeling program. This project for USACE, Vicksburg District was to provide digital orthophotography using DMC imagery for approximately 4,120 square miles located in NW Mississippi at a 2-foot pixel resolution. Original contact information: Contact Name: Elijah C. Hunt Contact Org: U.S. Army Corps of Engineers, Vicksburg District Phone: (601) 631-7040 Email: elijah.c.hunt@us.army.mil |
* Purpose |
The purpose of this survey is to provide the Vicksburg District with bare earth and top surface elevation data for providing geometry input to USACE hydraulic modeling programs. |
Notes |
10462 |
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/2600/supplemental/ms2009_2010_usace_phaseII.KMZ Reports explaining collection and quality assurance is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2600/supplemental/ms2009_2010_usace_phaseII.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | LAZ |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* 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 |
LiDAR points in LAZ format (ASPRS Classes 1,2) |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of Aeroquest Optimal, Inc., MDEQ, USACE, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-12-20 |
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-12-20 |
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-12-20 |
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-12-20 |
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.0886487 |
---|---|
* » E° Bound | -88.8334027 |
* » N° Bound | 34.981004 |
* » S° Bound | 33.6759277 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2009-12-17 |
End | 2010-07-09 |
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=2600 ; |
• » 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=2600 |
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/2600/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 |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
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/2600/supplemental/ms2009_2010_usace_phaseII.KMZ |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2009-2010 Phase II collection area in Mississippi. |
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 | 2016-05-23 |
---|---|
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 |
Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID03). |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Expected accuracies are not tested accuracies. OPTECH ALTM 3100 LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/2,000th of the flight height, which, in the instance of this particular project, was 3,280 U.S. survey feet (1,000 meters) AGL, giving a horizontal tolerance of less than 1.640 U.S. survey feet (0.500 meters). OPTECH ALTM 3100EA LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/5,500th of the flight height which, in the instance of this particular project, was 3,280 U.S. survey feet (1,000 meters) AGL, giving a horizontal tolerance of less than 0.596 U.S. survey feet (0.182 meters). OPTECH ALTM Gemini LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/11,000th of the flight height, which, in the instance of this particular project, was 5,905 U.S. survey feet (1,800 meters) AGL, giving a horizontal tolerance of less than 0.537 U.S. survey feet (0.164 meters). Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy are less than 1 meter. Not tested therefore horizontal accuracy is assumed as 1.0 m. ; Quantitative Value: 1.0 meters, Test that produced the value: See LiDAR data report. |
Vertical Positional Accuracy |
The LiDAR data was tested against control points established using RTK GPS techniques. Six-hundred and seventy-nine (679) test points were collected throughout the project area in several vegetation categories. The RMSE calculations were performed on the bare-earth, orthometric surface and determined for each of the four LiDAR acquisition areas separately. ; Quantitative Value: 0.11 meters, Test that produced the value: The following statements are derived in accordance with the ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data (Flood, M., 2004). Tested 0.365 U.S. survey feet (0.111 meters) fundamental vertical accuracy at the ninety-five percent confidence level in open terrain using RMSEz x 1.9600. Tested 0.431 U.S. survey feet (0.131 meters) consolidated vertical accuracy at the ninety-five percent confidence level in open terrain, high grass and trees using RMSEz x 1.9600. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
LiDAR data has been collected and processed for all areas within the project study area. |
Conceptual Consistency |
Analysis of parallel acquisitioned EO shows a RMS of 1.801ft , 2.101 ft and 3.100 ft for XYZ, respectively. |
» 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 |
During acquisition, two base stations were used to support the precise positioning and orientation of the LiDAR sensor head. At times an additional base station set at the Oxford Airport was used as a back-up. The base stations were positioned so that the aircraft would be no further than 20-miles from a single base station at any time during the flight and were placed on the control points established by Maptech during the ground control phase of the project. The LiDAR acquisition commenced on December 17, 2009 and was completed on March 5, 2010. Initial processing of the LiDAR data determined that reflights were necessary; in part because of sensor or base station malfunctions. The reflights occurred between June 27, 2010 and July 9, 2010. To achieve better penetration of the vegetation during the reflights, two passes were conducted over the reflight area; one in each direction. Detailed flight information and flight logs can be found in the separate Flight Report submitted with the project. |
Process Date/Time | 2010-03-05 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
For redundancy and accuracy purposes, the airborne GPS data were processed from two base stations using POSGPS from Applanix, Inc. The agreement between a minimum of two solutions checked or combined between a minimum of two stations was better than 10 cm in each of X, Y, and Z. These trajectories were used in the processing of the inertial data. The inertial data were processed using POSProc from Applanix, Inc. This software produces an SBET ("smooth best estimate of trajectory") using the GPS trajectory from POSGPS and the roll, pitch and heading information recorded by the POS (Position Orientation System). DASHMap uses the SBET to generate a set of data points for each laser return in the LAS file format. Each data point is assigned an echo value so it can be segregated based on the first and last pulse information. This project's data were processed in strip form, meaning each flight line was processed independently. Processing the lines individually provides the data analyst with the ability to QC the overlap between lines. Each strip was then imported into a project using TerraScan (Terrasolid, Ltd.) and the project management tool GeoCue (GeoCue Corp.). By creating a project the various flightlines are combined while breaking the dataset as a whole into manageable pieces. This process also converts the dataset from the geographic coordinate system (NAD83) to the State Plane Coordinate System (NAD83), Mississippi West, Feet, and utilizing standard ESRI transformations. The ellipsoid height values were converted to NAVD88, Feet, orthometric values using Geoid03, provided by NGS. Individual lines were then checked against adjacent lines and intersecting control lines to ensure a cohesive dataset. The data from each line were then combined and LiDAR intensity images were produced to visually check the horizontal positioning of the LiDAR data. Stereo pairs were generated from the LiDAR intensity data using Geocue and LiDAR1CuePac (Geocue Corp.). LiDARgrammetry was then utilized to collect breaklines where necessary along hydro features to support the contour generation. These breaklines were collected as a 3D element in the MicroStation (Bentley Systems, Inc.) environment utilizing ISSD (Z/I Imaging). A Triangular Irregular Network (TIN) was generated using the final surface data. Contours were then created from the TIN utilizing TerraModeler (Terrasolid, Ltd.). |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received topographic files in text format from the Mississippi Department of Environmental Quality (MDEQ). The files contained lidar easting, northing and elevation. The data were received in Mississippi State Plane West 2302, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid03 model. The vertical and horizontal units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII files were converted from txt format to las format using LASTools' txt2las 2. The LAS tiles were retiled to remove the buffer, then duplicate points were removed 3. The LAS tiles were then run through LASGround in order to extract surface classifications. 4. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 5. The las files' vertical units were converted from feet to meters, removing bad elevations. 6. The las files were converted from a Projected Coordinate System (MS SP West) to a Geographic Coordinate system (NAD83) 7. The las files' horizontal units were converted from feet to decimal degrees and converted to laz format. |
Process Date/Time | 2013-12-20 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 | 49818 |
---|---|
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 |
---|