From hobu.inc at gmail.com Wed Jun 18 23:15:04 2008 From: hobu.inc at gmail.com (Howard Butler) Date: Wed Jun 18 23:15:18 2008 Subject: [Liblas-devel] Preparing for a 1.0 release Message-ID: <0957D802-04A1-4D5F-BF85-979159F04018@gmail.com> All, I just recently completed geotiff key writing support for libLAS, and I think we are very close to issuing a 1.0 release candidate. This email is a final query to see if anyone has identified any outstanding issues that they would like to see resolved before making a release candidate. Here's a short list of stuff that's been done since 0.9.7: - proper endianness support for big and little endian machines - las2ogr is now available when libLAS is linked to GDAL - geotiff key writing from proj.4 strings with the latest CVS libgeotiff - VLR summary info is printed when lasinfo is issued - las2las respects the --verbose switch - las2las was using an incorrect system id http://liblas.org/ticket/56 - exit() calls in the utilities were normalized to behave similarly http://liblas.org/ticket/55 - The C API no longer uses void* for the opaque handles for more compile-time type safety http://liblas.org/ticket/59 - stack corruption bug in las2las http://liblas.org/ticket/57 I notice there are some of the C++ unit tests and Python unit tests failing due to the geotiff key support that I will fix before the release. I look forward to hearing of any experiences you have with the library and if you see any final thing that needs to be done before kicking 1.0 out the door. Thanks, Howard From mseibel at gmail.com Thu Jun 19 10:42:46 2008 From: mseibel at gmail.com (M S) Date: Thu Jun 19 10:43:02 2008 Subject: [Liblas-devel] Preparing for a 1.0 release In-Reply-To: <0957D802-04A1-4D5F-BF85-979159F04018@gmail.com> References: <0957D802-04A1-4D5F-BF85-979159F04018@gmail.com> Message-ID: That is fantastic. Great tie-in to OGR also! Huge thanks to everyone who made this possible. What a great tool. Mark On Thu, Jun 19, 2008 at 12:15 AM, Howard Butler wrote: > All, > > I just recently completed geotiff key writing support for libLAS, and I > think we are very close to issuing a 1.0 release candidate. This email is a > final query to see if anyone has identified any outstanding issues that they > would like to see resolved before making a release candidate. > > Here's a short list of stuff that's been done since 0.9.7: > > - proper endianness support for big and little endian machines > - las2ogr is now available when libLAS is linked to GDAL > - geotiff key writing from proj.4 strings with the latest CVS libgeotiff > - VLR summary info is printed when lasinfo is issued > - las2las respects the --verbose switch > - las2las was using an incorrect system id http://liblas.org/ticket/56 > - exit() calls in the utilities were normalized to behave similarly > http://liblas.org/ticket/55 > - The C API no longer uses void* for the opaque handles for more > compile-time type safety http://liblas.org/ticket/59 > - stack corruption bug in las2las http://liblas.org/ticket/57 > > I notice there are some of the C++ unit tests and Python unit tests failing > due to the geotiff key support that I will fix before the release. I look > forward to hearing of any experiences you have with the library and if you > see any final thing that needs to be done before kicking 1.0 out the door. > > Thanks, > > Howard > _______________________________________________ > Liblas-devel mailing list > Liblas-devel@mail.hobu.net > http://mail.hobu.net/mailman/listinfo/liblas-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.hobu.net/pipermail/liblas-devel/attachments/20080619/72eb772e/attachment.html From hobu.inc at gmail.com Fri Jun 20 16:46:27 2008 From: hobu.inc at gmail.com (Howard Butler) Date: Fri Jun 20 16:46:42 2008 Subject: [Liblas-devel] 1.0.0 Beta 1 Message-ID: <5B209335-8A3F-4256-A77F-AED114EEAD5C@gmail.com> 6/20/2008 All, I am pleased to announce the release of libLAS 1.0.0b1. Congratulations to all of the developers (especially Mateusz) who have helped make this software a reality. I think it has shaped up quite nicely, and it's time to kick it out the door. I propose that with the 1.0.0 beta 1 release, we attempt to widely advertise and hope to attract more testers. I would like to aim for a 1.0.0 final release by July 31st, with the number of beta releases being anywhere from one to three, depending on how much work is identified that needs to be done. Here's a short list of stuff that's been done since 0.9.7: - proper endianness support for big and little endian machines http://liblas.org/ticket/48 - las2ogr is now available when libLAS is linked to GDAL http://liblas.org/ticket/32 - geotiff key writing from proj.4 strings with the latest CVS libgeotiff http://liblas.org/ticket/39 - VLR summary info is printed when lasinfo is issued - las2las respects the --verbose switch - las2las was using an incorrect system id http://liblas.org/ticket/56 - las2las can be used to convert between 1.0 and 1.1 data by specifying --format http://liblas.org/ticket/53 - exit() calls in the utilities were normalized to behave similarly http://liblas.org/ticket/55 - The C API no longer uses void* for the opaque handles for more compile-time type safety http://liblas.org/ticket/59 - stack corruption bug in las2las http://liblas.org/ticket/57 - Use today's information upon initialization of a LASHeader http://liblas.org/ticket/60 Source release ------------------- http://liblas.org/raw-attachment/wiki/1.0.0b1/las-1.0.0b1.tar.bz2 http://liblas.org/raw-attachment/wiki/1.0.0b1/las-1.0.0b1.tar.bz2.md5 Windows Binary -------------------- http://liblas.org/raw-attachment/wiki/1.0.0b1/liblas1.0.0b1-win32.zip http://liblas.org/raw-attachment/wiki/1.0.0b1/liblas1.0.0b1-win32.zip.md5 Thanks, Howard From mateusz at loskot.net Fri Jun 27 05:20:37 2008 From: mateusz at loskot.net (=?UTF-8?B?TWF0ZXVzeiDFgW9za290?=) Date: Fri Jun 27 05:20:52 2008 Subject: [Liblas-devel] 1.0.0 Beta 1 In-Reply-To: <5B209335-8A3F-4256-A77F-AED114EEAD5C@gmail.com> References: <5B209335-8A3F-4256-A77F-AED114EEAD5C@gmail.com> Message-ID: <4864BEF5.6060302@loskot.net> Howard Butler pisze: > 6/20/2008 > > All, > > I am pleased to announce the release of libLAS 1.0.0b1. Hobu, I've forwarded the news to the USGS LDIDAR board: http://lidarbb.cr.usgs.gov/index.php?showtopic=3700 Ciao -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org From gok at aerometric-ak.com Fri Jun 27 12:37:52 2008 From: gok at aerometric-ak.com (Gennady Khokhorin) Date: Fri Jun 27 12:39:07 2008 Subject: [Liblas-devel] lasmerge in liblas Message-ID: <3054411AF4728548AD6D7137190D56B30C4824@admin1.aeromap.com> Hello, Mateusz. Have couple questions kind of about library design. Did receive you liblas Beta 1 announce from one of my college: http://lidarbb.cr.usgs.gov/index.php?showtopic=3700&pid=4622&st=0&#entry 4622 It is a great news that las is finally linked to GDAL. I'm using a lot of GDAL vector, raster functionality building stand-along apps. So, as far as liblas is part of GDAL what the purpose of lasmerge routine? Should it be part of GDAL syntax like "ogr2ogr -append.." ? In the past I did create driver for las (ASPRS), bin (TerraScan), cmp (Optech), xyz (text) lidar data formats with multiple operations: logical (merge, split), spatial (shift, reproject, VLR georeference), extract data (by time, by prizm). I'm wonder what are team's plans to extend liblas to create such features? Or it will be up to GDAL? Happy programming! Gennady Khokhorin Software Developer, www.aerometric.com (907) 272-4495