-
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
entwine build: SIGSEGV #250
Comments
Scanning input Entwine Version: 2.1.0 Adding 0 - /code/lidar/20PPC6610017190.las |
I got this one, Does anyone know what is going on here? |
You'll probably need to post the file to inspect somewhere. |
- 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
Closed by #308. |
* 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
I have tried to create a dataset from 120 las files, but I always got this SIGSEGV excemption.
Any suggestions?
The text was updated successfully, but these errors were encountered: