[Liblas-devel] problem accessing point_source_id using Python API
Stanley Wong
s.wong at kucerainternational.com
Tue Jun 5 11:57:51 PDT 2012
Doug,
Thanks for the suggestion. That is a good check.
The output from las2txt also confirmed that the point source id is assigned in the LAS file, and it is non-zero.
Stanley
----- Original Message -----
From: "Doug Newcomb" <Doug_Newcomb at fws.gov>
To: "Stanley Wong" <s.wong at kucerainternational.com>
Cc: "Liblas-devel at lists.osgeo.org" <liblas-devel at lists.osgeo.org>, liblas-devel-bounces at lists.osgeo.org
Sent: Tuesday, June 5, 2012 1:34:47 PM
Subject: Re: [Liblas-devel] problem accessing point_source_id using Python API
Stanley,
What do you get as output for point source id if you dump one of your las files to comma separated text? http://liblas.org/utilities/las2txt.html . I ask because I have seen several las files that have been missing parts :-)
Doug
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb at fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
Stanley Wong <s.wong at kucerainternational.com>
Sent by: liblas-devel-bounces at lists.osgeo.org
06/05/2012 12:43 PM
To "Liblas-devel at lists.osgeo.org" <liblas-devel at lists.osgeo.org>
cc
Subject [Liblas-devel] problem accessing point_source_id using Python API
Hi,
I am trying to read point_source_id of lidar points using Python API like below:
inLas = liblas.file.File(r'<path>\test.las',None, 'r')
pt = inLas[0]
print pt.point_source_id
I keep getting value 0 on the point_source_id values in all the files I tested. No problem on getting all other properties of Point, just not point_source_id. I confirmed that the point source values are assigned in those LAS files using other software (LP360 and TerraSolid).
I have 2 liblas python installation on Windows 7, 1.7.0-2 from OSGeo4W, and 1.6.0 from pypi.python.org. Both gave me the same results.
Can someone please let me know if this is a liblas setup problem, a bug on Python API, or simply wrong code on my part?
Thanks,
Stanley _______________________________________________
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: <http://lists.osgeo.org/pipermail/liblas-devel/attachments/20120605/4679e354/attachment.html>
More information about the Liblas-devel
mailing list