Howard just posted announcement about patch of libLAS 1.2.1 release.
Detailed list of fixes includes:
- #120 – support ‘comma’ as a separator in las2txt
- #121 – las2txt and txt2las don’t work with the Point Source ID
- #122 – las2las does not eliminate requested classifications
- #124 – some files have pad bytes when they shouldn’t
- #127 – Scan flags is order sensitive
- #129 – Version.rc doesn’t make the release
- #132 – Require libgeotiff when GDAL is requested
- #133 – FreeBSD endian.hpp
- #134 – GDAL transform translates the points incorrectly when there is a scale or translation on the points
- #136 – Problem overwritting Reader’s dataoffset due to VLR
- #139 – txt2las is not setting the point source id correctly for values > 255
- #140 – liblas 1.2 linking problems due to –with-hide-internals gdal option
- #141 – lasinfo in not reporting info about point source id
- #143 – libLAS 1.2 requires GDAL 1.7 (unreleased)
- #144 – Apps should take in filenames without -i argument
- #145 – Memory leak from LASWriter / lasspatialreference assignment operator=
- #148 – No prototype in core.py for LASPoint_Destroy
On behalf of the libLAS team, thanks to all who provided bug reports and patches!
Before delivering next major release of libLAS, there is one big issue that must be fixed. It is problem with large files under Windows 32-bit operating system – ticket #147. Volunteers are welcome to take care of it :-)
I would also like to see completed build configuration based on CMake – ticket #52. It is already usable on Unix (GCC) and Windows (Visual C++), so testers are welcome to give it a try and give us feedback.