-
Notifications
You must be signed in to change notification settings - Fork 128
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
OriginId dimension no added to the data #277
Comments
VSasyan
changed the title
OriginId dimension non added to the data
OriginId dimension no added to the data
Sep 1, 2022
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
Hello,
When I build data from LAZ files, I do not have the
OriginId
dimension added (or I do not find it).Reading the documentation, I understand that this dimension should be added by default (we can only disabled this).
For example: (entwine 2.2.0)
No "OriginId" in
red-rocks/ept.json
schema neither than in the LAZ files:Should I explicitly ask to have this information or is that a bug?
The text was updated successfully, but these errors were encountered: