Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Read really big e57 unique scan #7
In libe57, in order to read points, you create X vector with the size of the number of points. (1 vector for X values, 1 for Y, 1 for Z, 1 for intens, 3 for color for example). In my case, I have ~2billions points in a unique scan, that means I have to create 7 vector of size 2billions, and obviously my computer crash with a bad_alloc...
And I had another question actually about libe57Format : What is the difference between your library, and classic libe57 (except for the boost lib)?
Thanks a lot! And sorry for that question...
No problem Raphaël, but I'm afraid I'm not going to be much help...
I actually am in a strange position where I don't have the actual E57 standard and I don't really have a deep understanding of this format. I'm more of a digital janitor for this code.
My goal was to take the old E57RefImpl and make it compile on macOS. Along the way I've removed Boost, reorganized the code, modernized some of the code, fixed a few bugs, made file reading faster, and added a checksum policy to determine how often to compute checksums (see
Oh! I see!
It is funny to see that this lib is so old, nobody know how it works anymore! :(
Thanks a lot for your answer ! :)
If you ever think about it one day, I believe the function to use is "Seek" but they didn't implemented it yet ^^'
It's not really a function of how old the code is, it's just not written in a way that other developers can understand it without a lot of study/time.
"If you ever think about it one day..." :-)
If I ever needed to make larger changes, I would probably rewrite this library.