<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>Martin-<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I don’t understand why you put some of those applications under LGPL -- the LGPL typically only makes sense for *libraries* that are designed to be linked against…? (Or are you concerned about 3<sup>rd</sup> party applications that could invoke your applications as a separate process?)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-mpg<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> liblas-devel-bounces@lists.osgeo.org [mailto:liblas-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Martin Isenburg<br><b>Sent:</b> Thursday, April 07, 2011 6:43 AM<br><b>To:</b> francesco<br><b>Cc:</b> liblas-devel@lists.osgeo.org<br><b>Subject:</b> Re: [Liblas-devel] Open source lidar software?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>hi,<br><br>a quick note to end the confusion on the open-ness and license terms of LAStools.<br><br>On Wed, Apr 6, 2011 at 10:28 PM, francesco <<a href="mailto:francesco.pirotti@unipd.it">francesco.pirotti@unipd.it</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal><br>I've been trying out the following open source on lidar data: [...] Martin Isenberg's lastools (not clear if source is all open). [...]<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal><o:p> </o:p></p></div></blockquote><p class=MsoNormal><br>At first LAStools was just supporting my own research on memory-efficient LIDAR processing via Delaunay TIN streaming [1] and visualizing LIDAR with Google Earth [2]. When Howard contacted me on 17 Nov 2007 about turning my existing LAS reader/writer hack into a proper software engineering project called libLAS, LAStools was just a few tools (i.e. lasinfo, las2las, las2txt, txt2las, ..). At that point these tools branched off and now also (!) life with a BSD license inside libLAS.<br><br>Later I added more elaborate tools to LAStools. I did that sort of as an evening hobby and without specifying any licensing terms due to my own ignorance (or incompetence) on those things.<br><br>So what are the terms? Some parts of LAStools are open source (LGPL). Some are not (at least for now as some tools may move into the open). Here are the current terms in more detail [3]:<br><br>These LAStools are open-source and LGPL-licensed (see COPYING.txt):<br>* laszip<br>* las2las<br>* lasinfo<br>* lasdiff<br>* lasmerge<br>* las2txt & txt2las<br>* lasprecision<br>* LASzip - the lossless LAS compressor at <a href="http://laszip.org">http://laszip.org</a><br>* LASlib (with LASzip) - the API used by LAStools.<br><br>These LAStools require a license for commercial use. But they can<br>be used freely for non-commercial and non-military purposes that<br>are private, educational, humanitarian, not-for-profit, research,<br>or where you can convince me that they will better the world.<br><br>* lasboundary<br>* las2tin<br>* las2iso<br>* las2dem<br>* lasthin<br>* lassort<br>* lastile<br>* lasclip<br>* lasview<br>* las2shp & shp2las.<br><br>Cheers,<br><br>Martin<br><br>[1] <a href="http://www.cs.unc.edu/~isenburg/tin2dem/">http://www.cs.unc.edu/~isenburg/tin2dem/</a><br>[2] <a href="http://www.cs.unc.edu/~isenburg/googleearth/">http://www.cs.unc.edu/~isenburg/googleearth/</a><br>[3] <a href="http://www.cs.unc.edu/~isenburg/lastools/download/LICENSE.txt">http://www.cs.unc.edu/~isenburg/lastools/download/LICENSE.txt</a><o:p></o:p></p></div></div></body></html>