| NGDC Metadata Home | Published Metadata Records |
| Alternate Views: |
|
||||
| XML files: |
|
| Origin: | DOC/NOAA/NOS/CSC/CRS > Coastal Remote Sensing Program, Coastal Services Center, National Ocean Service, NOAA, U.S. Department of Commerce |
| Pub Date: | 20061018 |
| Title: | 2003 Oahu coastline lidar mapping project |
| Geoform: | model |
| Begdate: | 20031021 |
| Enddate: | 20031207 |
| Date | Event |
|---|---|
| 20050902 | EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001 compliant production work flows. The following is a step-by-step breakdown of the process. 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, the technician performed a visual inspection of the data to verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the data set and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 6. The final DEM was written to an ESRI grid format (.flt). 7. The point cloud data were also delivered in LAS format. |
| 20050927 | The NOAA Coastal Services Center (CSC) received LAS files containing the point cloud elevation data from Earth Data, Inc. CSC performed the following processing on the data to make it available within the Lidar Data Retrieval Tool (LDART): 1. Variable length header records were added to the LAS files to identify projection, datum and sort order. 2. The LAS files were sorted by latitude. |
| 20060103 | The NOAA National Geophysical Data Center (NGDC) received Lidar data files on external harddrive. The disk contains LiDAR data from the NOAA Coastal Services Center. This data is currently being served via LDART at http://www.csc.noaa.gov/ldart . This data can be used to re-populate the system. The data are provided on this disk in two forms, ascii x,y,z data and also in LAS format. LAS format is an industry standard for serving LiDAR data. The data are exclusively in geographic coordinates, however, the datums used vary. Most is NAD 83, however some is in ITRF. Vertical systems include both ellipsoid (ITRF and NAD 83) and NAVD 88. For NAVD 88 values, Geiod 03 is primarily used; however, data received in NAVD 88 prior to 2003 was processed using Geoid 99. |
| Availability in digital form: |
| Format Name: |
Please contact
metadata@csc.noaa.gov
for this information.
|
| Network Links: |
Please contact
metadata@csc.noaa.gov
for this information.
|
| Off line media: |
Please contact
metadata@csc.noaa.gov
for this information.
|
| Cost: |
Please contact
metadata@csc.noaa.gov
for this information.
|
| Special Instructions: |
Please contact
metadata@csc.noaa.gov
for this information.
|
| Delivery: |
Please contact
metadata@csc.noaa.gov
for this information.
|