[prev in list] [next in list] [prev in thread] [next in thread]
List: grass-user
Subject: Re: [GRASS-user] LiDAR LAS import
From: Rebecca Bennett <rabennett () ymail ! com>
Date: 2011-07-29 11:10:02
Message-ID: 1311937802.27227.YahooMailNeo () web28409 ! mail ! ukl ! yahoo ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
sorry for the delayed reply - (windoze day yesterday)
>Hmm. Is lasinfo --help working?
Yes. wont paste the output here but it is as expected.
>liblas-config --libs
-L/usr/lib -lgeotiff -L/usr/lib -lgdal1.6.0
>liblas-config --includes
-I/usr/include/geotiff -I/usr/include/gdal
Thanks,
Rebecca
>________________________________
>From: Markus Metz <markus.metz.giswork@googlemail.com>
>To: Rebecca Bennett <rabennett@ymail.com>
>Cc: "grass-user@lists.osgeo.org" <grass-user@lists.osgeo.org>
>Sent: Wednesday, 27 July 2011, 18:01
>Subject: Re: [GRASS-user] LiDAR LAS import
>
>On Wed, Jul 27, 2011 at 3:28 PM, Rebecca Bennett <rabennett@ymail.com> wrote:
>> sure -
>>
>> checking whether to use libLAS... yes
>> checking for liblas-config... /usr/bin/liblas-config
>> configure: error: *** Unable to locate libLAS library.
>>
>> I have the packages liblas1, liblas-dev, lib-las-bin and python-liblas
>> installed through synaptic and am wondering if there is a libraty package
>> missing?
>
>Hmm. Is lasinfo --help working?
>
>What does
>liblas-config --libs
>and
>liblas-config --includes
>say?
>
>
>>
>> ________________________________
>> From: Markus Metz <markus.metz.giswork@googlemail.com>
>> To: Rebecca Bennett <rabennett@ymail.com>
>> Cc: "grass-user@lists.osgeo.org" <grass-user@lists.osgeo.org>
>> Sent: Wednesday, 27 July 2011, 13:16
>> Subject: Re: [GRASS-user] LiDAR LAS import
>>
>> Rebecca Bennett wrote:
>>> Hello,
>>> Just trying to install GRASS 7 on Ubuntu 10.04 to try out the las import
>>> functions but I'm getting error messages during the configure that it is
>>> unable to find the liblas library, however the liblas library is installed
>>> in usr/bin/lib/ so I'm a bit puzzled...
>>
>> Can you post the exact error message? Also, liblas support will only
>> be available if liblas-config exists.
>>
>> Markus M
>>
>>> Did anyone else get stuck here or am I missing something obvious?
>>> Thanks for reading,
>>> Rebecca
>>>
>>> ________________________________
>>> From: Markus Metz <markus.metz.giswork@googlemail.com>
>>> To: Hamish <hamish_b@yahoo.com>
>>> Cc: grass-user <grass-user@lists.osgeo.org>; GRASS developers list
>>> <grass-dev@lists.osgeo.org>
>>> Sent: Wednesday, 25 May 2011, 12:48
>>> Subject: Re: [GRASS-user] LiDAR LAS import
>>>
>>> On Wed, May 25, 2011 at 12:16 PM, Hamish <hamish_b@yahoo.com> wrote:
>>>> Markus Metz wrote:
>>>>> Hi all,
>>>>>
>>>>> GRASS 7 has a new module v.in.lidar for importing LiDAR LAS files
>>>>> (*.las or *.laz). The LAS file format is commonly used for storing
>>>>> LiDAR point clouds, but is unfortunately not supported by OGR.
>>>>> v.in.lidar uses the libLAS library [0] and is only compiled if the
>>>>> libLAS library is present.
>>>>>
>>>>> I chose to use the library instead of writing a custom LAS reading
>>>>> interface because the current LAS library version 1.6.1 is stable,
>>>>> supports LAS file versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, each of
>>>>> which can store LiDAR points in up to 5 different point formats. The
>>>>> user and the interface do not need to know the file version and point
>>>>> format of a given file, all that is conveniently handled by the libLAS
>>>>> library in the background. The library has Large File Support (LFS)
>>>>> and is well tested on different platforms, also with different
>>>>> endian-ness. This functionality is not that easy to replicate.
>>>>>
>>>>> You will need to get the libLAS library and configure GRASS 7 with
>>>>> --with-liblas in order to have the module available. Please test!
>>>>>
>>>>> Markus M
>>>>>
>>>>> [0] http://www.liblas.org
>>>>
>>>>
>>>> neat! any time trials to say how much faster it is than piping
>>>> las2txt | v.in.ascii
>>>> ?
>>>
>>> Note that las2txt does NOT apply scale and offset to x,y,z, this would
>>> need to be done afterwards in order to obtain correct coordinates.
>>> Therefore the output of las2txt | v.in.ascii with the sample las file
>>> I used is incorrect.
>>>
>>> I discovered a bug in v.in.ascii: from a point file with | as field
>>> separator like
>>>
>>> 1|2|3||5|6
>>>
>>> only the first 3 columns will be imported because column 4 is empty
>>> which means that columns 5 and 6 are skipped.
>>>
>>> v.in.lidar is a notch faster than las2txt | v.in.ascii. And easier to
>>> use...
>>> Speed comparisons:
>>>
>>> # sample las file with 1,287,775 points
>>>
>>> # with table and topology
>>> time las2txt -i points.las --stdout --parse xyztinrcCpedRGBau
>>> --delimiter "|" | v.in.ascii in=- out=points_ascii -z x=1 y=2 z=3 --o
>>>
>>> real 6m34.430s
>>> user 4m57.530s
>>> sys 2m3.693s
>>>
>>> time v.in.lidar in=points.las out=points_las -o --o
>>>
>>> real 6m13.823s
>>> user 4m32.061s
>>> sys 2m1.068s
>>>
>>>
>>> # without table, with topology
>>> time las2txt -i points.las --stdout --parse xyz --delimiter "|" |
>>> v.in.ascii in=- out=points_ascii -zt x=1 y=2 z=3 --o
>>>
>>> real 1m53.578s
>>> user 1m47.032s
>>> sys 0m9.238s
>>>
>>> time v.in.lidar in=points.las out=points_las -ot --o
>>>
>>> real 1m44.876s
>>> user 1m34.450s
>>> sys 0m8.488s
>>> _______________________________________________
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>>
>>>
>>> _______________________________________________
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>>
>>
>>
>>
>
>
>
[Attachment #5 (text/html)]
<html><body><div style="color:#000; background-color:#fff; font-family:verdana, \
helvetica, sans-serif;font-size:10pt"><div>sorry for the delayed reply - (windoze day \
yesterday)</div><div><br></div><div>>Hmm. Is lasinfo --help \
working?</div><div><br></div><div>Yes. wont paste the output here but it is as \
expected.<br></div><div><br></div><div>>liblas-config --libs<br>-L/usr/lib \
-lgeotiff -L/usr/lib -lgdal1.6.0</div><div><br></div>>liblas-config \
--includes<br>-I/usr/include/geotiff \
-I/usr/include/gdal<br><br>Thanks,<br><br>Rebecca<div><br><blockquote \
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: \
5px;"><div style="font-family: verdana,helvetica,sans-serif; font-size: 10pt;"><div \
style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font \
face="Arial" size="2"><hr size="1"><b><span style="font-weight: \
bold;">From:</span></b> Markus Metz \
<markus.metz.giswork@googlemail.com><br><b><span style="font-weight: \
bold;">To:</span></b> Rebecca Bennett <rabennett@ymail.com><br><b><span \
style="font-weight: bold;">Cc:</span></b> "grass-user@lists.osgeo.org" \
<grass-user@lists.osgeo.org><br><b><span style="font-weight: \
bold;">Sent:</span></b> Wednesday, 27 July 2011, 18:01<br><b><span \
style="font-weight: bold;">Subject:</span></b> Re: [GRASS-user] LiDAR LAS \
import<br></font><br>On Wed, Jul 27, 2011 at 3:28 PM, Rebecca Bennett <<a \
ymailto="mailto:rabennett@ymail.com" \
href="mailto:rabennett@ymail.com">rabennett@ymail.com</a>> wrote:<br>> sure \
-<br>><br>> checking whether to use libLAS... yes<br>> checking for \
liblas-config... /usr/bin/liblas-config<br>> configure: error: *** Unable to \
locate libLAS library.<br>><br>> I have the packages liblas1, liblas-dev, \
lib-las-bin and python-liblas<br>> installed through synaptic and am wondering if \
there is a libraty package<br>> missing?<br><br>Hmm. Is lasinfo
--help working?<br><br>What does<br>liblas-config --libs<br>and<br>liblas-config \
--includes<br>say?<br><br><br>><br>> ________________________________<br>> \
From: Markus Metz <<a ymailto="mailto:markus.metz.giswork@googlemail.com" \
href="mailto:markus.metz.giswork@googlemail.com">markus.metz.giswork@googlemail.com</a>><br>> \
To: Rebecca Bennett <<a ymailto="mailto:rabennett@ymail.com" \
href="mailto:rabennett@ymail.com">rabennett@ymail.com</a>><br>> Cc: "<a \
ymailto="mailto:grass-user@lists.osgeo.org" \
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>" <<a \
ymailto="mailto:grass-user@lists.osgeo.org" \
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>><br>> \
Sent: Wednesday, 27 July 2011, 13:16<br>> Subject: Re: [GRASS-user] LiDAR LAS \
import<br>><br>> Rebecca Bennett wrote:<br>>> Hello,<br>>> Just \
trying to install GRASS 7 on Ubuntu 10.04 to try out the las import<br>>> \
functions but I'm getting error messages during the configure that it is<br>>> \
unable to find the liblas library, however the liblas library is \
installed<br>>> in usr/bin/lib/ so I'm a bit puzzled...<br>><br>> Can you \
post the exact error message? Also, liblas support will only<br>> be available if \
liblas-config exists.<br>><br>> Markus M<br>><br>>> Did anyone else \
get stuck here or am I missing something obvious?<br>>> Thanks for \
reading,<br>>> Rebecca<br>>><br>>> \
________________________________<br>>> From: Markus Metz <<a \
ymailto="mailto:markus.metz.giswork@googlemail.com" \
href="mailto:markus.metz.giswork@googlemail.com">markus.metz.giswork@googlemail.com</a>><br>>> \
To: Hamish <<a ymailto="mailto:hamish_b@yahoo.com" \
href="mailto:hamish_b@yahoo.com">hamish_b@yahoo.com</a>><br>>> Cc: \
grass-user <<a ymailto="mailto:grass-user@lists.osgeo.org" \
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>>; GRASS \
developers list<br>>> <<a ymailto="mailto:grass-dev@lists.osgeo.org" \
href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a>><br>>> \
Sent: Wednesday, 25 May 2011, 12:48<br>>> Subject: Re: [GRASS-user] LiDAR LAS \
import<br>>><br>>> On Wed, May 25, 2011 at 12:16 PM, Hamish <<a \
ymailto="mailto:hamish_b@yahoo.com" \
href="mailto:hamish_b@yahoo.com">hamish_b@yahoo.com</a>> wrote:<br>>>> \
Markus Metz wrote:<br>>>>> Hi \
all,<br>>>>><br>>>>> GRASS 7 has a new module v.in.lidar for \
importing LiDAR LAS files<br>>>>> (*.las or *.laz). The LAS file format \
is commonly used for storing<br>>>>> LiDAR point clouds, but is \
unfortunately not supported by OGR.<br>>>>> v.in.lidar uses the libLAS \
library [0] and is only compiled if the<br>>>>> libLAS library is \
present.<br>>>>><br>>>>> I chose to use the library instead \
of writing a custom LAS reading<br>>>>> interface because the current LAS \
library version 1.6.1 is stable,<br>>>>> supports LAS file versions 1.0, \
1.1, 1.2, 1.3, 1.4, 1.5, 1.6, each of<br>>>>> which can store LiDAR \
points in up to 5 different point formats. The<br>>>>> user and the \
interface do not need to know the file version and point<br>>>>> format \
of a given file, all that is conveniently handled by the libLAS<br>>>>> \
library in the background. The library has Large File Support \
(LFS)<br>>>>> and is well tested on different platforms, also with \
different<br>>>>> endian-ness. This functionality is not that easy to \
replicate.<br>>>>><br>>>>> You will need to get the libLAS \
library and configure GRASS 7 with<br>>>>>
--with-liblas in order to have the module available. Please \
test!<br>>>>><br>>>>> Markus \
M<br>>>>><br>>>>> [0] <a href="http://www.liblas.org" \
target="_blank">http://www.liblas.org</a><br>>>><br>>>><br>>>> \
neat! any time trials to say how much faster it is than piping<br>>>> \
las2txt | v.in.ascii<br>>>> ?<br>>><br>>> Note that \
las2txt does NOT apply scale and offset to x,y,z, this would<br>>> need to be \
done afterwards in order to obtain correct coordinates.<br>>> Therefore the \
output of las2txt | v.in.ascii with the sample las file<br>>> I used is \
incorrect.<br>>><br>>> I discovered a bug in v.in.ascii: from a point \
file with | as field<br>>> separator like<br>>><br>>> \
1|2|3||5|6<br>>><br>>> only the first 3 columns will be imported because \
column 4 is empty<br>>> which means that columns 5 and 6 are \
skipped.<br>>><br>>> v.in.lidar is a notch faster than las2txt | \
v.in.ascii. And easier to<br>>> use...<br>>> Speed \
comparisons:<br>>><br>>> # sample las file with 1,287,775 \
points<br>>><br>>> # with table and topology<br>>> time las2txt -i \
points.las --stdout --parse xyztinrcCpedRGBau<br>>> --delimiter "|" | \
v.in.ascii in=- out=points_ascii -z x=1 y=2 z=3 --o<br>>><br>>> \
real 6m34.430s<br>>> user \
4m57.530s<br>>> sys 2m3.693s<br>>><br>>> time \
v.in.lidar in=points.las out=points_las -o --o<br>>><br>>> \
real 6m13.823s<br>>> user \
4m32.061s<br>>> sys \
2m1.068s<br>>><br>>><br>>> # without table, with \
topology<br>>> time las2txt -i points.las --stdout --parse xyz --delimiter "|" \
|<br>>> v.in.ascii in=- out=points_ascii -zt x=1 y=2 z=3 \
--o<br>>><br>>> real 1m53.578s<br>>> \
user 1m47.032s<br>>> sys \
0m9.238s<br>>><br>>> time v.in.lidar in=points.las out=points_las -ot \
--o<br>>><br>>> real 1m44.876s<br>>> \
user 1m34.450s<br>>> sys \
0m8.488s<br>>> _______________________________________________<br>>> \
grass-user mailing list<br>>> <a ymailto="mailto:grass-user@lists.osgeo.org" \
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>>> \
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" \
target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>>><br>>><br>>><br>>> \
_______________________________________________<br>>> grass-user mailing \
list<br>>> <a ymailto="mailto:grass-user@lists.osgeo.org" \
href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>>> \
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" \
target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>>><br> \
>><br>><br>><br>><br><br><br></div></div></blockquote></div></div></body></html>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic