[pdal] Stats Filter

[Kramer, Oscar]

Hey Andrew,

My conventional scan is simply iterating over each point in the pointview (represents all points in the file), latching min and max UTM E,N. I wrote a small test and it turns out that the StatsFilter does indeed return the exact same bounds as the scan. So I must have wires crossed somewhere else.

Thanks anyway,
Oscar


________________________________
From: Andrew Bell [andrew.bell.ia at gmail.com]
Sent: Friday, June 12, 2015 11:00
To: Kramer, Oscar
Cc: pdal at lists.osgeo.org
Subject: Re: [pdal] Stats Filter

On Fri, Jun 12, 2015 at 3:32 AM, Kramer, Oscar <OKramer at radiantblue.com<mailto:OKramer at radiantblue.com>> wrote:
Hi,

I constructed a reader pipeline with a StatsFilter to determine the geographic bounds of a LAS file. The minimums and maximums (X, Y, Z) however were not the same as those that I latched in a conventional scan over all points. In fact, there were points over ten meters beyond the boundaries determined via StatsFilter. Does StatsFilter take a statistical sampling of points so that extremes might be missed? Is there some property I should set to make sure all points are considered?

The stats filter does not statistically sample.  The behavior you're describing seems incorrect.  I'd need more information to investigate.  If you have a small file you could provide, I could look.  I'd also need to know how you "conventionally scanned" the points.

Thanks,

--
Andrew Bell
andrew.bell.ia at gmail.com<mailto:andrew.bell.ia at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150612/92b942b7/attachment.html>