Tool/software:
Hello
In 3D people tracking demo, is there a way to associate detected point clouds with target IDs from serial output data? Like to say each point belong to which target?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hello
In 3D people tracking demo, is there a way to associate detected point clouds with target IDs from serial output data? Like to say each point belong to which target?
Thank you. To make sure I understand correctly: If there are 50 points in the point cloud and 3 target IDs, the TLV type 1011 would be 50 bytes long, with each byte representing the target ID for each corresponding point (e.g., byte[0] shows point 0 belongs to which target, byte[1] shows point 1 belongs to which target, and so on)?
If a point does not belong to any target, what value would be used to indicate this? Would it be something like 0xFF?
I assume the points arragment is the same as TLV type 1020 3D Spherical Compressed Point Cloud?
Thank you. To make sure I understand correctly: If there are 50 points in the point cloud and 3 target IDs, the TLV type 1011 would be 50 bytes long, with each byte representing the target ID for each corresponding point (e.g., byte[0] shows point 0 belongs to which target, byte[1] shows point 1 belongs to which target, and so on)?
yes
If a point does not belong to any target, what value would be used to indicate this? Would it be something like 0xFF?
Yes I think it's some value between 250-255 to indicate different ways that points are not assigned.
Best,
Nate
Thanks Nathan. And is the order of points in TLV 1011 the same as the order in TLV 1020 3D Compressed Point Cloud? If so, we can correlate them.
Hi,
Thanks Nathan. And is the order of points in TLV 1011 the same as the order in TLV 1020 3D Compressed Point Cloud? If so, we can correlate them.
Yes the order should be the same.
Best,
Nate