[pdal] Digitized building footprints

[adam steer]

So your aim is to label building points?

If yes, then overlay seems like the least resistance way (I haven't played
with that enough, I'd implicitly trust Howard here though) :)

My maybe-useful addition is that it'll conceptually still work just fine if
you have to tile things up, there's no neighbourhood usage going on. So no
need to try and jam things all into one giant memory blob.

Cheers

Adam

On Tue, 30 Jun 2020 at 04:03, Andrew Bell <andrew.bell.ia at gmail.com> wrote:

>
>
> On Mon, Jun 29, 2020 at 1:20 PM Stephen V. Mather <
> svm at clevelandmetroparks.com> wrote:
>
>> Ha! Ok, my gut was right. Rasters it is.
>>
>> And by massive, I just mean 80k images worth of photogrammetric point
>> clouds over 300km2. I know I estimated how many points that is at one
>> point, but I don't recall now. 😄
>>
>> [image: http://sig.cmparks.net/cmp-ms-90x122.png] *Stephen V. Mather*
>> GIS Manager
>> (216) 635-3243 (Work)
>> clevelandmetroparks.com <http://www.clemetparks.com>
>>
>>
>>
>>
>> ------------------------------
>> *From:* Howard Butler <howard at hobu.co>
>> *Sent:* Monday, June 29, 2020 12:50 PM
>> *To:* Stephen V. Mather <svm at clevelandmetroparks.com>
>> *Cc:* pdal <pdal at lists.osgeo.org>
>> *Subject:* Re: [pdal] Digitized building footprints
>>
>>
>> *WARNING: This email originated outside of Cleveland Metroparks. DO NOT
>> CLICK links or attachments unless you recognize the sender and know the
>> content is safe.*
>>
>>
>> On Jun 29, 2020, at 10:18 AM, Stephen V. Mather <
>> svm at clevelandmetroparks.com> wrote:
>>
>> Hi All,
>>
>> I am processing a dataset for which I have a digitized building
>> footprints. It'd be even cooler if I had vegetation, but beggers !=
>> choosers.
>>
>> In principle, I could use filters.overlay, but this is a massive dataset,
>> so I am curious if it makes more sense to rasterize, tile things up, and
>> use filters.colorization.
>>
>>
>> Define massive ;)
>>
>> I think your instinct to rasterize the footprints is the right one here.
>> filters.overlay is going to do point-in-polygon for every point/poly combo.
>> Most are quickly thrown out, but you're going to be checking every one. A
>> raster mask is going to be much quicker, and you can control the resolution
>> with gdal_rasterize.
>>
>
> I don't know why you wouldn't use the overlay/range option. I don't know
> any reason why this would be slow and it seems simple.
>
> --
> Andrew Bell
> andrew.bell.ia at gmail.com
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal



-- 
Dr. Adam Steer
http://spatialised.net
https://www.researchgate.net/profile/Adam_Steer
http://au.linkedin.com/in/adamsteer
http://orcid.org/0000-0003-0046-7236
+61 427 091 712 ::  @adamdsteer

Suits are bad for business: http://www.spatialised.net/business-penguins/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20200630/27335d0c/attachment.html>