2016 Martin County QL2 Lidar DEM (FL)
OCM Partners
Data Set
(DS)
| ID: 49422
| Published / External
Created: 2017-11-15
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 49404
ID: 49422
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2016 Martin County QL2 Lidar DEM (FL) |
---|---|
Short Name | fl2016_martin_county_dem_m6254_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2017-03-15 |
* » Abstract |
Martin County FL QL2 Lidar Acquisition and Processing Production Task Task Order No. G14PS00574 Woolpert Order No. 76001 Contractor: Woolpert, Inc. This task is for a high resolution data set of lidar covering the total task order area of Martin County(566 square miles). The lidar data was acquired and processed under the requirements identified in this task order. The data delivered in this task order is compliant with US. Geological Survey National Geospatial Program Lidar Base Specification Version 1.2. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, 4 feet pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and Intensity data delivered in 5,000ft x 5,000ft tiles. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, bridge abutment breakline data, control data, and tile index provided as ESRI shapefile, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Please note that tile 29261 is a coastal tile and contains no lidar points. The data boundary intersects this tile and a hydro breakline was digitized based on this boundary. For this reason a hydro-flattened DEM IMG was generated. There will be no LAS 1.4 or Intensity Tiff for tile 29261. The DEM IMG file count is 768. The LAS 1.4/Intensity Tiff file count is 767. Lidar data acquired during mean low/low tide. Polygon-Z hydro breaklines contain islands as donut-holes. Ground conditions: Water at normal levels; no unusual inundation; leaf off. In addition to the bare earth Digital Elevation Models (DEMs), the lidar point data are also available. These data are available for download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6233 Breaklines created from the lidar are also available by request via email at: coastal.info@noaa.gov. The DEM and breakline products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA, OCM or its partners. Original contact information: Contact Org: Woolpert Phone: (937) 461-5660 |
* Purpose |
The purpose of this County Wide 3D Elevation Program is to support primary and secondary engineering, surveying, flood plain/risk management, emergency services/response, GIS, conservation land restorations, environmental protection, natural and man-made infrastructure improvement initiatives. Data will be utilized for mapping, planning and design on various current and future local, federal, regional, state and water management regional impact initiatives such as FEMA/Flood Plain Mapping, Water Quality, C44 Everglades & Cypress Creek restoration projects, Indian River Lagoon/St. Lucie Estuary environmental protection, beach re-nourishment, flood resilience and mitigation, urban/rural infrastructure planning and improvements projects. |
Notes |
12086 |
Other Citation Details | |
• Supplemental Information |
The Martin County QL2 Lidar Project Report may be accessed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/6233/supplemental/fl2016_martin_county_m6233_lidar_report.pdf The Martin County QL2 Lidar Project Survey Control Report may be accessed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/6233/supplemental/fl2016_martin_county_m6233_survey_report.pdf The lidar point data that thes DEMs were created from may be accessed here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6233 Breaklines created from the lidar point data, in either gdb or gpkg format, may be accessed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/6233/breaklines. The DEM and breakline products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA, OCM or its partners. |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
None | DEM |
None | IMG |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA |
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 | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Woolpert prepared the original data as set forth in the Scope of Services, in accordance with reasonable care and due diligence as set forth in this Agreement, however, due to the easily alterable nature of electronic media, files, documents, and other deliverables, Woolpert, Inc. makes no warranties, either expressed or implied, with respect to the accuracy, completeness, merchantability, or fitness for any particular purpose, including, but not limited to, use of any/all data as described within this metadata file, by any user of this data. Any use will be at the end-user's sole risk. Any conclusions drawn from the analysis of this information are not the responsibility of Woolpert, Inc., Martin County, Florida, NOAA, the NOAA Office for Coastal Management (OCM) or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2017-03-15 |
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 | 2017-03-15 |
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 | 2017-03-15 |
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 | 2017-03-15 |
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 | -80.752363 |
---|---|
* » E° Bound | -80.052245 |
* » N° Bound | 27.299831 |
* » S° Bound | 26.886398 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2016-01-16 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2016-01-18 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2016-01-23 |
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? | Yes |
---|---|
Vector Representation Used? | |
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 | EPSG:6360 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | EPSG:6438 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
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=6254; |
• » Data Access Constraints |
No restrictions apply to this data. |
• Data Use Constraints |
None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. End users should be aware some areas of this project are located in areas exhibiting swamp-like and/or heavily vegetated conditions. In such areas, placement of hydrographic features developed as part of the hydrologic breakline dataset may appear ambiguous. Users should not use these data for critical applications without a full awareness of its limitations. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | 2023-08-15 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6254 |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2017-03-15 - Present) |
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) | Zip |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2023-08-15 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/FL_Martin_County_DEM_2016_6254/index.html |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2017-03-15 - Present) |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | GeoTIFF |
Distribution Format | GeoTIFF |
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/dataregistry |
---|---|
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/geoid12b/6233/supplemental/fl2016_martin_county_m6233.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar footprint for the 2016 Martin County Florida lidar project along the east coast of Florida. |
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-13 |
---|---|
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-02-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 |
Microsoft Windows 7 Version 6.1 (Build 7600); ArcMap 10.3; ArcCatalog 10.3; TerraScan ver. 16.01; TerraModeler ver. 16.01; Geocue 2014.1.21; LP360 2015.1. Approximate size of entire delivery dataset = 400 GB |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Compiled to meet 0.36 m (1.18 feet) horizontal accuracy at 95 percent confidence level.; Quantitative Value: 0.36 meters, Test that produced the value: Lidar system specifications are available in the project report |
Vertical Positional Accuracy |
LAS data covering the Martin County QL2 Lidar Task Order was compared to independent survey control points to determine the NVA of the LAS Swath and of the Bare-Earth DEM. In addition, this LAS data was compared to independent VVA points. LAS Swath Non-Vegetated Vertical Accuracy (NVA) Tested 0.07 m (0.243 US feet) Non vegetated vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using 0.038 m (0.124 US feet) (RMSEz) x 1.96000 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. Bare-Earth DEM Non-Vegetated Vertical Accuracy (NVA) Tested 0.08 m (0.264 US feet) Non vegetated vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using 0.04 m (0.135 US feet) (RMSEz) x 1.96000 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. Relative accuracy also known as "between swath" accuracy was tested through a series of well distributed flight line overlap locations. The relative accuracy for the Martin County Florida QL2 Lidar tested at 0.03 m (0.099 US ft) RMSDz.; Quantitative Value: 0.07 meters, Test that produced the value: LAS Swath Non-Vegetated Vertical Accuracy (NVA) Tested 0.07 m (0.243 US feet) Non vegetated vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using (RMSEz) x 1.96000 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines and tested against the TIN using ground points. ; Quantitative Value: 0.08 meters, Test that produced the value: Bare-Earth DEM Non-Vegetated Vertical Accuracy (NVA) Tested 0.08 m (0.264 US feet) Non-Vegetated vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using (RMSEz) x 1.96000 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines and tested against the DEM.; Quantitative Value: 0.196 meters, Test that produced the value: Vegetated Vertical Accuracy (VVA) Tested 0.196 m (0.642 US feet) at the 95th percentile reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines and tested against the DEM. VVA Errors larger than 95th percentile include: Point 3023, Easting 761568.448, Northing 1028270.720, Z-Error 0.998 US feet |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The lidar data is visually inspected for completeness to ensure that are no void areas or missing data. |
Conceptual Consistency |
All formatted data cover the entire area specified for this project and are validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. |
» 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 | Lidar acquisition |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2016-07-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2016-01-16 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
This data set is the project specified acquired point cloud data. | Type of Source Media: Lidar dataset |
Citation Title | Lidar deliverable processing |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2016-07-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2016-01-17 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
This data set is the project specified lidar deliverables. | Type of Source Media: Lidar dataset |
Citation Title | Survey Control Acquisition |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2016-07-01 |
Extent Type | Discrete |
Extent Start Date/Time | 2015-12-15 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
This data set is the project specified acquired ground control and QAQC control data. | Type of Source Media: Control dataset |
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 |
Using a Leica ALS80 (lidar) systems on board a Woolpert aircraft, high density data, at a nominal pulse spacing (NPS) of 0.7 meters, were collected for this task order (approximately 556 square miles). Leica Specs- AGL = 1,981 meters - Aircraft Speed = 150 Knots, Field of View (Full) = 40 degrees, Pulse Rate = 545 kHz, Scan Rate = 51.0 Hz, with an average side lap of 25%. Multiple returns were recorded for each laser pulse along with an intensity value for each return. Four (4) missions were flown between January 16, 2015 and January 23, 2016. Global Navigation Satellite System (GNSS) Base Stations were used in support of the lidar data acquisition. Specific information regarding latitude, longitude, and ellipsoid height to the L1 phase center is included in the lidar processing report. Data for the task order is referenced to the NAD83(2011) StatePlane Florida East FIPS 4100 US Survey Feet, and NAVD88 in US Survey Feet. The geoid used to reduce satellite derived elevations to orthometric heights was GEOID12B. Once the data acquisition and GPS processing phases are complete, the lidar data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. The SBET was used to reduce the lidar slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. The ALS80 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of lidar data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw lidar data is reduced using the refined misalignment angles. |
Process Date/Time | 2016-01-17 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The field crew utilized Real-Time Kinematic (RTK) GPS surveying throughout most of the ground control data collection process. The survey was conducted using a 1-second epoch rate, in a fixed solution RTK mode, with each observation lasting between 60 to 180 seconds. Each station was occupied twice to insure the necessary horizontal and vertical accuracies were being met for this photogrammetric project. |
Process Date/Time | 2015-12-18 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Default (Class 1), Ground (Class 2), Low Noise (Class 7), Water (Class 9), Ignored Ground (Class 10), Bridge Decks (Class 17) and High Noise (Class 18). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. Classification of water (class 9) and ignored ground (class 10) was completed via the use of the hydrologic breaklines collected for the hydro-flattening phase. The overlap classes were determined by first identifying the overlapping areas and reclassifying the LAS data by offset from a corridor. This allows the returns located on the edge of the swath to be removed from the bare earth coverage in an effort to produce a more uniform data density. The returns determined to be overlap including overlap default, ground, water, and ignored ground are then applied an overlap flag and reclassified to their respective standard classification value. The surveyed ground control points are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project area. The resulting deliverables for this task order consist of classified LAS file in LAS 1.4 format, Raw Swath LAS files in LAS 1.4 format, 4 feet pixel size DEM files in ERDAS IMG format, 8-bit Intensity files in GeoTIFF format, and Hydrologic Breakline data in ESRI .GDB format. |
Process Date/Time | 2016-01-17 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received 768 files in IMG format from Martin County, Florida. The DEM files contained elevation measurements in Florida State Plane East horizontal coordinates (feet) with vertical elevations referenced to NAVD88 (Geoid 12b) in feet. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. GDAL translate was used to convert to cloud optimized geotiff format. 2. The files were ingested into the Digital Coast Data Access Viewer. |
Process Date/Time | 2023-08-15 00:00:00 |
Process Contact | NOAA Office for Coastal Management (NOAA/OCM) |
Phone (Voice) | (843) 740-1202 |
Email Address | coastal.info@noaa.gov |
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 | 49422 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:13+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 18:55+0000 |
Metadata Record Published | 2024-01-10 |
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 |
---|