From howard at hobu.co  Tue Apr  1 16:13:19 2025
From: howard at hobu.co (Howard Butler)
Date: Tue, 1 Apr 2025 18:13:19 -0500
Subject: [pdal] filter.crop option "ogr"
In-Reply-To: <trinity-3d97f3fe-9026-4a49-8ef3-049d9632dd45-1743430279076@trinity-msg-rest-gmx-gmx-live-5779db864f-pmzwq>
References: <trinity-7acb314d-ee91-448b-a3e5-e9c5a1fa8e6e-1743428451369@trinity-msg-rest-gmx-gmx-live-5779db864f-9sbgp>
 <385F0C72-B275-4C0F-8158-E33CE31B13F8@hobu.co>
 <trinity-3d97f3fe-9026-4a49-8ef3-049d9632dd45-1743430279076@trinity-msg-rest-gmx-gmx-live-5779db864f-pmzwq>
Message-ID: <EED010DA-797E-423D-AFB4-D03843636A1F@hobu.co>

What does your pipeline look like?

> On Mar 31, 2025, at 9:11?AM, Roland Spielhofer via pdal <pdal at lists.osgeo.org> wrote:
> 
> Thanks Howard for clarifying this.
> The reason why I am trying to use filters.crop is the following:
> I am trying to find the max(z) in each of a number of polygons.
> I found
> https://stackoverflow.com/questions/75907829/can-pdal-be-used-to-find-the-max-point-in-each-of-a-set-of-polygons
> that exactly describes what I want to do, but I do not have the WKT geometries.
>  
> When I use the filters.assign and filters.expression workflow, I get only one single point, not one per polygon.
>  
> Is there a difference how filters.crop works compared to filters.assign/filters.expression that effects the outcome of filters.locate?
>  
> Regards,
> Roland
>  
> Gesendet: Montag, 31. M?rz 2025 um 15:43
> Von: "Howard Butler" <howard at hobu.co>
> An: "Roland Spielhofer" <rspiel at gmx.net>
> CC: pdal at lists.osgeo.org
> Betreff: Re: [pdal] filter.crop option "ogr"
> Roland,
>  
> This feature is a 2.9.0+ thing, which has not been released yet.
>  
> https://pdal.io/en/2.8.4/stages/filters.crop.html doesn't show any 'ogr' option. You can achieve a similar outcome by using filters.assign to label points and filters.expression to cull them https://pdal.io/en/2.8.4/workshop/manipulation/clipping/clipping.html#workshop-clipping
>  
> Howard
> 
> On Mar 31, 2025, at 8:40?AM, Roland Spielhofer via pdal <pdal at lists.osgeo.org> wrote:
> 
> Hi,
> I am trying to use the option "ogr" in filters.crop.
>  
> ...
> {
>         "type":"filters.crop",
>         "ogr":{
>             "type":"ogr",
>             "datasource": ["Buffers.shp"],
>             "drivers":"ESRI Shapefile"
>         }
>      },
> ...
>  
> When doing so, I get
> "PDAL: filters.crop: Unexpected argument 'ogr'."
>  
> My version:
> (lidar) Q:\.....\PDAL>pdal --version
> --------------------------------------------------------------------------------
> pdal 2.8.4 (git-version: Release)
> --------------------------------------------------------------------------------
> on Windows/Conda
>  
> Is "ogr" already included in v2.8.4?
>  
> Thanks!
> Roland
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20250401/085c1720/attachment.htm>

From rspiel at gmx.net  Wed Apr  2 02:54:16 2025
From: rspiel at gmx.net (Roland Spielhofer)
Date: Wed, 2 Apr 2025 09:54:16 +0000
Subject: [pdal] filter.crop option "ogr"
In-Reply-To: <EED010DA-797E-423D-AFB4-D03843636A1F@hobu.co>
References: <trinity-7acb314d-ee91-448b-a3e5-e9c5a1fa8e6e-1743428451369@trinity-msg-rest-gmx-gmx-live-5779db864f-9sbgp>
 <385F0C72-B275-4C0F-8158-E33CE31B13F8@hobu.co>
 <trinity-3d97f3fe-9026-4a49-8ef3-049d9632dd45-1743430279076@trinity-msg-rest-gmx-gmx-live-5779db864f-pmzwq>
 <EED010DA-797E-423D-AFB4-D03843636A1F@hobu.co>
Message-ID: <trinity-4046a307-e33a-485f-bd3b-a612aadf706a-1743587656766@trinity-msg-rest-gmx-gmx-live-5cffc45595-2cgwt>

An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20250402/da55b1ea/attachment-0001.htm>