Closed floriandeboissieu closed 6 years ago
Crap !
You know what? From both of us you're now the more knowledgeable about LASlib integration in R. So I'm not asking you to find the problem because you do whatever you want. But you are likely to find the problem before me :wink:
I will look at that next week but not sooner.
But I'm not sure to understand a point. When loading the data into R it doesn't work but when reading, filtering writting into a las file in a streaming way it works?
I updated lasreadermerged
from the lastest commit in LAStools https://github.com/LAStools/LAStools/commit/7fb18d65bcebb2caf0332e7f44b0d9e525e72fa7 Please tell me if it solves the issue. Thanks
The LAStools update seems to work well, nice merge! However, you forgot to include the rest of my last commit:
On Sun, Dec 3, 2017 at 1:15 PM, Jean-Romain Roussel < notifications@github.com> wrote:
I updated lasreadermerged from the lastest commit in LAStools LAStools/LAStools@7fb18d6 https://github.com/LAStools/LAStools/commit/7fb18d65bcebb2caf0332e7f44b0d9e525e72fa7 please tell me if it solve the issue. Thanks
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Jean-Romain/rlas/issues/7#issuecomment-348760507, or mute the thread https://github.com/notifications/unsubscribe-auth/AP54IR8vGytVsDd2o4MOz_-SMTdBhQD8ks5s8pDegaJpZM4QnsWl .
I did not forget anything. I'm just a bit lost with all these commits. Are you sure I can safely merge #8 in devel? It sounds ok but maybe I should close your PR and you can make a new tidy one with only the useful stuff?
Sorry for the delay,
Yes I am sure you can merge it, but I can make a new PR if you feel more confortable with it, so that I can explain the issue with interger/double and scale/offset. It makes sense as this issue has nothing to do with the lasreadermerge one.
To test it, try
rlas::readlasdata("inst/extdata/extra_byte.laz", eb=0)
Amplitude Pulse width 3146904 12292
Amplitude Pulse width 8.27 4.8
Finally with las2txt command line you should find the same as with the PR version:
LAStools/bin/las2txt -i ~/git/rlasfdb/inst/extdata/extra_byte.laz -parse
txyz01 -stdout
Cheers Florian On 04/12/2017 16:15, Jean-Romain Roussel wrote:
I did not forget anything. I'm just a bit lost with all these commits. Are you sure I can safely merge #8 https://github.com/Jean-Romain/rlas/pull/8 in devel? It sounds ok but maybe I should close your PR and you can make a new tidy one with only the useful stuff?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Jean-Romain/rlas/issues/7#issuecomment-348991836, or mute the thread https://github.com/notifications/unsubscribe-auth/AP54IZpDWn8DF8qQ-D37SFNhV-JjrOOCks5s9AyggaJpZM4QnsWl.
Ok great I'm merging. Again thank you for your contributions
The extra bytes are not read when multiple files are merged. This is caused by LASreaderMerged::open under comment special check for attributes in extra bytes. I couldn't find any reason for this resetting of attributes, maybe because the unity/uniformity of the extra bytes across files is not checked (at reading nor at writing).