ROS index logo ROS Index
  1. Home
  2. Packages
  3. velodyne_pointcloud
 
Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
humble

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
kilted

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
rolling

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from sync_gps_lidar_imu_cam repo

gps_driver image_exposure_msgs pointgrey_camera_description pointgrey_camera_driver statistics_msgs wfov_camera_msgs velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pcl velodyne_pointcloud xsens_imu_driver

ROS Distro
github

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 1.6.0
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description lidar-imu-cam-GPS时间戳硬件同步方案
Checkout URI https://github.com/nkliuhui/sync_gps_lidar_imu_cam.git
VCS Type git
VCS Version master
Last Updated 2021-07-21
Dev Status UNKNOWN
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Sebastian Pütz
README
No README found. See repository README.
CHANGELOG

Change history

1.6.0 (2020-07-09)

  • Unify tf frame parameters between transform and cloud nodes (#344)

    • Unify tf frame parameters between transform and cloud nodes
    • Use more common ROS terminology instead of 'htm'
    • Just use tf listener when necessary
    • Migrate package to tf2
    • Explicitly store sensor frame in a dedicated variable to make code easier to read

    * Avoid unnecessary transforms when sensor_frame == target_frame Co-authored-by: anre <<andreas.reich@unibw.de>>

  • Velodyne pcl (#335)

    • fix time assignment in organized cloud container
    • add velodyne_pcl package with point_types.h
    • add README.md with infos for conversion
    • rename containers to cover the added time property

    * Update package.xml to Format2 and package version to 1.5.2 Co-authored-by: Joshua Whitley <<josh.whitley@autoware.org>>

  • Passing fixed_frame and target_frame to Convert object. (#330)

  • Updating maintainer email address.

  • Increase the max_range of the 32C launch file (#323)

  • Getting model param for timings from private node handle. (#318)

  • updated model to have a default of "" so that tests run successfully

  • Move timing offsets functionality into class private. Also fix linter errors

  • Added model param to each of the cloud nodelet starters

  • Initial commit to timestamp each point using the timing spec in the manuals

  • use correct node handles and node names for diagnostic_updater::Updater

  • Added config option to timestamp a full scan based on first velo packet instead of last packet

  • Remove a dead store from rawdata.cc.

  • fix for #267, transform each packet

  • Merge pull request #250 from zhixy/master bug fix for row step

  • Merge pull request #253 from ros-drivers/fix/fixed_frame_target_frame Add configurable fixed_frame/target_frame for velodyne_pointcloud

  • Merge pull request #214 from spuetz/feature/opc_nopcl Container cleanup and organized pointclouds

  • Merge pull request #236 from mpitropov/fix_transform_node_frame_bug set correct output frame

  • Merge pull request #234 from kmhallen/c++11 Set minimum C++ standard to C++11

  • Merge pull request #223 from mpitropov/feat_Add_fixed_frame Add fixed frame and use ros message time within transform node

  • Made static tf publisher test adhere to REP 105

  • change more odom to map

  • Merge pull request #224 from mpitropov/feat_add_diagnostics Added diagnostic publishing

  • Merge pull request #222 from mpitropov/feat_Use_GPS_time Add flag to enable using GPS time from within the Velodyne packet instead of ROS time for scan.

File truncated at 100 lines see the full file

Launch files

  • launch/32e_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/32db.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: true]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: true]
  • launch/64e_S3.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/64e_s3-xiesc.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
  • launch/VLP-32C_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VeloView-VLP-32C.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 200.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/VLP16_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLP16db.yaml]
      • device_ip [default: 192.168.0.212]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2370]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: true]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: true]
  • launch/VLP16_points_gao.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLP16db.yaml]
      • device_ip [default: 192.168.1.201]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: true]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: true]
  • launch/VLP16_points_ori.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLP16db.yaml]
      • device_ip [default: 192.168.0.211]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2369]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: true]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: true]
  • launch/laserscan_nodelet.launch
    • -*- mode: XML -*-
      • manager [default: velodyne_nodelet_manager]
      • ring [default: -1]
      • resolution [default: 0.007]
  • launch/transform_nodelet.launch
    • -*- mode: XML -*-
      • model [default: ]
      • calibration [default: ]
      • fixed_frame [default: ]
      • target_frame [default: ]
      • manager [default: velodyne_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.9]
      • organize_cloud [default: false]
  • tests/static_vehicle_tf.launch
    • -*- mode: XML -*-

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
galactic

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
iron

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 2.5.1
License BSD
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version ros2
Last Updated 2024-10-31
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Andreas Klintberg
velodyne_pointcloud/README.md

Velodyne ROS 2 raw to pointcloud converters

This is a ROS 2 package that takes raw velodyne data as output by the velodyne_driver node, and converts it into a sensor_msgs/PointCloud2 message.

There are two different nodes here:

velodyne_convert_node - This node takes in the raw data and converts it to a pointcloud immediately. velodyne_transform_node - This node takes the raw data and converts it only when a corresponding tf message with a compatible timestamp has arrived.

The topics and parameters for both nodes are identical, so they’ll be described together below.

Published Topics

  • velodyne_points (sensor_msgs/PointCloud2) - The pointcloud that results from the raw velodyne data.

Subscribed Topics

  • velodyne_packets (velodyne_msgs/VelodyneScan) - The raw velodyne packets coming from the velodyne_driver.

Parameters

  • calibration (string) - The path to the calibration file for the particular device. There are a set of default calibration files to start with in the “params” subdirectory in this package. Defaults to the empty string.
  • min_range (double) - The minimum range in meters that a point must be to be added to the resulting point cloud. Points closer than this are discarded. Must be between 0.1 and 10.0. Defaults to 0.9.
  • max_range (double) - The maximum range in meters that a point must be to be added to the resulting point cloud. Points further away than this are discarded. Must be between 0.1 and 200.0. Defaults to 130.0.
  • view_direction (double) - The point around the circumference of the device, in radians, to “center” the view. Combined with view_width, this allows the node to generate a pointcloud only for the given width, centered at this point. This can vastly reduce the CPU requirements of the node. Must be between -Pi and Pi, where 0 is straight ahead from the device. Defaults to 0.0.
  • view_width (double) - The width, in radians, of the view to generate for the resulting pointcloud. Combined with view_direction, this allows the node to generate a pointcloud only for the given width, centered at the view_direction point. This can vastly reduce the CPU requirements of the node. Must be between 0 and 2Pi. Defaults to 2Pi.
  • organize_cloud (bool) - Whether to organize the cloud by ring (True), or to use the order as it comes directly from the driver (False). Defaults to True.
  • target_frame (string) - The coordinate frame to apply to the generated point cloud header before publishing. If the empty string (the default), the frame is passed along from the driver packet. If this frame is different than the fixed_frame, a transformation to this coordinate frame is performed while creating the pointcloud.
  • fixed_frame (string) - The fixed coordinate frame to transform the data from.
CHANGELOG

Change history

2.5.1 (2024-10-31)

  • Fix compiling on RHEL-8. (#549)
  • Contributors: Chris Lalancette

2.5.0 (2024-10-30)

  • Clalancette/cmake cleanups (#546)
  • Fix exports (#535)
  • Add in the Eigen dependency to velodyne_pointcloud (#545)
  • Add package to compile in Jazzy (#539)
  • Feature script add two pt ros2 (#498)
  • delete unused valiable (#529)
  • Add vert offset corrections to VLP16 calib file (#518)
  • Fix double-include.
  • feat: support vls128 for ros2 (#493)
  • Update rolling ci (#512) (#513)
  • Contributors: Chris Lalancette, Daisuke Nishimatsu, Joshua Whitley, Mateusz Szczygielski, Pierrick Koch, Taiga Takano, Thomas Emter, g-kurz

2.4.0 (2023-05-27)

2.3.0 (2022-07-08)

  • Passing fixed_frame and target_frame to Convert object. (#330) (#451) Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Updating maintainer email address. (#450)

    • Updating maintainer email address.

    * chore: update maintainer email address Co-authored-by: Joshua Whitley <<jwhitley@autonomoustuff.com>>

  • Add per point time field

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pointcloud

ROS Distro
melodic

API Docs
Browse Code
Wiki

Package Summary

Tags No category tags.
Version 1.5.2
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version melodic-devel
Last Updated 2021-05-13
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Sebastian Pütz
README
No README found. See repository README.
CHANGELOG

Change history

1.5.2 (2019-01-28)

  • Merge pull request #205 from xiesc/master support for 64E-S3
  • add an example yaml file for S3
  • Contributors: Joshua Whitley, Shichao XIE, xiesc

1.5.1 (2018-12-10)

  • Merge pull request #194 from ros-drivers/avoid_unnecessary_computation Avoid unnecessary computation - causes approximately 20% performance increase on VLP-32C - should be similar for other sensors
  • std::vector<>::reserve is your friend
  • add static to avoid frequence memory allocation
  • avoid unecesary calculations in unpack()
  • Contributors: Davide Faconti, Joshua Whitley

1.5.0 (2018-10-19)

  • Merge pull request #164 from ros-drivers/maint/vlp_32c_support Adding VLP-32C support. This was tested by AutonomouStuff and several external users. Though it does not include new information that I've learned (it appears that the distance resolution is different <50m vs >=50m), it is a good start.
  • Merge pull request #189 from kveretennicov/patch-1
  • Fix malformed plugin description XML ROS pluginlib only recognizes multiple <library> elements if they are under <class_libraries> XML root. It silently ignores malformed XMLs with multiple <library> "root"s and just reads the first one, due to relaxed way tinyxml2 does parsing. Though if you do [rosrun nodelet declared_nodelets]{.title-ref}, the issue is reported properly. See also similar issue in https://github.com/ros-perception/perception_pcl/issues/131
  • Adding distance_resolution to test yaml files.
  • Adding VLP-32C support. Based on work done by \@rockcdr. Adds distance_resolution calibration value to support 0.004m distance resolution for VLP-32C.
  • Contributors: Joshua Whitley, Konstantin Veretennicov

1.4.0 (2018-09-19)

  • Merge pull request #178 from sts-thm/bugfix_issue_#174 Bugfix issue #174
  • Merge pull request #177 from C-NR/feature/WrapPointcloudData Feature/wrap pointcloud data
  • Changes fixing deadlock for specific cut_angle values.
  • moved definition of VPoint and VPointCloud back to namespace rawdata in rawdata.h
  • put a wrapper around pointcloud data including a generic setter method to enable the use of arbitrary data structures (pcl pointcloud, depth image, octomaps and so on) to be filled by just using RawData::unpack method with the wrapper object as parameter
  • Merge pull request #170 from ros-drivers/maint/move_header_files Moving header files to traditional location inside include folders.
  • Merge pull request #160 from ros-drivers/maint/updating_package_xml_to_v2
  • Updated all package.xmls to ver 2. Cleaned up catkin_lint errors. All package.xml files are now compatible with version 2 of the package.xml specification in REP 140. Removed some unnecessary execute permissions on a few files. Fixed a missing test_depend.
  • Merge pull request #136 from stsundermann/patch-1 Use std::abs instead of abs
  • Adding missing 32C configuration file.
  • Merge pull request #139 from ASDeveloper00/vlp32 Adding support for VLP-32C.
  • Merge pull request #138 from volkandre/cut_at_specified_angle_feature Cut at specified angle feature
  • Updated default cut_angle parameters in launch files after switching from deg to rad.
  • Use std::abs instead of abs abs is the c version which returns an integer. This is probably not intended here, so use the templated std::abs function.
  • Contributors: Andre Volk, Autonomoustuff Developer, CNR, Joshua Whitley, Kyle Rector, Stephan Sundermann, Tobias Athmer, kennouni

1.3.0 (2017-11-10)

  • Merge pull request #110 from kmhallen/master Added velodyne_laserscan package

File truncated at 100 lines see the full file

Launch files

  • launch/32e_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/32db.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/64e_S3.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/64e_s3-xiesc.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
  • launch/VLP-32C_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VeloView-VLP-32C.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 200.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/VLP16_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLP16db.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/cloud_nodelet.launch
    • -*- mode: XML -*-
      • model [default: ]
      • calibration [default: ]
      • manager [default: velodyne_nodelet_manager]
      • fixed_frame [default: velodyne]
      • target_frame [default: velodyne]
      • max_range [default: 130.0]
      • min_range [default: 0.9]
      • organize_cloud [default: false]
  • launch/laserscan_nodelet.launch
    • -*- mode: XML -*-
      • manager [default: velodyne_nodelet_manager]
      • ring [default: -1]
      • resolution [default: 0.007]
  • launch/transform_nodelet.launch
    • -*- mode: XML -*-
      • model [default: ]
      • calibration [default: ]
      • frame_id [default: map]
      • manager [default: velodyne_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.9]
      • organize_cloud [default: false]
  • tests/static_vehicle_tf.launch
    • -*- mode: XML -*-

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange

Package symbol

velodyne_pointcloud package from velodyne repo

velodyne velodyne_driver velodyne_laserscan velodyne_msgs velodyne_pcl velodyne_pointcloud

ROS Distro
noetic

API Docs
Browse Code
Wiki

Package Summary

Tags No category tags.
Version 1.7.0
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description ROS support for Velodyne 3D LIDARs
Checkout URI https://github.com/ros-drivers/velodyne.git
VCS Type git
VCS Version master
Last Updated 2023-06-01
Dev Status DEVELOPED
Released RELEASED
Tags No category tags.
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Point cloud conversions for Velodyne 3D LIDARs.

Additional Links

Maintainers

  • Josh Whitley

Authors

  • Jack O'Quin
  • Piyush Khandelwal
  • Jesse Vera
  • Sebastian Pütz
README
No README found. See repository README.
CHANGELOG

Change history

1.7.0 (2022-07-08)

  • build timings in offline setup (#428) Currently when using the offline setup, it does not build the per-point timing offsets which means when unpacking the packets in the offline mode, you cannot timestamp each point with its packet time. This commit does the following:

    • call buildTimings from setupOffline function
    • add model to setupOffline interface
    • set config model param which is needed by buildTimings

  • vls128: add line only once all four banks are processed (#413)

  • PCAP timestamps & PCAP+GPS timestamps (#384)

    • Add pcap_time param and implement gps_time with it
    • If gps_time == true, ignore pcap_time

  • Fixed row_step=0 when init_width=0 (dense cloud) (#404) The PointCloud2 msg will be then valid: http://docs.ros.org/en/melodic/api/sensor_msgs/html/msg/PointCloud2.html Referred issues:

  • Fix accidental integer division (#391) Intensity values for VLP-16 were being calculated incorrectly.

  • Add VLS128 launch and calibration file (#382)

  • Fixing incorrect type in velodyne_pointcloud.

  • Fixing typo.

  • Add support for the velodyne Alpha Prime (#370)

    • Add support for the velodyne Alpha Prime
    • Change packet rate for the VLS128 according to the times specified in the manual
    • Organize setup functions to avoid code duplication. Add a constant for the model ID of the VLS128.

    * Use the defined constants to calculate the time offset of the points for the VLS128 Co-authored-by: jugo <<juan.gonzalez@unibw.de>>

  • Contributors: Daisuke Nishimatsu, HMellor, Institute for Autonomous Systems Technology, Joshua Whitley, Martin Valgur, Nick Charron, Sebastian Scherer, matlabbe

1.6.1 (2020-11-09)

  • Add invalid points in organized cloud (#360)

    • Set NaN in ordered point cloud in case of no return
    • Adapt to current master

    * consider min/max angle and timing_offsets also in organized mode Co-authored-by: Nuernberg Thomas (CR/AEV4) <<thomas.nuernberg@de.bosch.com>>

  • build and export library data_containers so it can be used in other packages (#359)

  • Contributors: Sebastian Scherer

1.6.0 (2020-07-09)

  • Unify tf frame parameters between transform and cloud nodes (#344)

    • Unify tf frame parameters between transform and cloud nodes
    • Use more common ROS terminology instead of 'htm'
    • Just use tf listener when necessary
    • Migrate package to tf2
    • Explicitly store sensor frame in a dedicated variable to make code easier to read

    * Avoid unnecessary transforms when sensor_frame == target_frame Co-authored-by: anre <<andreas.reich@unibw.de>>

  • Velodyne pcl (#335)

    • fix time assignment in organized cloud container
    • add velodyne_pcl package with point_types.h
    • add README.md with infos for conversion

File truncated at 100 lines see the full file

Launch files

  • launch/32e_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/32db.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • pcap_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/64e_S3.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/64e_s3-xiesc.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • pcap_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
  • launch/VLP-32C_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VeloView-VLP-32C.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 200.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • pcap_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/VLP16_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLP16db.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • pcap_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/VLS128_points.launch
    • -*- mode: XML -*-
      • calibration [default: $(find velodyne_pointcloud)/params/VLS128.yaml]
      • device_ip [default: ]
      • frame_id [default: velodyne]
      • manager [default: $(arg frame_id)_nodelet_manager]
      • max_range [default: 200.0]
      • min_range [default: 0.4]
      • pcap [default: ]
      • port [default: 2368]
      • read_fast [default: false]
      • read_once [default: false]
      • repeat_delay [default: 0.0]
      • rpm [default: 600.0]
      • gps_time [default: false]
      • cut_angle [default: -0.01]
      • timestamp_first_packet [default: false]
      • laserscan_ring [default: -1]
      • laserscan_resolution [default: 0.007]
      • organize_cloud [default: false]
  • launch/laserscan_nodelet.launch
    • -*- mode: XML -*-
      • manager [default: velodyne_nodelet_manager]
      • ring [default: -1]
      • resolution [default: 0.007]
  • launch/transform_nodelet.launch
    • -*- mode: XML -*-
      • model [default: ]
      • calibration [default: ]
      • fixed_frame [default: ]
      • target_frame [default: ]
      • manager [default: velodyne_nodelet_manager]
      • max_range [default: 130.0]
      • min_range [default: 0.9]
      • organize_cloud [default: false]
  • tests/static_vehicle_tf.launch
    • -*- mode: XML -*-

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged velodyne_pointcloud at Robotics Stack Exchange