Overview  ** Features ** User Instructions **  Developer Instructions

VeloView is an open source application built on top of ParaView that performs visualization of live or captured 3D LiDAR data from Velodyne’s HDL line of sensors (HDL-32E, HDL-64E, support for VLP-16 coming soon).  The following videos introduce the features of VeloView.

Kitware and Velodyne collaborated to release VeloView 2.0 in April 2014, coinciding with the SPAR International 3D Measurement & Imaging Conference.

VeloView can playback pre-recorded data stored in .pcap files. The HDL sensor sweeps an array of lasers (32 or 64) 360° and a vertical field of view of 40°/26° with 5-20Hz and captures about a million points per second (HDL-32E: ~700,000pt/sec; HDL-64E: ~1.3Million pt/sec). VeloView displays the distance measurements from the HDL as point cloud data and supports custom color maps of multiple variables such as intensity-of-return, time, distance, azimuth, and laser id. The data can be exported as XYZ data in CSV format or screenshots of the currently displayed point cloud can be exported with the touch of a button.


Overview  ** Features ** User Instructions **  Developer Instructions

  • Input from live sensor stream or recorded .pcap file
  • Visualization of LiDAR returns in 3D + time including 3d position and attribute data such as timestamp, azimuth, laser id, etc.
  • Spreadsheet inspector for LiDAR attributes
  • Record to .pcap from sensor
  • Export to CSV or VTK formats
  • Record and export GPS and IMU data (New in 2.0)
  • Ruler tool (New in 2.0)
  • Visualize path of GPS data (New in 2.0)
  • Show multiple frames of data simultaneously (New in 2.0)
  • Show or hide a subset of lasers (New in 2.0)

User Instructions

Overview  ** Features ** User Instructions **  Developer Instructions Binary installers for VeloView are available as community contributed applications:

Previous releases are also available

Sample data for VeloView can be obtained from Midas in the Velodyne LiDAR collection. For “sensor streaming” (live display of sensor data) it is important to change the network settings of the Ethernet adapter connected to the sensor from automatic IP address to manual IP address selection and choose:

  • HDL-32E
    • IP address: (70 as example, any number except 201 works)
    • Gateway:
  • HDL-64E
    • IP address: (70 as example, any number except 43 works)
    • Gateway:

In order for sensor streaming to work properly, it is important to disable firewall restrictions for the Ethernet port. Disable the firewall completely for the ethernet device connected to the sensor or explicitly allow data from that Ethernet port of (including both public and private networks). When opening pre-recorded data or live sensor streaming data one is prompted to choose a calibration file.

  • For HDL-32E data no calibration file is needed (the HDL-32E calibration values are already incorporated in VeloView) therefore select “NONE”.
  • For HDL-64E data the correct calibration file for that sensor needs to be chosen. The calibration file can be found on the individual product CD that was send with the HDL-64E sensor.

Developer Instructions

Overview  ** Features ** User Instructions **  Developer Instructions Detailed instructions for building and packaging are available in developers guide the source code checkout under the Documentation folder. The source code for VeloView is made available under the Apache 2.0 license. Source code is available as a .tgz file for version 2.0.0. To obtain the latest version clone the git repository as shown below: $ git clone git:// Sample data for VeloView can be obtained from MIDAS in the Velodyne LiDAR collection.