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
Is your feature request related to a problem? Please describe.
Lidar data is quite similar to back-projected depth maps, so it would be nice to support distance-based color maps that can be changed from inside the viewer.
Raw lidar data often comes in terms of angles, distances, and per-point timestamps; processed data (projected and potentially motion compensated) typically comes as 3D point clouds in the sensor frame + sensor pose. I believe the latter would be more important to support directly.
Similar ideas apply to, for example, radar data; so maybe it would make sense to name the archetype in a more general way than just LidarScan.
Things I'm unsure of
I suspect raw lidar data might come in lots of different formats and conventions (i.e., how to interpret the angles to retrieve the 3D point); hence, just supporting 3D points in the sensor frame might be sufficient
Should the sensor pose be logged as a transform or should there be an option to log it as part of the sensor scan? Maybe best to support both for simplicity; however, in that case, it's important that both cases behave the same way.
It's probably worth checking a few lidars and what data they provide (I know about return number and intensity, but maybe there's more)
Describe the solution you'd like
Add a LidarScan archetype (or something more general like RangeScan maybe) that takes 3D points and supports different color maps based on the Euclidean distance to the scan origin.
Specifically for lidar, special per-point values that might be nice to support are the return number (integer) and intensity (float).
It would be nice if the color map input could be changed between distance / return number / intensity / x-value / ...
Describe alternatives you've considered
It's already possible to log lidar scans as points, but the color map has to be calculated manually and can't be changed from inside the viewer.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Lidar data is quite similar to back-projected depth maps, so it would be nice to support distance-based color maps that can be changed from inside the viewer.
Raw lidar data often comes in terms of angles, distances, and per-point timestamps; processed data (projected and potentially motion compensated) typically comes as 3D point clouds in the sensor frame + sensor pose. I believe the latter would be more important to support directly.
Similar ideas apply to, for example, radar data; so maybe it would make sense to name the archetype in a more general way than just
LidarScan
.Things I'm unsure of
Describe the solution you'd like
Add a
LidarScan
archetype (or something more general likeRangeScan
maybe) that takes 3D points and supports different color maps based on the Euclidean distance to the scan origin.Specifically for lidar, special per-point values that might be nice to support are the
return number
(integer) andintensity
(float).It would be nice if the color map input could be changed between
distance
/return number
/intensity
/x-value
/ ...Describe alternatives you've considered
It's already possible to log lidar scans as points, but the color map has to be calculated manually and can't be changed from inside the viewer.
The text was updated successfully, but these errors were encountered: