All,

10/2/2009

The libLAS team is pleased to announce the maintenance release of libLAS 1.2.1 This release fixes seventeen bugs:

• http://liblas.org/ticket/120 - support 'comma' as a separator in las2txt
• http://liblas.org/ticket/121 - las2txt and txt2las don't work with the Point Source ID
• http://liblas.org/ticket/122 - las2las does not eliminate requested classifications
• http://liblas.org/ticket/124 - some files have pad bytes when they shouldn't
• http://liblas.org/ticket/127 - Scan flags is order sensitive
• http://liblas.org/ticket/129 - Version.rc doesn't make the release
• http://liblas.org/ticket/132 - Require libgeotiff when GDAL is requested
• http://liblas.org/ticket/133 - FreeBSD endian.hpp
• http://liblas.org/ticket/134 - GDAL transform translates the points incorrectly when there is a scale or translation on the points
• http://liblas.org/ticket/136 - Problem overwritting Reader's dataoffset due to VLR
• http://liblas.org/ticket/139 - txt2las is not setting the point source id correctly for values > 255
• http://liblas.org/ticket/140 - liblas 1.2 linking problems due to --with-hide-internals gdal option
• http://liblas.org/ticket/141 - lasinfo in not reporting info about point source id
• http://liblas.org/ticket/143 - libLAS 1.2 requires GDAL 1.7 (unreleased)
• http://liblas.org/ticket/144 - Apps should take in filenames without -i argument
• http://liblas.org/ticket/145 - Memory leak from LASWriter / lasspatialreference assignment operator=
• http://liblas.org/ticket/148 - No prototype in core.py for LASPoint_Destroy

Links to source code and binaries are available from <http://liblas.org/wiki/1.2.1> or from updating your OSGeo4W <http://trac.osgeo.org/osgeo4w/> install if you are using that. Python bindings can be obtained from OSGeo4W or from PyPI (no GDAL support) <http://pypi.python.org/pypi/libLAS> if you want libLAS in your own Python install.

Thanks to all who provided bug reports and patches!

Howard