Skip to content

WASA dataset

This page contains an open multimodal vehicle dataset described in the “Towards Collecting Large-Scale Vehicular Sensor Data for Open Access” paper, published in the 12th International Workshop on Autonomous Systems and Software Architecture (WASA) 2026. The data is free to be used under the Creative Commons CC BY 4.0 license. When using the data, you must give an attribution to the following paper and provide a link to the dataset:

B. Kämä, O. Timonen, N. Stafford, J. Lotvonen, O. Kalliokoski, A. Kanerva, P. Rathnayake, S. Gamage, A. Vuorinen, S. Ariram, E. Gilman & E. Peltonen. Towards Collecting Large-Scale Vehicular Sensor Data for Open Access. IEEE 23rd International Conference on Software Architecture Companion (ICSA-C). Amsterdam, Netherlands. 2026

Link to the preprint and final publication

For further enqueries and questions about the data or paper, please contact benjamin.kama or ella.peltonen at oulu.fi

Our trusty steed

How the Dataset was Collected

The dataset was collected by driving in urban areas of Oulu, Finland while having sensors installed on the roof of the car. Sensor data was collected and recorded via ROS2 on on-board computer. Recorded data includes stereo camera images, thermal camera images, lidar pointcloud, plus the car’s CAN bus data and GPS information.

Route and environmental specifics

Three separate people drove through the same route in Oulu on a sunny day in June. The city part includes cobblestones, traffic lights, parked vehicles, and pedestrians. The highway route begins with merging onto the highway, and then sustaining 80-100km/h speed.

City routeHighway route
city routehighway route
City route linkHighway route link

Computer and software setup

The computer inside the car is a NVIDIA Jetson AGX Orin Developer Kit on Ubuntu 22.04 running ROS2 nodes in Docker containers. The nodes include sensor drivers, and a recorder to write the messages on an SSD in the form of .mcap files. The source code for our setup is publicly available on github. The source codes for the .mcap processor and the image anonymizer is also publicly available.

Car and sensor setup

The car used was a Toyota RAV4 Hybrid 2019.

Thermal cameras: FLIR ADK 2.0 LWIR

Stereo camera: Carnegie Robotics Multisense S27

Lidar: Hesai OT128 Lidar

GPS: PCAN-GPS.

Recording settings for Lidar:

  • Standard resolution
  • Single-point first return
  • 600 RPM

image of the roof

Data format

The dataset has people’s faces and vehicle license plates blurred to respect people’s privacy. Hence the dataset does not contain the original .mcap files which would include unblurred images.

Data sourceDescriptionOriginal formatDataset formatTarget frequency
/lidar_points ROS2 topicLiDARPointCloud2 (230400 points).laz10hz
/image_raw ROS2 topicThermal camerasmono168-bit colormap .png60hz
/aux/image_color ROS2 topicStereo camera’s middle camerabgr88-bit rgb .png25hz
/left/image_rect ROS2 topicStereo camera’s left cameramono88-bit grayscale .png25hz
/right/image_rect ROS2 topicStereo camera’s right cameramono88-bit grayscale .png25hz
/left/depth ROS2 topicStereo camera’s estimated depth distance32FC18-bit colormap .png25hz
/left/cost ROS2 topicStereo camera’s confidence value of /left/depthmono88-bit grayscale .png25hz
Car CAN busCar sensor messagesHexadecimal bytesHuman-readable .json–
PCAN-GPSGPS sensor messagesHexadecimal bytesHuman-readable .json–

CAN and GPS frequencies are over 700 messages per second, however they have no “target” frequency. There are no messages lost in them, but unknown CAN signals are excluded out of this dataset. 100% of GPS signals are converted and included in this dataset. CAN bus is read and translated into known signals using .dbc file generated by opendbc software. No proprietary information was published when sharing the decoded signals and no NDA was broken. The generated dbc file had 43 message definitions.

Data examples

The following sample of data is from the dataset.

Stereo camera

/aux/image_color:

aux_image_color

/left/image_rect/right/image_rect
left_image_rectright_image_rect

/left/depth:

left_depth

/left/cost:

left_cost

Thermal camera

/flir_0/image_raw/flir_1/image_raw
left_image_rectright_image_rect

Lidar

/lidar_points:

lidar_points

CAN Bus

Example JSON:

    {
        "timestamp": 1780480412.007036,
        "frame_id": "0x1D3",
        "message": "PCM_CRUISE_2",
        "signal": "CHECKSUM",
        "value": 4
    },
    {
        "timestamp": 1780480412.007036,
        "frame_id": "0xB4",
        "message": "SPEED",
        "signal": "ENCODER",
        "value": 45
    },
    {
        "timestamp": 1780480412.007036,
        "frame_id": "0xB4",
        "message": "SPEED",
        "signal": "SPEED",
        "value": 28.18
    },

GPS

Example JSON:

    {
        "timestamp": 1780480412.039233,
        "frame_id": "0x601",
        "message": "BMC_MagneticField",
        "signal": "MagneticField_X",
        "value": -71.7
    },
    {
        "timestamp": 1780480412.039233,
        "frame_id": "0x601",
        "message": "BMC_MagneticField",
        "signal": "MagneticField_Y",
        "value": 41.699999999999996
    },
    {
        "timestamp": 1780480412.039233,
        "frame_id": "0x601",
        "message": "BMC_MagneticField",
        "signal": "MagneticField_Z",
        "value": -66.3
    },

Timestamps of all files are included in the file name in Unix time format.

Download links

City 1
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS
City 2
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS
City 3
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS
Highway 1
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS
Highway 2
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS
Highway 3
Size estimationDownload linkData source
5 GB/aux/image_colorStereo camera
3 GB/left/image_rectStereo camera
3 GB/right/image_rectStereo camera
2 GB/left/depthStereo camera
2 GB/left/costStereo camera
3 GB/lidar_pointsLidar
7 GB/flir_0/image_rawThermal camera
7 GB/flir_1/image_rawThermal camera
67 MBCar CAN bus & GPSCAN bus & PCAN-GPS

Files are stored in a .tar archive file. Most compression utilities such as WinRAR can extract them. On Linux, run the following on the command line:

tar -xvf <file_name>.tar

For example:

tar -xvf aux_image_color.tar