Bringing LiDAR Data into ArcGIS

In this tutorial, Danielle Lee explains how to bring LiDAR data into ArcGIS. It requires the use of the 3D Analyst extension with ArcGIS, so hopefully you’ve got it!

To follow along, grab the data from http://lidar.swc.nd.gov/
The data Danielle used is called 13908001.LAS, so feel free to grab that, or get any other LiDAR data!
This tutorial was prepared for Arc version 9.3.1 but works with Arc v10.

1. Turn on the 3D Analyst Extension

2. Determine the Average Point Spacing of your LiDAR data by using the 3D Analyst Tools>Conversion>From File>Point File Information tool if unknown. The point spacing will be in the attribute table of the new Shapefile created.

a. In ArcMap ArcToolbox, browse to 3D Analyst Tools>Conversion>From File> LAS to Multipoint. Choose the LAS files for your area of interest and point spacing, and save as LAS_to_Multipoint.shp.

b. If your LAS data is in ASCII format, use the ASCII 3D to Feature tool.

3. Open ArcCatalog and browse to the folder that contains the new multipoint feature LAS_to_Multipoint.shp. Assign a coordinate system to the LAS_to_Multipoint if there is not one already assigned. (in Arc10 you can find the projection in: projectect coordinate systems > state plane > NAD 1983 > NAD 1983 StatePlane North Dakota S FIPS 3302 (US Feet))

 

4. In the same folder that contains LAS_to_Multipoint, go to File>New>File Geodatabase and name it LiDAR:

5. Right click on the new LiDAR.gdb and go to New>Feature Dataset and name it LiDAR_Files

 

6. Right click on LiDAR_Files Feature Dataset and go to Import>Feature class (single), importing LAS_to_Multipoint.shp. You may also import breaklines, clipping boundaries, and any other files that cover the project area. Click through the wizard to completion.

 

7. Right click on the LiDAR_Files Feature Dataset and go to New>Terrain

 

8. This is the Terrain Wizard. See http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?id=3413&pid=3410&topicname=Building_a_terrain_dataset_with_the_terrain_wizard for detailed information. Name the terrain Terrain and select all the LAS_to_Multipoint and breaklines.

a. The pyramid levels are simply for display purposes, so only create one pyramid level (this will drastically cut down on processing time). Click Calculate Pyramid Properties to create pyramid (ensure that you have at least 1). Click Next, view the summary, and click Finish.

b. When the Wizard is complete, it will take a while to create the actual terrain. Click Yes to build now.

9. When your Terrain is created, bring it into ArcMap to check that it looks reasonable.

10. If everything looks good, go back to Catalog, convert to Raster or to TIN by using 3D Analyst Tools> Conversion> From Terrain> Terrain to Raster/TIN.

Note: When working with large terrains, you may want to click Environments>Terrain and limit memory use for terrain analysis.

Supplementary Info: Importing ASCI LIDAR Break Lines

If break lines are in this ASCII text format (if they are not in this format, the text file must first be modified):

Use the 3-D Analyst “ASCII 3D to Feature Class” conversion tool:

Options: Generate & Polyline

3 Comments

  • Lopezpavillio
    Posted December 4, 2013 at 4:54 pm | Permalink

    Thanks for this information. I found this very helpful, while working on a project of mine which required an introduction to LiDAR data.

  • MADHUSUDHAN REDDY NAGENDLA
    Posted March 10, 2014 at 4:01 am | Permalink

    good information sir. please send more information on canopy height determination in ArcGIS using lidar data.

  • Danielle Lee
    Posted August 4, 2014 at 1:29 pm | Permalink

    Hi there! This is Danielle, the original poster. Madhusudhan, I do not usually focus on canopy height, more “bare earth.” You might need to check elsewhere. Thank you!

Post a Comment

Your email is kept private. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>