[pdal] pdal translate cropping problem/question

[Andrew Bell]

Fixed.

On Wed, Aug 19, 2015 at 2:22 PM, Stefan Ziegler
<stefan.ziegler.de at gmail.com> wrote:
> The "pdal tindex --merge" command still requires a BOX3D. Could this also be
> changed to 2D to be more consistent?
>
> regards
> Stefan
>
> On Tue, Aug 18, 2015 at 2:44 PM, Howard Butler <howard at hobu.co> wrote:
>>
>> Absolutely. It has to do much less comparison and indexing work, and it
>> doesn't have to light up GEOS.
>>
>> > On Aug 18, 2015, at 6:31 AM, Stefan Ziegler
>> > <stefan.ziegler.de at gmail.com> wrote:
>> >
>> > Is --bounds faster than --polygon?
>> >
>> > Stefan
>> >
>> > On Mon, Aug 17, 2015 at 11:30 PM, Andrew Bell <andrew.bell.ia at gmail.com>
>> > wrote:
>> > I've recreated the problem.  I don't have any trouble when using
>> > --bounds.  We're passing the points through to GEOS to filter based on the
>> > provided polygon.  I'll have to research further.  On-the-line should count
>> > as in.
>> >
>> > On Mon, Aug 17, 2015 at 3:32 PM, Stefan Ziegler
>> > <stefan.ziegler.de at gmail.com> wrote:
>> > Yes.
>> >
>> > Stefan
>> >
>> > Sent from my iPhone
>> >
>> > On 17 Aug 2015, at 22:03, Andrew Bell <andrew.bell.ia at gmail.com> wrote:
>> >
>> >> On Mon, Aug 17, 2015 at 8:04 AM, Stefan Ziegler
>> >> <stefan.ziegler.de at gmail.com> wrote:
>> >> I'd guess they lie near the border. The polygon is the boundary
>> >> generated with "pdal tindex" for this las file so this is why I think it's
>> >> strange that cropping a las file with its own boundary delivers not all
>> >> points in this las file.
>> >>
>> >> Are you using --fast-boundary when you generate the index file?
>> >>
>> >> --
>> >> Andrew Bell
>> >> andrew.bell.ia at gmail.com
>> >
>> >
>> >
>> > --
>> > Andrew Bell
>> > andrew.bell.ia at gmail.com
>> >
>>
>



-- 
Andrew Bell
andrew.bell.ia at gmail.com