[Liblas-devel] ARSF LiDAR Analysis GUI
Martin Isenburg
martin.isenburg at gmail.com
Thu Aug 23 07:08:49 PDT 2012
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
based in the content (not the ending) whether the LAS file is compressed of
not.
Cheers,
Martin
PS: if you use lasreadopener, then you would also
BIN/SHP/QFIT/ASCII/ASC/BIL support that would get opened "as if" they were
LAS files ...
On Thu, Aug 23, 2012 at 6:56 AM, Berin Smaldon <besm at pml.ac.uk> wrote:
> **
> 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 open an issue now though to remind myself to make that change,
> since that seems like a logical thing to do. If there is any other laslib
> documentation and tips anywhere then I will be glad to look through and see
> if there's any easy changes I can make to improve performance.
>
> Berin
>
> On 23/08/12 14:39, Martin Isenburg wrote:
>
> 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 LoadWorker.cpp
>
> if (usearea)
> {
> if (!vectorTest(fence.getXs(), fence.getYs(), 4,
> reader->point.get_x(), reader->point.get_y()))
> {
> skip_counter = 0;
> continue;
> }
>
> }
>
> instead you would put a
>
> reader->inside_rectangle(fence.getXs()[0], fence.getYs()[0],
> fence.getXs()[1], fence.getYs()[1]);
>
> at the beginning of the reader loop and then LASlib will utilize the
> spatially indexing LAX files should they be present or not give you any win
> otherwise. For the moment you need to dig through code and LAStools user
> forum to learn more about LASindex, but I will present the details at this
> year's ELMF in Salzburg
>
> Cheers,
>
> Martin @rapidlasso
>
> On Thu, Aug 23, 2012 at 6:06 AM, Mark Seibel <mseibel at gmail.com> wrote:
>
>> 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 directory in the lidarsf-lag-53d94dd
>> directory and did ./configure and make.
>>
>> Make returned this error:
>> In file included from src/LidarPoint.cpp:34:0:
>> src/LidarPoint.h:38:37: fatal error: laslib/lasdefinitions.hpp: No
>> such file or directory
>> compilation terminated.
>>
>> I have the lasdefinitions.hpp file in the laslib directory, but it is
>> in ../lastools/laslib/inc/lasdefinitions.hpp
>>
>> How do I make configure aware of this file's location? I know I'm
>> missing something obvious, but I just cant see it.
>>
>> Thanks,
>> Mark
>>
>> On Thu, Aug 23, 2012 at 6:18 AM, Berin Smaldon <besm at pml.ac.uk> wrote:
>> > As I gather, open source LAS viewers have been in short supply for
>> some
>> > time now, and having been talked about for over a year, we're finally
>> > getting around to announcing a GPL licensed LAS viewer that Mike Grant
>> > has been promising since the dawn of time. For now, this only works on
>> Linux, but
>> > I'm already working on the Windows port, the purpose here being to get
>> > people using the software to attract bug reports, ideas and development.
>> > So, feel free to try and get it working, I'll be interested to know how
>> > it co-operates with other systems.
>> >
>> > Here is the splash page: http://arsf.github.com/lag/
>> >
>> > The link explains what to do to build it for your Linux system if
>> you're so inclined, the Windows port is a bit of a way off yet though, but
>> in the pipeline. If it were useful to enough people, I could potentially be
>> persuaded to work out how to build packages for some Linux package managers
>> too.
>> >
>> > I acknowledge that the quality of the source code is poor in places.
>> > There have been a number of student programmers before me having pretty
>> > much free rein over how the program is structured and what conventions
>> > are used. Documentation and improving the quality of the code is high on
>> > my priority list, but not on the top of it. For now, my e-mail address
>> > and the github page are the best sources of information, and will help
>> > me work out how the github wiki pages could be more useful. In a few
>> months when I'm no longer on the project, whatever e-mail address is on the
>> splash screen or latest version of the software will have to do instead.
>> >
>> > Enjoy,
>> > Berin
>> >
>> >
>> > <br />
>> > <hr />
>> > <p><font face="Arial" size="1">
>> > Plymouth Marine Laboratory<br />
>> > Registered Office: <br />
>> > Prospect Place<br />
>> > The Hoe<br />
>> > Plymouth PL1 3DH
>> > </font></p>
>> >
>> > <p><font face="Arial" size="1">Website: <a href="http://www.pml.ac.uk">
>> www.pml.ac.uk</a>
>> > <br />
>> > <a href="http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf">Click
>> here for the latest PML Annual Review</a>
>> > <br />
>> > Registered Charity No. 1091222<br />
>> > PML is a company limited by guarantee<br />
>> > registered in England & Wales<br />
>> > company number 4178503</font></p>
>> >
>> > <p><font face="Arial" size="1" color="green">Please think before you
>> print.</font></p>
>> >
>> > <hr />
>> >
>> > <p><font face="Arial" size="1">This e-mail, its content and any file
>> attachments are confidential.</font></p>
>> >
>> > <p><font face="Arial" size="1">If you have received this e-mail in
>> error please do not copy, disclose it to any third party or use the
>> contents or attachments in any way. Please notify the sender by replying to
>> this e-mail or e-mail forinfo at pml.ac.uk and then delete the email
>> without making any copies or using it in any other way.</font></p>
>> >
>> > <p><font face="Arial" size="1">The content of this message may contain
>> personal views which are not the views of Plymouth Marine Laboratory unless
>> specifically stated.</font></p>
>> >
>> > <p><font face="Arial" size="1">You are reminded that e-mail
>> communications are not secure and may contain viruses. Plymouth Marine
>> Laboratory accepts no liability for any loss or damage which may be caused
>> by viruses.</font></p>
>> >
>> > <hr />
>> > <br />
>> > <br />
>> >
>> > _______________________________________________
>> > Liblas-devel mailing list
>> > Liblas-devel at lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/liblas-devel
>> _______________________________________________
>> Liblas-devel mailing list
>> Liblas-devel at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/liblas-devel
>>
>
>
>
> ------------------------------
>
>
> Plymouth Marine Laboratory
>
> Registered Office:
>
> Prospect Place
>
> The Hoe
>
> Plymouth PL1 3DH
>
> Website: www.pml.ac.uk
>
> Click here for the latest PML Annual Review <http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf>
>
> Registered Charity No. 1091222
>
>
> PML is a company limited by guarantee
>
> registered in England & Wales
>
> company number 4178503
>
> Please think before you print.
>
> ------------------------------
>
> This e-mail, its content and any file attachments are confidential.
>
> If you have received this e-mail in error please do not copy, disclose it to any third party or use the contents or attachments in any way. Please notify the sender by replying to this e-mail or e-mail forinfo at pml.ac.uk and then delete the email without making any copies or using it in any other way.
>
> The content of this message may contain personal views which are not the views of Plymouth Marine Laboratory unless specifically stated.
>
> You are reminded that e-mail communications are not secure and may contain viruses. Plymouth Marine Laboratory accepts no liability for any loss or damage which may be caused by viruses.
>
> ------------------------------
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/liblas-devel/attachments/20120823/d3cd7090/attachment.html>
More information about the Liblas-devel
mailing list