According to the Openni camera documentation, the z value in the depth
image corresponds to the distance in meters. However, when inspecting
the data, you can see that the z values followin discrete jumps.
Back when I was working with the libfreenect driver (and its ros
wrapper), the output of the Kinect was a 11-bit number, which was
linear with the inverse of the distance in meters. This produced
discretization levels with steps that increased as the distance to the
object increased. Is the same true for the openni driver? Is it still
using 11 bits internally, and are they still related to the meter
distance by the same function? I tried looking through the wrapper
source, but it's not there.
The reason I'm asking this is because I'm writing an application where
it might be advantageous if I could work with the data in its raw
(unlinearized) discrete values, rather than the meter distance.