View License

Download apps, toolboxes, and other File Exchange content using Add-On Explorer in MATLAB.

» Watch video

Highlights from

5.0 | 1 rating Rate this file 4 Downloads (last 30 days) File Size: 14.1 KB File ID: #23136 Version: 1.1




26 Feb 2009 (Updated )

Reads in and displays the header information from a lidar data file in LAS format

| Watch this File

File Information

The function read_las_header reads and displays the header information from a lidar data file in the American Society for Photogrammetry & Remote Sensing (ASPRS) LAS format, as specified in the following document: "LAS Specification Version 1.2" ASPRS, April 29, 2008. If properly populated, the LAS header contains such information as the software used to generate the LAS file, the year and day the file was created, the sensor or process used to generate the data, the number of points per return (e.g., first, second, third pulse, etc.), the total number of points in the file, the min and max X,Y,Z coordinates, and other info needed to correctly read lidar points from the file. The function is backwards-compatible, with respect to the LAS version (i.e., header information from lidar files in LAS 1.0 and 1.1 formats should display fine).

The accompanying file, coordinate_sys.mat, is needed to display coordinate system information.

lasFilename: Path and filename of LAS file
Example of calling this function:
headerInfo = read_las_header('C:\my_lidar_file.las');
lasHeaderInfo: Up to 40x2 cell array containing all the info read in from the LAS file header. If coordinate system info is missing, then lasHeaderInfo will be a 36x2 cell array.
Chris Parrish

MATLAB release MATLAB 7.0.1 (R14SP1)
Tags for This File   Please login to tag files.
Please login to add a comment or rating.
Comments and Ratings (2)
23 May 2012 Liu

Liu (view profile)

it does not work for usgs las 1.2 format file, can you leave some contact infomation?

Comment only
17 Feb 2011 Sven

Sven (view profile)

just what I needed, thanks!

02 Sep 2011 1.1

Fixed bug that caused Version Major, Version Minor, and Point Data Format IDs to not be read in correctly. Also now displays vertical datum info and units, if populated in GeoKeyDirectoryTag.

Contact us