LidarView performs real-time reception, recording, visualization and processing of 3D LiDAR data.
LidarView's open source codebase developed by Kitware is used by many different applications to display live LiDAR data from Velodyne, Ouster, Opsys, Lumotive, RoboSense, Hesai, LeiShen LS Lidar, and more.
This open-source declination only supports VeloDyne's open-source interpreters: VLP-16, VLP-32, HDL-32, HDL64, Alpha Prime. An Experimental branch with Hesai sensor support also exists.
Many of these LiDAR sensors sweep an array of lasers (often 8 to 128) 360° with a vertical field of view of tens of degrees at a 5-20Hz spinning frequency, capturing about a million points per second.
LidarView can display live sensors' streams or playback pre-recorded data stored in .pcap files.
LidarView displays the distance measurements from the LiDAR as point cloud data and custom color maps for multiple variables such as intensity-of-return, time, distance, azimuth, and laser id.
The processed data can be exported in multiple file formats (CSV, PLY, LAS, ...), and screenshots of the currently displayed point cloud can be easily exported with the help of a button.
As a Paraview based application, LidarView can effortlessly offer Paraview's features and plugins.
Lidar data processed by Kitware's SLAM within LidarView
- Input from live sensor stream or recorded
.pcapfile - Visualization of timestamped LiDAR returns in 3D
- Spreadsheet inspector for LiDAR attributes (timestamp, azimuth, laser id, etc)
- Record to
.pcapfrom sensor - Export to CSV, PLY, PCD, LAS or VTK formats
- Grid and Ruler tools
- Show or hide lasers subsets
- Show multiple frames of data simultaneously and aggregate them
- Apply 3D transforms to pointclouds
- Run SLAM to estimate the trajectory of the LiDAR in the scene and build a 3D map of the environment
Many other features can be added using Plugins, some can be found on this page.
Feel free to reach out at kitware@kitware.com for support or new features development.
Lidarview is maintained on the following platforms:
- Ubuntu 18, Ubuntu 20
- Windows x64
- MacOS 12
See detailed general installation instructions on the LVCore/Documentation/INSTALLATION.md page.
See the Detailed installation instructions for the current and older releases on the RELEASES.md page.
See associated download links in the Release page of this repository.
Most of the LidarView common codebase lies within:
- LVCore repository.
- LidarView-superbuild repository.
Detailed Instructions to build and package LidarView are available under LVCore/Documentation/LidarView_Developer_Guide.md.
Specific network configuration is required for sensor livestream. The ethernet adapter connected to the sensor has to be switched from dynamic IP address assignment to static IP address selection and correct IP adress and gateway must be specified.
For example:
- Velodyne HDL-32E
- IP address: 192.168.1.70 (70 as example, any number except 201 works)
- Gateway: 255.255.255.0
- Velodyne HDL-64E
- IP address: 192.168.3.70 (70 as example, any number except 43 works)
- Gateway: 192.168.3.255
In order for sensor streaming to work properly, it is important to disable firewall restrictions for the chosen ethernet port and allow inbound traffic. Alternatively, completely disable the firewall for the ethernet device connected to the sensor (including both public and private networks).
When opening pre-recorded data or live sensor streaming data, one is prompted to choose a calibration file. This calibration can either be directly embedded in LidarView, or may be loaded from a custom location.
More instructions can be found on the LidarSlam repository.
Have a look also at the How to SLAM with LidarView webinar.
LiDAR data samples for LidarView can be obtained from:
- MIDAS in the Velodyne LiDAR collection
- Kitware's demos shared drive
Github is a mirror of the official repository. We do not actively monitor issues or pull request on Github. Please use the official repository to report issues or contributes fixes.
The source code for LidarView is made available under the Apache 2.0 license.
See LICENSE.