From besm at pml.ac.uk Thu Aug 23 03:18:09 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 11:18:09 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI Message-ID: <50360361.8000608@pml.ac.uk> 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

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
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.




From mseibel at gmail.com Thu Aug 23 03:58:55 2012 From: mseibel at gmail.com (Mark Seibel) Date: Thu, 23 Aug 2012 06:58:55 -0400 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: <50360361.8000608@pml.ac.uk> References: <50360361.8000608@pml.ac.uk> Message-ID: Fantastic! Looking forward to giving it a go. Mark On Thu, Aug 23, 2012 at 6:18 AM, Berin Smaldon 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 > > >
>
>

> 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 >
> 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.

> >
>
>
> > _______________________________________________ > Liblas-devel mailing list > Liblas-devel at lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/liblas-devel From mateusz at loskot.net Thu Aug 23 04:01:58 2012 From: mateusz at loskot.net (Mateusz Loskot) Date: Thu, 23 Aug 2012 12:01:58 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: Yes, indeed, the project looks great. Mat On 23 August 2012 11:58, Mark Seibel wrote: > Fantastic! Looking forward to giving it a go. > > Mark > > On Thu, Aug 23, 2012 at 6:18 AM, Berin Smaldon 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 >> >> >>
>>
>>

>> 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 >>
>> 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.

>> >>
>>
>>
>> >> _______________________________________________ >> 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 -- Mateusz Loskot, http://mateusz.loskot.net From mseibel at gmail.com Thu Aug 23 06:06:18 2012 From: mseibel at gmail.com (Mark Seibel) Date: Thu, 23 Aug 2012 09:06:18 -0400 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: <50360361.8000608@pml.ac.uk> References: <50360361.8000608@pml.ac.uk> Message-ID: 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 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 > > >
>
>

> 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 >
> 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.

> >
>
>
> > _______________________________________________ > Liblas-devel mailing list > Liblas-devel at lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/liblas-devel From martin.isenburg at gmail.com Thu Aug 23 06:39:36 2012 From: martin.isenburg at gmail.com (Martin Isenburg) Date: Thu, 23 Aug 2012 06:39:36 -0700 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: 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 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 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 > > > > > >
> >
> >

> > 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 > >
> > 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.

> > > >
> >
> >
> > > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mateusz at loskot.net Thu Aug 23 06:45:27 2012 From: mateusz at loskot.net (Mateusz Loskot) Date: Thu, 23 Aug 2012 14:45:27 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: On 23 August 2012 14:39, Martin Isenburg wrote: > > reader->inside_rectangle(fence.getXs()[0], fence.getYs()[0], > fence.getXs()[1], fence.getYs()[1]); Speaking of performance, replace fence.getXs()[0], fence.getYs()[0], fence.getXs()[1], fence.getYs()[1]); with vector const x = fence.getXs(); vector const y = fence.getys(); x[0], y[0], x[1], y[1]); and you are 50% of vector copies less. As SelectionBox is represented by 4 elements only, std::array would be cheaper. "Every little helps." Best regards, -- Mateusz Loskot, http://mateusz.loskot.net From besm at pml.ac.uk Thu Aug 23 06:50:18 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 14:50:18 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: <5036351A.6040402@pml.ac.uk> Hi Mark, Sorry about that, it seems that on our systems we have installed the laslib headers to /usr/local/include/laslib. Problematically, both programs I think expect the headers to be in the format laslib/*.hpp, I'm not sure yet whether that's specific to our system and we should change the program to ignore the "laslib/" prefix, so that the configure script can be configured to point the compiler to any old directory, or whether there is some conventional way of installing laslib that we've followed. I'm afraid Mike, who would know, is away until Tuesday, so I can't say for sure. Your options are to either wait for me to find out and I will set it up how it should be, (configure already points the compiler at both /usr/local/include and /usr/local/include/laslib, so you or I should be able to change any of the include statements over without trouble) OR you can work around it for now if you don't mind the hassle. To work around it, either copy the headers to /usr/local/include/laslib/, or copy them to some local location you'll remember to delete, and as long as they're in a folder called laslib, you'll be able to point the compiler to the parent folder with: export laslib_CFLAGS=-I/path/to/folder # where folder contains laslib/*.hpp export laslib_LIBS=-L/path/to/object/files -llaslib ./configure I'm concerned that our .pc files for laslib are our own version and that there is no official version. I will get back to you on Tuesday with more details on that. Berin On 23/08/12 14:06, Mark Seibel 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 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 >> >> >>
>>
>>

>> 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 >>
>> 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.

>> >>
>>
>>
>> >> _______________________________________________ >> 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
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.




From besm at pml.ac.uk Thu Aug 23 06:56:34 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 14:56:34 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: <50363692.9020905@pml.ac.uk> 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 > 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 > 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 > > > > > >
> >
> >

> > Plymouth Marine Laboratory
> > Registered Office:
> > Prospect Place
> > The Hoe
> > Plymouth PL1 3DH > >

> > > >

Website: href="http://www.pml.ac.uk">www.pml.ac.uk > >
> > href="http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf">Click > here for the latest PML Annual Review > >
> > 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.

> > > >
> >
> >
> > > > _______________________________________________ > > 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
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: From besm at pml.ac.uk Thu Aug 23 06:58:57 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 14:58:57 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> Message-ID: <50363721.6010706@pml.ac.uk> 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 wrote: >> reader->inside_rectangle(fence.getXs()[0], fence.getYs()[0], >> fence.getXs()[1], fence.getYs()[1]); > Speaking of performance, replace > > fence.getXs()[0], fence.getYs()[0], fence.getXs()[1], fence.getYs()[1]); > > with > vector const x = fence.getXs(); > vector const y = fence.getys(); > x[0], y[0], x[1], y[1]); > > and you are 50% of vector copies less. > > As SelectionBox is represented by 4 elements only, std::array would be cheaper. > > "Every little helps." > > Best regards,

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
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.




From martin.isenburg at gmail.com Thu Aug 23 07:08:49 2012 From: martin.isenburg at gmail.com (Martin Isenburg) Date: Thu, 23 Aug 2012 07:08:49 -0700 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: <50363692.9020905@pml.ac.uk> References: <50360361.8000608@pml.ac.uk> <50363692.9020905@pml.ac.uk> Message-ID: 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 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 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 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 >> > >> > >> >
>> >
>> >

>> > 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 >> >
>> > 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.

>> > >> >
>> >
>> >
>> > >> > _______________________________________________ >> > 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 > > 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: From besm at pml.ac.uk Thu Aug 23 07:25:56 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 15:25:56 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> <50363692.9020905@pml.ac.uk> Message-ID: <50363D74.1090805@pml.ac.uk> 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 now appears to load LAZ files without a single hiccup. I should hope to change this in future. For the meantime, anyone who wants this functionality can use git to use the hotfix: git clone git at github.com:arsf/lag.git git checkout testing *compile as usual* Berin On 23/08/12 15:08, Martin Isenburg wrote: > 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 ... >

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
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: From hobu.inc at gmail.com Thu Aug 23 07:54:03 2012 From: hobu.inc at gmail.com (Howard Butler) Date: Thu, 23 Aug 2012 09:54:03 -0500 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: <50363D74.1090805@pml.ac.uk> References: <50360361.8000608@pml.ac.uk> <50363692.9020905@pml.ac.uk> <50363D74.1090805@pml.ac.uk> Message-ID: This looks awesome. I'll add that Grant Brown added a freeglut-based simple viewer (lasviewer) based on PyOpenGL to laspy at https://github.com/grantbrown/laspy . It needs quite a bit of work (addition of mouse navigation would be nice), but the fun part is that it's programmable in pure python. It's primary features are fly-through navigation and RGB/Intensity colorization. PDAL has a freeglut-based simple viewer too, but both of these are simple visualization -- and they're not as useful as LAG appears to be. Martin, When can we convince you that proper source code tracking and versioned releases are prerequisite for people to build upon your software? It's great that LASlib is LGPL, but it's frustrating that we can't refer to release versions, or track your changes in a revision system unless we're doing it ourselves manually. Things like LAG demonstrate the need for this even more clearly. Howard On Aug 23, 2012, at 9:25 AM, Berin Smaldon wrote: > 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 now appears to load LAZ files without a single hiccup. > > I should hope to change this in future. > > For the meantime, anyone who wants this functionality can use git to use the hotfix: > git clone git at github.com:arsf/lag.git > git checkout testing > *compile as usual* > > Berin > > On 23/08/12 15:08, Martin Isenburg wrote: >> >> 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 ... >> > > > > 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 > > > 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. > > > > > > > > > _______________________________________________ > Liblas-devel mailing list > Liblas-devel at lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/liblas-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From mseibel at gmail.com Thu Aug 23 07:57:57 2012 From: mseibel at gmail.com (Mark Seibel) Date: Thu, 23 Aug 2012 10:57:57 -0400 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: <5036351A.6040402@pml.ac.uk> References: <50360361.8000608@pml.ac.uk> <5036351A.6040402@pml.ac.uk> Message-ID: 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 Thu, Aug 23, 2012 at 9:50 AM, Berin Smaldon wrote: > Hi Mark, > > Sorry about that, it seems that on our systems we have installed the > laslib headers to /usr/local/include/laslib. Problematically, both > programs I think expect the headers to be in the format laslib/*.hpp, > I'm not sure yet whether that's specific to our system and we should > change the program to ignore the "laslib/" prefix, so that the configure > script can be configured to point the compiler to any old directory, or > whether there is some conventional way of installing laslib that we've > followed. I'm afraid Mike, who would know, is away until Tuesday, so I > can't say for sure. > > Your options are to either wait for me to find out and I will set it up > how it should be, (configure already points the compiler at both > /usr/local/include and /usr/local/include/laslib, so you or I should be > able to change any of the include statements over without trouble) OR > you can work around it for now if you don't mind the hassle. > > To work around it, either copy the headers to > /usr/local/include/laslib/, or copy them to some local location you'll > remember to delete, and as long as they're in a folder called laslib, > you'll be able to point the compiler to the parent folder with: > > export laslib_CFLAGS=-I/path/to/folder # where folder contains laslib/*.hpp > export laslib_LIBS=-L/path/to/object/files -llaslib > ./configure > > I'm concerned that our .pc files for laslib are our own version and that > there is no official version. I will get back to you on Tuesday with > more details on that. > > Berin > > On 23/08/12 14:06, Mark Seibel 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 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 >>> >>> >>>
>>>
>>>

>>> 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 >>>
>>> 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.

>>> >>>
>>>
>>>
>>> >>> _______________________________________________ >>> 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 >
> 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.

> >
>
>
> From mateusz at loskot.net Thu Aug 23 07:57:52 2012 From: mateusz at loskot.net (Mateusz Loskot) Date: Thu, 23 Aug 2012 15:57:52 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> <50363692.9020905@pml.ac.uk> <50363D74.1090805@pml.ac.uk> Message-ID: On 23 August 2012 15:54, Howard Butler 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 Austria and explain it to Martin over a coffee. Martin, any climbing sites near you? :D Cheers, -- Mateusz Loskot, http://mateusz.loskot.net From martin.isenburg at gmail.com Thu Aug 23 08:12:00 2012 From: martin.isenburg at gmail.com (Martin Isenburg) Date: Thu, 23 Aug 2012 08:12:00 -0700 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> <50363692.9020905@pml.ac.uk> <50363D74.1090805@pml.ac.uk> Message-ID: Hobu / Mateusz, I hear you and I know that it appears as if I have become a lazy bum. But i have 0 spare cycles left now that i try to get rapidlasso up and running. I explained it to Volker Wichmann when me met in Salzburg. I am not really a software developer and so far LAStools has been a one-man gig. I do not have time for anything that adds overhead to my usual way of doing things. Keeping LASzip properly updated on github is bad enough ... |-; That said. I will soon familiarize myself with "your" way of doing things when I release the first version of PulseWaves so things are bound to get better ... (-: Cheers, Martin PS: I am in Frankonia (near Wuerzburg, Germany) at the moment. But I always have time for coffee. (-: On Thu, Aug 23, 2012 at 7:57 AM, Mateusz Loskot wrote: > On 23 August 2012 15:54, Howard Butler 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 > Austria > and explain it to Martin over a coffee. > Martin, any climbing sites near you? :D > > Cheers, > -- > Mateusz Loskot, http://mateusz.loskot.net > _______________________________________________ > Liblas-devel mailing list > Liblas-devel at lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/liblas-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From besm at pml.ac.uk Thu Aug 23 08:22:28 2012 From: besm at pml.ac.uk (Berin Smaldon) Date: Thu, 23 Aug 2012 16:22:28 +0100 Subject: [Liblas-devel] ARSF LiDAR Analysis GUI In-Reply-To: References: <50360361.8000608@pml.ac.uk> <5036351A.6040402@pml.ac.uk> Message-ID: <50364AB4.1000206@pml.ac.uk> 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 now understand better what is going on here. Until I have a workaround, you may be able to configure lidarquadtree and lag in the following way (for both LAG and lidarquadtree): export laslib_LIBS=-L/path/to/lastools/laslib/lib -llaslib ./configure These problems have brought an important issue to light, so thankyou for the quick responses. Berin > 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 Thu, Aug 23, 2012 at 9:50 AM, Berin Smaldon wrote:

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
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.




From pwtittmann at ucdavis.edu Tue Aug 28 17:18:18 2012 From: pwtittmann at ucdavis.edu (Peter Tittmann) Date: Tue, 28 Aug 2012 17:18:18 -0700 Subject: [Liblas-devel] piping lasmerge to las2las Message-ID: Hi Liblas-ers, I have several .las tiles which, depending upon the analysis region of interest (i.e on the boundary between two tiles) may need to be merged and then clipped. Ideally, id like to pipe the output of lasmerge to las2las with the --extent flag. An example from the lasmerge --help indicates stout as an option. However it seems to just create a file called 'stdout': lasmerge -i ~/Data/Lidar201104/LAS/ALL_POINTS/PC_025.las -i ~/Data/Lidar201104/LAS/ALL_POINTS/PC_026.las --stdout adds a file called 'stout' to the working directory Further, las2las doesn't seem to recognized the --stdin flag, so I'm worried that this is not an option. lasmerge -i ~/Data/Lidar201104/LAS/ALL_POINTS/PC_025.las -i ~/Data/Lidar201104/LAS/ALL_POINTS/PC_026.las --stdout | las2las --stdin -e 471400.920313 5014482.90021 471436.91534 5014518.90834 -o ../plot_las/110102.las -- Peter Tittmann, Ph.D. Postdoctoral researcher Energy Institute Institute for Transportation Studies UC Davis -------------- next part -------------- An HTML attachment was scrubbed... URL: