'\" -*- coding: us-ascii -*- .if \n(.g .ds T< \\FC .if \n(.g .ds T> \\F[\n[.fam]] .de URL \\$2 \(la\\$1\(ra\\$3 .. .if \n(.g .mso www.tmac .TH txt2las 1 "16 February 2019" "" "" .SH NAME txt2las \- converts LIDAR data from ASCII format into LAS representation .SH SYNOPSIS 'nh .fi .ad l \fBtxt2las\fR \kx .if (\nx>(\n(.l/2)) .nr x (\n(.l/5) 'in \n(.iu+\nxu [\fB-h\fR | \fB-parse\fR tsxyz \fIlidar.txt\fR | \fB-parse\fR txyzar \fIlidar.txt.gz lidar.laz\fR | \fB-parse\fR xyz [\fB-scale\fR \fI0.02\fR ] \fB-i\fR \fIlidar.txt\fR \fB-o\fR \fIlidar.laz\fR | \fB-parse\fR xyzsst [\fB-verbose\fR] [\fB-scale\fR \fI0.05\fR] \fIlidar.txt\fR | \fB-parse\fR xsysz [\fB-xyz_scale\fR \fI0.02 0.02 0.01\fR] \fIlidar.txt\fR ] 'in \n(.iu-\nxu .ad b 'hy .SH DESCRIPTION \fBtxt2las\fR converts LIDAR data from a standard ASCII format into the more efficient binary LAS representation. .SH OPTIONS .TP \*(T<\fB\-h\fR\*(T> produce help message .TP \*(T<\fB\-parse\fR\*(T> \fIarg\fR Parsing Flags The '\*(T<\fB\-parse tsxyz\fR\*(T>' flag specifies how to interpret each line of the ASCII file. For example, '\*(T' means that the first number is the gpstime, the next number should be skipped, the next three numbers are the x, y, and z coordinate, the next two should be skipped, and the next number is the scan angle. The other supported entries are: .RS .TP 0.2i \(bu i - intensity .TP 0.2i \(bu n - number of returns of given pulse .TP 0.2i \(bu r - number of return .TP 0.2i \(bu c - classification .TP 0.2i \(bu u - user data .TP 0.2i \(bu p - point source ID .TP 0.2i \(bu e - edge of flight line flag .TP 0.2i \(bu d - direction of scan flag. .RE .TP \*(T<\fB\-scale\fR\*(T> \fIarg\fR Scale The '\*(T<\fB\-scale 0.02\fR\*(T>' flag specifies the quantization. The default value of 0.01 means that the smallest increment two between coordinates is 0.01. If measurements are in meters this corresponds to centimeter accuracy, which is commonly considered sufficient for LIDAR data. .TP \*(T<\fB\-i\fR\*(T> \fIarg\fR input LAS file. .TP \*(T<\fB\-o\fR\*(T> \fIarg\fR output text file. .TP \*(T<\fB\-xyz_offset\fR\*(T> \fI500000 2000000 0\fR .TP \*(T<\fB\-xyz_scale\fR\*(T> \fI0.02 0.02 0.01\fR .TP \*(T<\fB\-file_creation\fR\*(T> \fI67 2003\fR .TP \*(T<\fB\-system_identifier\fR\*(T> \fI"Airborne One Leica 50,000 Hz"\fR .TP \*(T<\fB\-generating_software\fR\*(T> \fI"TerraScan"\fR .SH EXAMPLE \fBSimple conversion to text file\fR .PP .nf \*(T< $ txt2las \-i lidar.las \-o lidar.txt \-parse xyz \*(T> .fi converts LAS file to ASCII and places the x, y, and z coordinate of each point at the 1st, 2nd, and 3rd entry of each line. The entries are separated by a space. .nf \*(T< $ txt2las \-i lidar.taxyz \-o lidar.las \-parse ssxyz \*(T> .fi converts ASCII file and uses the 3rd, 4th, and 5th entry of each line as the x, y, and z coordinate of each point. .nf \*(T< $ txt2las \-i lidar.txt.gz \-o lidar.las \-parse txyzsa \*(T> .fi converts a gzipped ASCII file and uses the 1st entry of each line as the gps time, the 3rd, 4th, and 5th entry as the x, y, and z coordinate of each point, and the 6th entry as the scan angle