You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thank you first for sharing this excellent work!
If my input is pointcloud, such as the KITTI .BIN file, is this conversion using projection (sphere or ring), always conver to 64x870 size?
How/Where this 870 is calculated?
And can we change this size 870, I saw some other size such as 64x1030.
My concern is the original xyz of the poincloud from BIN is around ~120,000 points while the range image is only covering 55680 xyz points (55680=870*64). It seems more than 50% points are removed/overwrite in this "pc2range" conversion process. Can you comment on this?
Thank you very much!
The text was updated successfully, but these errors were encountered:
So, the way it is implemented now was tailored to Frank Moosman's data. These data are all 64x870, which seems to give a good tradeoff between speed and precision. The way I handle multiple points that fall into the same pixel is that only the furthest reading is taken per pixel, but all the points that fall into it get assigned the same label. It can create some minor artifacts, but seemed to work well in practice for me.
You can however, pick any resolution you want if you look into the ProjectionParams class by adding another function like this one with any resolution you want.
Be advised, that working with KITTI data directly might be a little imprecise as the HDL64 has two sets of beams that do not exactly match onto a single depth image.
Hi, thank you first for sharing this excellent work!
If my input is pointcloud, such as the KITTI .BIN file, is this conversion using projection (sphere or ring), always conver to 64x870 size?
How/Where this 870 is calculated?
And can we change this size 870, I saw some other size such as 64x1030.
My concern is the original xyz of the poincloud from BIN is around ~120,000 points while the range image is only covering 55680 xyz points (55680=870*64). It seems more than 50% points are removed/overwrite in this "pc2range" conversion process. Can you comment on this?
Thank you very much!
The text was updated successfully, but these errors were encountered: