[ADD] missing PointField type entries #301
Merged
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.
Description
Adding missing entries in the PointField message definition.
The current PCL uses more types than currently available in the message definition.
However, some Python libraries expect to find the datatype values in the message definition.
Fixes #300
Is this user-facing behavior change?
Users may use int64, uint64 and bool in PointClouds and have an easier life decoding them
Did you use Generative AI?
No
Additional Information
https://github.com/PointCloudLibrary/pcl/blob/master/common/include/pcl/type_traits.h
this is where the PCL defines the values