hi,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I hope to add support for the other LAS 1.3 point formats in the near future. Martin has already updated the LASzip compressor to handle them as well.<font color="#888888"></font><br></blockquote><div><br>let me clarify. all LAStools support reading and writing LAS 1.3 point formats 4 and 5. only laszip, lasinfo and las2txt have functionality that make use of the wavepacket part of each point. laszip can losslessly compress LAS 1.3 files that store the waveforms externally - including the wavepacket part. but there is no support for compressing the waveforms themselves. lasinfo reports about the wavepackets, and las2txt can extract both the wavepacket part of each point and the waveforms themselves and put them into ASCII form <br>
<br>las2txt -i lidar1.3.las -o waveform -parse xyzV<br>las2txt -i lidar1.3.las -o waveform -parse xyzWV<br><br>that said i do not think we should make our life miserable trying to support LAS 1.3 waveforms. i have written up a little something about why - in my humble opinion - the LAS 1.3 format's way of handling waveforms is poorly designed:<br>
<br><a href="https://lidarbb.cr.usgs.gov/index.php?showtopic=11748">https://lidarbb.cr.usgs.gov/index.php?showtopic=11748</a><br><br>and i was contemplating about creating a facebook page "<span onclick="return span_desc_to_input("11748");" id="tid-desc-11748">the messy waveform storage in LAS 1.3". i thought many of you "like" this page ... </span>(-;<br>
<br>martin<br><br><br></div></div>