Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behavior of Pipeline.arrays with/without filter step #141

Open
spolloni opened this issue Dec 29, 2022 · 0 comments
Open

Behavior of Pipeline.arrays with/without filter step #141

spolloni opened this issue Dec 29, 2022 · 0 comments

Comments

@spolloni
Copy link

spolloni commented Dec 29, 2022

When trying to query Lidar out-of-bounds from an EPT, we noticed that Pipeline.arrays returns different objects based on whether the pipeline contains a Filter step or not:

import pdal

filename = 'https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_NY_LongIsland_Z18_2014_LAS_2015/ept.json'
bounds = '([8126849, 8126859],[-4980069, -4980059])' # far far away from Long Island, NY

# without filter
pipeline = pdal.Reader.ept(filename=filename, bounds=bounds).pipeline()
pipeline.execute()
print(pipeline.arrays) #  non-empty list containing one empty array

# with filter
pipeline = pdal.Reader.ept(filename=filename, bounds=bounds).pipeline()
pipeline |= pdal.Filter.range(limits='Classification[1:31]')
pipeline.execute()
print(pipeline.arrays) #  empty list

wondering if this is by design or should be tweaked to be consistent where there are no points to return.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant