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
(I asked on the depthai forums as well, but was also curious about your take!)
I am trying to use Oak-D to get spatial data of the pose landmarks. For example, XYZ data of all the points that mark the joints.
I think the way Oak-D works for spatial detection on objects is that it draws a box around an object, and then averages out all of the xyz data of the points in the box from a depth map (created by using disparity matching), is this correct?
If so, what happens when a box is drawn around a person, and then some of the points in the box are objects that are further behind the person (such as the wall)?
In the case of getting spatial data for the body landmarks, do you think it's wiser to draw boxes around the landmarks and then average out the depth data? Or just get the depth data precisely at the landmark points?
Thanks in advance,
Jae
The text was updated successfully, but these errors were encountered:
(I asked on the depthai forums as well, but was also curious about your take!)
I am trying to use Oak-D to get spatial data of the pose landmarks. For example, XYZ data of all the points that mark the joints.
I think the way Oak-D works for spatial detection on objects is that it draws a box around an object, and then averages out all of the xyz data of the points in the box from a depth map (created by using disparity matching), is this correct?
If so, what happens when a box is drawn around a person, and then some of the points in the box are objects that are further behind the person (such as the wall)?
In the case of getting spatial data for the body landmarks, do you think it's wiser to draw boxes around the landmarks and then average out the depth data? Or just get the depth data precisely at the landmark points?
Thanks in advance,
Jae
The text was updated successfully, but these errors were encountered: