On Tue, Dec 6, 2011 at 7:38 PM, Kevin Walchko <span dir="ltr">&lt;<a href="mailto:kevin.walchko@gmail.com">kevin.walchko@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><br></div><div><div><div class="im"><div>On Dec 6, 2011, at 10:16 PM, Patrick Mihelich wrote:</div></div><div class="im"><blockquote type="cite"><div class="gmail_quote"><div>The proposed depth image representation is <i>exactly</i> the one currently used by the ROS OpenNI driver. The intent of this REP is to codify existing practice. What code would need to be rewritten?<br>
</div></div></blockquote><div><br></div></div><div>ok, wouldn&#39;t you have to re-write anything you want to start using DepthImage with? Currently any packages that accept sensor_msgs/Image can read the Kinect images … that is cool. However, now everything would have to be re-written if you wanted it to view the kinect depth image. Maybe I am wrong, but wouldn&#39;t that mean rviz, image_view, other user software, etc would have to be modified to accept this new message? To me this sounds like a big change for little gain.</div>
</div></div></div></blockquote><div><br>There is no DepthImage message. The REP describes how to use sensor_msgs/Image to represent depths.<br><br>I&#39;ll update the abstract to make the purpose and recommendations more explicit from the beginning.<br>
<br>Cheers,<br>Patrick<br></div></div>