las2txt with all the atributes
624 views
Skip to first unread message
Julian Olszewski
Sep 24, 2013, 5:27:19 AM9/24/13
to last...@googlegroups.com
Hi Everyone,
Is it possible to convert las to txt with full attributes? Not only XYZ.
Thanks
J
Martin Isenburg
Sep 24, 2013, 5:43:37 AM9/24/13
to LAStools - efficient command line tools for LIDAR processing
Hello,
I has hoped that somewhere between the GUI (see screen shot attached),
the las2txt_README file, and the command line help via 'las2txt -h'
would help folks to figure this out. (-: You need to add a more
embellished '-parse xyzit' parameter to the command to get something
other than the default '-parse xyz'.
Regards,
Martin @rapidlasso
-------------------
http://lastools.org/download/las2txt_README.txt
****************************************************************
las2txt:
Converts from binary LAS/LAZ 1.0 - 1.3 to an ASCII text format
For updates check the website or join the LAStools mailing list.
http://lastools.org/
http://groups.google.com/group/lastools/
http://twitter.com/lastools/
http://facebook.com/lastools/
http://linkedin.com/groups?gid=4408378
Martin @lastools
****************************************************************
example usage:
>> las2txt -i *.las -parse xyzit -sep comma
converts all LAS files *.las to ASCII files *.txt and places the
x, y, and z coordinate of each point as the 1st, 2nd, and 3rd
entries, the intensity as the 4th entry, and the gps_time as the
5th entry of each line. the entries are separated by commas.
>> las2txt -i lidar.las -o lidar.txt -parse xyz
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.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzEit -extra 0.1
converts LAZ 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
extra string "0.1" as the 4th entry and the intensity and time
of each point as the 5th and 6th entry.
>> las2txt -i lidar_1_3.las -o lidar.txt -parse WV
converts LAS 1.3 file including waveform information to ASCII. it
places the wavepacket info of each point followed by its entire
waveform into one line separated by spaces.
>> las2txt -i lidar.laz -o lidar.txt -parse txyzr -sep comma
converts LAZ file to ASCII and places the gps_time as the first
entry, the x, y, and z coordinates at the 2nd, 3rd, and 4th entry
and the number of the return as the 5th entry of each line. the
entries are separated by a comma.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzRGB
converts LAZ file to ASCII and places the x, y, and z coordinates
at the 1st, 2nd, and 3rd entry and the r, g, and b value of the
RGB color as the 4th, 5th, and 6th entry of each line. the entries
are separated by a space. note that lidar.las should be format 1.2
or higher (because 1.0 and 1.1 do not support RGB colors).
>> las2txt -i lidar.las -o lidar.txt -parse xyzia -sep semicolon -header pound
converts LAS file to ASCII and places the x, y, and z coordinate
at the 1st, 2nd, and 3rd entry, the intensity at the 4th and the
scan angle as the 5th entry of each line. the entries are separated
by a semicolon. at the beginning of the file we print the header
information as a comment starting with a '#' symbol.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzcu -sep tab -header percent
converts LAZ file to ASCII and places the x, y, and z coordinate
at the 1st, 2nd, and 3rd entry, the classification at the 4th and
the user data as the 5th entry of each line. the entries are
separated by a semicolon. at the beginning of the file we print
the header information as a comment starting with a '%' symbol.
C:\lastools\bin>las2txt -h
Filter points based on their coordinates.
-clip_tile 631000 4834000 1000 (ll_x, ll_y, size)
-clip_circle 630250.00 4834750.00 100 (x, y, radius)
-clip 630000 4834000 631000 4836000 (min_x, min_y, max_x, max_y)
-clip_x_below 630000.50 (min_x)
-clip_y_below 4834500.25 (min_y)
-clip_x_above 630500.50 (max_x)
-clip_y_above 4836000.75 (max_y)
-clip_z 11.125 130.725 (min_z, max_z)
-clip_z_below 11.125 (min_z)
-clip_z_above 130.725 (max_z)
Filter points based on their return number.
-first_only
-last_only
-keep_return 1 2 3
-drop_return 3 4
-single_returns_only
-double_returns_only
-triple_returns_only
-quadruple_returns_only
-quintuple_returns_only
Filter points based on the scanline flags.
-drop_scan_direction 0
-scan_direction_change_only
-edge_of_flight_line_only
Filter points based on their intensity.
-keep_intensity 20 380
-drop_intensity_below 20
-drop_intensity_above 380
-drop_intensity_between 4000 5000
Filter points based on their classification.
-keep_class 1 3 7
-drop_class 4 2
Filter points based on their point source ID.
-keep_point_source 3
-keep_point_source_between 2 6
-drop_point_source_below 6
-drop_point_source_above 15
-drop_point_source_between 17 21
Filter points based on their scan angle.
-keep_scan_angle -15 15
-drop_scan_angle_below -15
-drop_scan_angle_above 15
-drop_scan_angle_between -25 -23
Filter points based on their gps time.
-keep_gps_time 11.125 130.725
-drop_gps_time_below 11.125
-drop_gps_time_above 130.725
-drop_gps_time_between 22.0 48.0
Filter points with simple thinning.
-keep_every_nth 2
-keep_random_fraction 0.1
-thin_with_grid 1.0
Transform coordinates.
-translate_x -2.5
-scale_z 0.3048
-rotate_xy 15.0 620000 4100000 (angle + origin)
-translate_xyz 0.5 0.5 0
-translate_then_scale_y -0.5 1.001
-clamp_z 70.5 72.5
Transform raw xyz integers.
-translate_raw_z 20
-translate_raw_xyz 1 1 0
-clamp_raw_z 500 800
Transform intensity.
-scale_intensity 2.5
-translate_intensity 50
-translate_then_scale_intensity 0.5 3.1
Transform scan_angle.
-scale_scan_angle 1.944445
-translate_scan_angle -5
-translate_then_scale_scan_angle -0.5 2.1
Repair points with return number or pulse count of zero.
-repair_zero_returns
Change classification by replacing one with another.
-change_classification_from_to 2 4
Transform gps_time.
-translate_gps_time 40.50
Transform RGB colors.
-scale_rgb_down (by 256)
-scale_rgb_up (by 256)
Supported LAS Inputs
-i lidar.las
-i lidar.laz
-i lidar1.las lidar2.las lidar3.las -merged
-i *.las
-i flight0??.laz flight1??.laz -single
-i lidar.txt -iparse xyzti (on-the-fly from ASCII)
-i lidar.txt -iparse xyzi -itranslate_intensity 1024
-lof file_list.txt
-stdin (pipe from stdin)
-rescale 0.1 0.1 0.1
-reoffset 600000 4000000 0
LAStools (by martin....@gmail.com) version 110521
usage:
las2txt -i *.las -parse xyzt
las2txt -i flight1*.las flight2*.las -parse xyziarn
las2txt -i *.las -parse xyzrn -sep comma -verbose
las2txt -i lidar.las -parse xyztE -extra 99 -o ascii.txt
las2txt -h
---------------------------------------------
The '-parse txyz' flag specifies how to format each
each line of the ASCII file. For example, 'txyzia'
means that the first number of each line should be the
gpstime, the next three numbers should be the x, y, and
z coordinate, the next number should be the intensity
and the next number should be the scan angle.
The supported entries are a - scan angle, i - intensity,
n - number of returns for given pulse, r - number of
this return, c - classification, u - user data,
p - point source ID, e - edge of flight line flag, and
d - direction of scan flag, R - red channel of RGB color,
G - green channel of RGB color, B - blue channel of RGB color,
M - the index for each point
X, Y, and Z - the unscaled, raw LAS integer coordinates
w and W - for the wavepacket information (LAS 1.3 only)
V - for the waVeform from the *.wpd file (LAS 1.3 only)
E - for an extra string. specify it with '-extra <string>'
---------------------------------------------
The '-sep space' flag specifies what separator to use. The
default is a space but 'tab', 'comma', 'colon', 'hyphen',
'dot', or 'semicolon' are other possibilities.
---------------------------------------------
The '-header pound' flag results in the header information
being printed at the beginning of the ASCII file in form of
a comment that starts with the special character '#'. Also
possible are 'percent', 'dollar', 'comma', 'star', 'colon',
or 'semicolon' as that special character.
> --
> Download LAStools at
> http://lastools.org
> http://rapidlasso.com
> Be social with LAStools at
> http://facebook.com/LAStools
> http://twitter.com/LAStools
> http://linkedin.com/groups/LAStools-4408378
> Manage your settings at
> http://groups.google.com/group/lastools/subscribe
I has hoped that somewhere between the GUI (see screen shot attached),
the las2txt_README file, and the command line help via 'las2txt -h'
would help folks to figure this out. (-: You need to add a more
embellished '-parse xyzit' parameter to the command to get something
other than the default '-parse xyz'.
Regards,
Martin @rapidlasso
-------------------
http://lastools.org/download/las2txt_README.txt
****************************************************************
las2txt:
Converts from binary LAS/LAZ 1.0 - 1.3 to an ASCII text format
For updates check the website or join the LAStools mailing list.
http://lastools.org/
http://groups.google.com/group/lastools/
http://twitter.com/lastools/
http://facebook.com/lastools/
http://linkedin.com/groups?gid=4408378
Martin @lastools
****************************************************************
example usage:
>> las2txt -i *.las -parse xyzit -sep comma
converts all LAS files *.las to ASCII files *.txt and places the
x, y, and z coordinate of each point as the 1st, 2nd, and 3rd
entries, the intensity as the 4th entry, and the gps_time as the
5th entry of each line. the entries are separated by commas.
>> las2txt -i lidar.las -o lidar.txt -parse xyz
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.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzEit -extra 0.1
converts LAZ 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
extra string "0.1" as the 4th entry and the intensity and time
of each point as the 5th and 6th entry.
>> las2txt -i lidar_1_3.las -o lidar.txt -parse WV
converts LAS 1.3 file including waveform information to ASCII. it
places the wavepacket info of each point followed by its entire
waveform into one line separated by spaces.
>> las2txt -i lidar.laz -o lidar.txt -parse txyzr -sep comma
converts LAZ file to ASCII and places the gps_time as the first
entry, the x, y, and z coordinates at the 2nd, 3rd, and 4th entry
and the number of the return as the 5th entry of each line. the
entries are separated by a comma.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzRGB
converts LAZ file to ASCII and places the x, y, and z coordinates
at the 1st, 2nd, and 3rd entry and the r, g, and b value of the
RGB color as the 4th, 5th, and 6th entry of each line. the entries
are separated by a space. note that lidar.las should be format 1.2
or higher (because 1.0 and 1.1 do not support RGB colors).
>> las2txt -i lidar.las -o lidar.txt -parse xyzia -sep semicolon -header pound
converts LAS file to ASCII and places the x, y, and z coordinate
at the 1st, 2nd, and 3rd entry, the intensity at the 4th and the
scan angle as the 5th entry of each line. the entries are separated
by a semicolon. at the beginning of the file we print the header
information as a comment starting with a '#' symbol.
>> las2txt -i lidar.laz -o lidar.txt -parse xyzcu -sep tab -header percent
converts LAZ file to ASCII and places the x, y, and z coordinate
at the 1st, 2nd, and 3rd entry, the classification at the 4th and
the user data as the 5th entry of each line. the entries are
separated by a semicolon. at the beginning of the file we print
the header information as a comment starting with a '%' symbol.
C:\lastools\bin>las2txt -h
Filter points based on their coordinates.
-clip_tile 631000 4834000 1000 (ll_x, ll_y, size)
-clip_circle 630250.00 4834750.00 100 (x, y, radius)
-clip 630000 4834000 631000 4836000 (min_x, min_y, max_x, max_y)
-clip_x_below 630000.50 (min_x)
-clip_y_below 4834500.25 (min_y)
-clip_x_above 630500.50 (max_x)
-clip_y_above 4836000.75 (max_y)
-clip_z 11.125 130.725 (min_z, max_z)
-clip_z_below 11.125 (min_z)
-clip_z_above 130.725 (max_z)
Filter points based on their return number.
-first_only
-last_only
-keep_return 1 2 3
-drop_return 3 4
-single_returns_only
-double_returns_only
-triple_returns_only
-quadruple_returns_only
-quintuple_returns_only
Filter points based on the scanline flags.
-drop_scan_direction 0
-scan_direction_change_only
-edge_of_flight_line_only
Filter points based on their intensity.
-keep_intensity 20 380
-drop_intensity_below 20
-drop_intensity_above 380
-drop_intensity_between 4000 5000
Filter points based on their classification.
-keep_class 1 3 7
-drop_class 4 2
Filter points based on their point source ID.
-keep_point_source 3
-keep_point_source_between 2 6
-drop_point_source_below 6
-drop_point_source_above 15
-drop_point_source_between 17 21
Filter points based on their scan angle.
-keep_scan_angle -15 15
-drop_scan_angle_below -15
-drop_scan_angle_above 15
-drop_scan_angle_between -25 -23
Filter points based on their gps time.
-keep_gps_time 11.125 130.725
-drop_gps_time_below 11.125
-drop_gps_time_above 130.725
-drop_gps_time_between 22.0 48.0
Filter points with simple thinning.
-keep_every_nth 2
-keep_random_fraction 0.1
-thin_with_grid 1.0
Transform coordinates.
-translate_x -2.5
-scale_z 0.3048
-rotate_xy 15.0 620000 4100000 (angle + origin)
-translate_xyz 0.5 0.5 0
-translate_then_scale_y -0.5 1.001
-clamp_z 70.5 72.5
Transform raw xyz integers.
-translate_raw_z 20
-translate_raw_xyz 1 1 0
-clamp_raw_z 500 800
Transform intensity.
-scale_intensity 2.5
-translate_intensity 50
-translate_then_scale_intensity 0.5 3.1
Transform scan_angle.
-scale_scan_angle 1.944445
-translate_scan_angle -5
-translate_then_scale_scan_angle -0.5 2.1
Repair points with return number or pulse count of zero.
-repair_zero_returns
Change classification by replacing one with another.
-change_classification_from_to 2 4
Transform gps_time.
-translate_gps_time 40.50
Transform RGB colors.
-scale_rgb_down (by 256)
-scale_rgb_up (by 256)
Supported LAS Inputs
-i lidar.las
-i lidar.laz
-i lidar1.las lidar2.las lidar3.las -merged
-i *.las
-i flight0??.laz flight1??.laz -single
-i lidar.txt -iparse xyzti (on-the-fly from ASCII)
-i lidar.txt -iparse xyzi -itranslate_intensity 1024
-lof file_list.txt
-stdin (pipe from stdin)
-rescale 0.1 0.1 0.1
-reoffset 600000 4000000 0
LAStools (by martin....@gmail.com) version 110521
usage:
las2txt -i *.las -parse xyzt
las2txt -i flight1*.las flight2*.las -parse xyziarn
las2txt -i *.las -parse xyzrn -sep comma -verbose
las2txt -i lidar.las -parse xyztE -extra 99 -o ascii.txt
las2txt -h
---------------------------------------------
The '-parse txyz' flag specifies how to format each
each line of the ASCII file. For example, 'txyzia'
means that the first number of each line should be the
gpstime, the next three numbers should be the x, y, and
z coordinate, the next number should be the intensity
and the next number should be the scan angle.
The supported entries are a - scan angle, i - intensity,
n - number of returns for given pulse, r - number of
this return, c - classification, u - user data,
p - point source ID, e - edge of flight line flag, and
d - direction of scan flag, R - red channel of RGB color,
G - green channel of RGB color, B - blue channel of RGB color,
M - the index for each point
X, Y, and Z - the unscaled, raw LAS integer coordinates
w and W - for the wavepacket information (LAS 1.3 only)
V - for the waVeform from the *.wpd file (LAS 1.3 only)
E - for an extra string. specify it with '-extra <string>'
---------------------------------------------
The '-sep space' flag specifies what separator to use. The
default is a space but 'tab', 'comma', 'colon', 'hyphen',
'dot', or 'semicolon' are other possibilities.
---------------------------------------------
The '-header pound' flag results in the header information
being printed at the beginning of the ASCII file in form of
a comment that starts with the special character '#'. Also
possible are 'percent', 'dollar', 'comma', 'star', 'colon',
or 'semicolon' as that special character.
> Download LAStools at
> http://lastools.org
> http://rapidlasso.com
> Be social with LAStools at
> http://facebook.com/LAStools
> http://twitter.com/LAStools
> http://linkedin.com/groups/LAStools-4408378
> Manage your settings at
> http://groups.google.com/group/lastools/subscribe
Rebecca Bennett
Sep 24, 2013, 5:52:14 AM9/24/13
to last...@googlegroups.com
Dear lastools users,
I am drafting a lidar data collection for archaeological survey of a (predominantly deciduous) woodland area and would welcome advice on specifying the point cloud data deliverables.
I have requested tiled las format in local CRS with:
time, easting, northing, elevation, intensity, classification, return
number, scan angle rank
Did I miss anything? Additionally, what is considered standard file format for transfer / archiving full-waveform data? Are there any good practice guidelines out there for full-waveform data?
Thanks for reading,
Rebecca
Rebecca Bennett
Postdoctoral Associate, Wired! Group
Department of Art, Art History and Visual Studies
Duke University, Durham, NC
www.pushingthesensors.com
Postdoctoral Associate, Wired! Group
Department of Art, Art History and Visual Studies
Duke University, Durham, NC
www.pushingthesensors.com
Newcomb, Doug
Sep 24, 2013, 11:11:54 AM9/24/13
to last...@googlegroups.com
Rebecca,
Here is a good place to start...
http://lidar.cr.usgs.gov/USGS-NGP%20Lidar%20Guidelines%20and%20Base%20Specification%20v13%28ILMF%29.pdfDoug
--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe
Doug Newcomb
USFWS
Raleigh, NC
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
Evon Silvia
Sep 24, 2013, 11:41:38 AM9/24/13
to last...@googlegroups.com
Perhaps a "-parse all" option would be helpful to those that want every field? :-)
Evon
Reply all
Reply to author
Forward
0 new messages