I sure hope they incorporate it. Lidar is becoming ever so popular, and the LAS format more common. As a user, incorporating libLAS into GRASS seems a necessity, especially given there are no tools in GRASS to import LAS files. I cant think of other GIS related data that needs pre-processed to some other format for GRASS to import it.<br>
<br>Mark<br><br><div class="gmail_quote">On Thu, May 8, 2008 at 4:56 AM, Mateusz Loskot <<a href="mailto:mateusz@loskot.net">mateusz@loskot.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Roberto Antolín wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I've took a look into the Mateusz's thread in the grass-devel list and I agree that, by the moment and as a fast thing, it would be possible to make a wrapper with last2txt and v.in.ascii or r.in.xyz. Later, it would be great to make a *.in.las command or something like that. I don't know whether it is possible/necessary/useful to embed libLAS to work directly with the grass lidar tools (v.lidar.*).<br>
</blockquote>
<br></div>
Roberto,<br>
<br>
FYI, I've decided to leave the decision about which approach to follow<br>
to the GRASS team. So, I'll wait for their decision and see if<br>
there is a place for me to contribute, if they want to use libLAS :-)<br>
<br>
Greetings<br><font color="#888888">
-- <br>
Mateusz Loskot<br>
<a href="http://mateusz.loskot.net" target="_blank">http://mateusz.loskot.net</a></font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Liblas-devel mailing list<br>
<a href="mailto:Liblas-devel@mail.hobu.net" target="_blank">Liblas-devel@mail.hobu.net</a><br>
<a href="http://mail.hobu.net/mailman/listinfo/liblas-devel" target="_blank">http://mail.hobu.net/mailman/listinfo/liblas-devel</a><br>
</div></div></blockquote></div><br>