Hi Howard, I have to mention that I received a lot of help from William Kyngesburye while compiling 'boost' and with the cmake -D etc. code for GRASS on Mac. I am happy to contribute to the help on how to install boost/libLas on MacOsX.
Reading/Writing LAS files directly with libLAS in GRASS would be nice. I happy to try and have a look at implementing it within GRASS but I am just a GRASS beginner and not a programmer. I have been using R statistics all the time. I would be great to make liblas work for R also! There is a package within R that integrates R and C++ ->http://cran.r-project.org/web/packages/Rcpp/index.html and http://dirk.eddelbuettel.com/code/rcpp.html (if somebody could support me in making it run I am happy to volunteer here) Cheers, Jan On 02/12/2010, at 6:23 PM, Howard Butler wrote: On Dec 2, 2010, at 10:55 AM, Verbesselt, Jan wrote: Hi all, I am trying to install the libLAS C++ library on my mac here so that I can use it with GRASS (from http://www.kyngchaos.com/software/grass) as shown on the following wiki (http://grass.osgeo.org/wiki/LIDAR) and in the future via Python or R statistics. It would be nice if someone contributed some code to GRASS to enable reading/writing LAS files directly with libLAS instead of using the las2txt/txt2las mechanisms. It'd be much faster. I would happily help any volunteer who takes on the task. Initially, I was getting an error when running the 'cmake -G "Unix Makefiles" ../ ' command. This was solved by commenting out ln the CMakeLists.txt : #file(READ "doc/index.txt" README ) (thanks Howard) I will fix this for the next release. Thanks for the report. Then I ran the following to link it with gdal and geotif library (installed before installing grass from http://www.kyngchaos.com/software/grass): " cmake -D CMAKE_INSTALL_PREFIX=/usr/local \ -D GDAL_CONFIG=/Library/Frameworks/GDAL.framework/Programs/gdal-config \ -D GEOTIFF_INCLUDE_DIR=/Library/Frameworks/UnixImageIO.framework/unix/include \ -D GEOTIFF_LIBRARY=/Library/Frameworks/UnixImageIO.framework/unix/lib/libgeotiff.dylib \ .. " which went ok: Awesome. I hadn't tested with William's frameworks yet. I will add this to the docs as another alternative. Do I have to do something about these warning messages? These warnings are expected. What are the consequences? Some of these might be issues to worry about. Others are not so consequential. We do strive to compile as warning-free as possible, and we compile by default with most of the warning knobs turned on. Howard Jan Verbesselt Wageningen University, Centre for Geo-information P.O. box 47 6700 AA Wageningen The Netherlands _______________________________________________ Liblas-devel mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/liblas-devel
