Dataloader
Convert autonomous-driving datasets into one timestamped layout, then use the same Python API and ROS player across datasets.
Conversion, validation, and reading are ROS-independent. ROS is required only for playback.
Highlights
| Capability | Included |
|---|---|
| Unified data | manifest.yaml, timeline.csv, sensors/, and poses/ |
| Dataset adapters | MulRan, HeLiPR, SemanticKITTI |
| Python tools | Converter, batch conversion, reader, validator, and summary CLI |
| LiDAR readers | Ouster, Velodyne, Livox Avia, and Aeva |
| ROS playback | ROS 1 catkin and ROS 2 colcon, with time, topics, and pose transforms |
Quick start
Install
Python
Install the public package from PyPI:
python3 -m pip install autodataloader
The distribution is named autodataloader; import it as dataloader. The PyPI package installs only the ROS-independent conversion, reading, validation, and inspection tools.
ROS 1
source /opt/ros/noetic/setup.bash
mkdir -p ~/catkin_ws/src
cd ~/catkin_ws/src
git clone https://github.com/kimdaebeom/dataloader.git
cd ..
rosdep install --from-paths src --ignore-src -r -y
catkin_make
source devel/setup.bash
ROS 2
source /opt/ros/jazzy/setup.bash
mkdir -p ~/ros2_ws/src
cd ~/ros2_ws/src
git clone https://github.com/kimdaebeom/dataloader.git
cd ..
rosdep install --from-paths src --ignore-src -r -y
colcon build --symlink-install --packages-select dataloader
source install/setup.bash
Convert
Python CLI
dataloader-convert \
--dataset mulran \
--source /data/raw/mulran/KAIST01 \
--output /data/converted
Python API
from dataloader import Dataset, convert_dataset
result = convert_dataset(
dataset="mulran",
source="/data/raw/mulran/KAIST01",
output_root="/data/converted",
)
dataset = Dataset(result["sequence_dir"])
points = dataset.lidar(frame=0).numpy() # float32 [N, 4]
ROS 1
rosrun dataloader dataloader_convert.py \
--dataset mulran \
--source /data/raw/mulran/KAIST01 \
--output /data/converted
ROS 2
ros2 run dataloader dataloader_convert \
--dataset mulran \
--source /data/raw/mulran/KAIST01 \
--output /data/converted
Playback
Choose a config from config/ and set its dataset root and sequence.
ROS 1
roslaunch dataloader player.launch \
config:=$(rospack find dataloader)/config/mulran.yaml
ROS 2
ros2 launch dataloader player.launch.py \
config:=$(ros2 pkg prefix dataloader)/share/dataloader/config/mulran.yaml
Documentation
- Installation — Python, ROS 1, and ROS 2
- Usage — CLI and Python API
- Dataset layouts — expected raw input structures
- Converted format — manifest, timeline, poses, and storage modes
- ROS playback — configuration, topics, and transforms
- Development · Release checklist
Supported datasets
| Dataset | Converter | LiDAR formats |
|---|---|---|
| MulRan | Yes | Ouster |
| HeLiPR | Yes | Ouster, Velodyne, Livox Avia, Aeva |
| SemanticKITTI | Yes | Velodyne |
SemanticKITTI currently expects the preprocessed pcd/ plus odom_tum.txt layout described in Dataset layouts. Native KITTI/KITTI Odometry input is not yet supported.
Released under the MIT License.
Metadata
Release files for autodataloader 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| autodataloader-0.1.0.tar.gz | 46.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autodataloader-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.2 kB
Release files / autodataloader-0.1.0.tar.gz
| Download URL | autodataloader-0.1.0.tar.gz |
|---|---|
| Size | 46.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70b1bad32f913eec40ffbbca091de4755327bf12764cf83fcdbc0cbe0cb958a6
|
|
BLAKE2b-256 checksum How to use checksums |
d93f365354ab3db31b83b5fdcb04f38fd0e03558afb78ff276f4d3bd1bdaaa69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 8, 2026.
Transparency logRelease files / autodataloader-0.1.0-py3-none-any.whl
| Download URL | autodataloader-0.1.0-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d16ec85ea58394f58245c604b5bf5a329d37e52e21384d984e537eef173aa8e
|
|
BLAKE2b-256 checksum How to use checksums |
02a694a05f199e03968cf8bf0a09402994f8b4c5b1f4576e4ebb3b403cffa132
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 8, 2026.
Transparency logSecurity for autodataloader 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for autodataloader-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.