Added time offset to the sensor_msgs/Pointcloud2 message. #60
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now it can be directly used and converted to PCL type, manipulated etc.
|
Hi, @samkys Could you please explain more about the timestamp? The stamp in /livox/lidar msg is relative time from the start of the lidar. Now i need the ros timestamp, how to calculate it? Looking forward to your help :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now it can be directly used and converted to PCL type, manipulated etc. We needed the timeoffset readily exposed to ROS and also be able to use PCL and ROS conversion tools for compatibility purposes.
Timeoffset is the same as the custom point message type, nanoseconds past the timestamp of the message.