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
When importing ROS point clouds with 'intensity' fields it would be nice to have some way to pass this to open3d. As intensity is usually not accompanied by rgb it could be passed into these fields.
I would suggest something like:
r = b = g = intensity/255 for each point
Will likely create fork for own purposes but thought I discuss how best to implement. Should this have explicit flag in definition e.g.
def rospc_to_o3dpc(rospc, remove_nans=False, has_intensity=False):? If reading back to ros should it use average of r,g,b?
The text was updated successfully, but these errors were encountered:
Thank you for suggesting a feature to support more various ROS point clouds.
Maybe we can add a external flag "alpha" to "o3dpc_to_rospc", where alpha = 1 / intensity and "o3dpc_to_rospc" returns (r, g, b) * alpha. But I am not sure it is correct, so I will test it later.
When importing ROS point clouds with 'intensity' fields it would be nice to have some way to pass this to open3d. As intensity is usually not accompanied by rgb it could be passed into these fields.
I would suggest something like:
r = b = g = intensity/255 for each point
Will likely create fork for own purposes but thought I discuss how best to implement. Should this have explicit flag in definition e.g.
def rospc_to_o3dpc(rospc, remove_nans=False, has_intensity=False):? If reading back to ros should it use average of r,g,b?
The text was updated successfully, but these errors were encountered: