Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Mark Seibel
When I try to compile LAG, I have all components present except lidarquadtree. I'm trying to compile the lidarquadtree, and have encountered errors. configure error for LAG is: Package requirements (lidarquadtree =1.2 were not met: no package lidarquadtree found. So I went to the lidarquadtree

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Martin Isenburg
Hi, sweet. so can LAG readily read LAZ files then? you can potentially get a lot of speed-up when you load a fenced area if you use the simple spatial query functionality through LASindex that LASlib provides. lasreader-inside() functions instead of doing your own clipping test in line 304 of

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Berin Smaldon
Hi, I tried earlier on this machine and it did not, although I heavily suspect that our system-wide installation is sorely outdated. I will open an issue on github to remind myself to make sure it is capable of doing so, as performance is certainly an area we would like to improve in LAG. I will

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Berin Smaldon
Looks good. LAG does much too much needless copying and memory allocation for my liking. I will open an issue on github to make sure I don't forget to do this. Berin On 23/08/12 14:45, Mateusz Loskot wrote: On 23 August 2012 14:39, Martin Isenburg martin.isenb...@gmail.com wrote:

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Martin Isenburg
Hi Berin, if you use LASlib and you can open LAS files then you can also open LAZ files as the code path is the same. It may be that your LAG file selector does not allow a *.laz ending? In this case simply test by renaming (temporarily) a *.laz file to *.las and try to open it. LASlib decides

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Berin Smaldon
Hi again, I was disappointed to find that the previous developer had just added a function to check the filename ending for .las or .LAS to decide whether a given file is a LAS file or not. I have added .laz and .LAZ for the time being, and merged the changes into the testing branch, where LAG

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Mark Seibel
I copied the .hpp files into /usr/local/include/laslib and the compilation went further. Any suggestions? Now I end up with errors: /usr/bin/ld: cannot find -llaslib /usr/bin/ld: cannot find -ljemalloc collect2: ld returned 1 exit status make[1]: *** [liblidarquadtree.la] Error 1 Mark On

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Mateusz Loskot
On 23 August 2012 15:54, Howard Butler hobu@gmail.com wrote: Martin, When can we convince you that proper source code tracking and versioned releases are prerequisite for people to build upon your software? (off-topic) Next time I'll be driving to Poland, I may stop by Martin's place in

Re: [Liblas-devel] ARSF LiDAR Analysis GUI

2012-08-23 Thread Berin Smaldon
Hi again, Jemalloc is a dependency that I may have forgotten to list. Your package manager ought to be able to provide it if you are using any mainstream Linux flavour. I was worried about that. I have just had a discussion with somebody who knows about our internal installation of laslib and