xpchuan-95

I think it doesn't contain, @nisseknudsen ,does annotations contain track id?

'i' means 'intensity' and 'd' means 'device' (0 means from Pandar64, 1 means from PandarGT) For limiting Lidar points you can see https://github.com/scaleapi/pandaset-devkit/blob/master/tutorials/projection/projection.ipynb

We can temporarily provide raw data of Pandar64 and a instruction of the raw data [ PandaSet Raw Data Instructions.pdf](https://github.com/scaleapi/pandaset-devkit/files/5078794/PandaSet.Raw.Data.Instructions.pdf). The raw data can be download at https://drive.google.com/drive/folders/1ou_HqaQq0rGR0UrGZkFYWrE3mCJDosX8?usp=sharing

> I was just going to describe the exact same problem. > > I've downloaded raw data given the link here: #67 > I've read the raw point cloud in...

#67 Is this issue the same with yours?

Maybe you can refer to this #26

Some sequences are aborted for some problem, and 16,000+ LiDAR sweeps means 8000+ Pandar64 sweeps and 8000+ PandarGT sweeps.

IMU raw data has already be converted to pose of every sensor, you can find keyword "pose" of every sensor.

I am sorry that it's hard to get raw IMU data, but the pose of camera is directly calculated by IMU/GPS data, can you try to use pose of camera...