-
Notifications
You must be signed in to change notification settings - Fork 129
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
Support EPT point cloud as input? #291
Comments
@joaori Hi there. Seems you're not the only one to have encountered this. Did you find a resolution yourself or did you bypass it? I'm considering an "aws sync" to my EC2, followed by a ec2-local-->s3 ept build. |
connormanning
added a commit
that referenced
this issue
Aug 24, 2023
- Drastically reduce metadata duplication for subset builds - Properly handle OriginId dimension, as well as its stats for subset builds (#277) - Properly compute detailed stats for subset builds rather than disabling them - Allow EPT to be used as input rather than treating it as an "info" result (#291) - Handle large amounts of duplicate points which overflow the tree (#250) - Update arbiter bundle - Update docs removing outdated info
Merged
Closed by #308. |
connormanning
added a commit
that referenced
this issue
Aug 29, 2023
* Various fixes, optimizations, and updates. - Drastically reduce metadata duplication for subset builds - Properly handle OriginId dimension, as well as its stats for subset builds (#277) - Properly compute detailed stats for subset builds rather than disabling them - Allow EPT to be used as input rather than treating it as an "info" result (#291) - Handle large amounts of duplicate points which overflow the tree (#250) - Update arbiter bundle - Update docs removing outdated info
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Can EPT point clouds be used as input? The documentation page mentions that all PDAL-readable formats should be supported but looking at the code seems that files with json extension have a different parsing flow.
I've tried using a previously generated EPT scans as input for a new one without success (see below). Is there any way to do it using the current version of entwine?
Thank you!
The text was updated successfully, but these errors were encountered: