You need to agree to share your Hugging Face information to access this dataset

This repository is publicly accessible, but you have to accept the conditions to access its files and content.

Log in or Sign Up to review the conditions and access this dataset content.

YAML Metadata Warning:empty or missing yaml metadata in repo card

Check out the documentation for more information.

T-Car nuScenes — release 1016

Driving data from the T-Car test vehicle (six cameras, a roof LiDAR, RTK INS) in the nuScenes v1.0-trainval format: load it with the nuscenes-devkit as is.

682 scenes of 20 s (3.79 h) from 54 recordings · 27,280 key-frame samples · 2,523,160 sensor frames · 1195 GB to download in 178 sensor tars + 1 table tar (1395 GB unpacked). No 3D box annotations (sample_annotation is empty).

Download and use

  1. Request access on this page (the dataset is gated), and log in: hf auth login.
  2. Download this release and put it together (assemble.py checks every tar's sha256 and extracts it):
pip install -U huggingface_hub
hf download shchon11/TCar --repo-type dataset --revision 1016 --local-dir tcar_tars
python tcar_tars/assemble.py --tars tcar_tars --out tcar_nuscenes      # -> tcar_nuscenes/ and tcar_nuscenes_2/
from nuscenes.nuscenes import NuScenes
from nuscenes.can_bus.can_bus_api import NuScenesCanBus
nusc = NuScenes(version="v1.0-trainval", dataroot="tcar_nuscenes")
can = NuScenesCanBus(dataroot="tcar_nuscenes")      # pose, ms_imu, meta per scene
nusc_2 = NuScenes(version="v1.0-trainval", dataroot="tcar_nuscenes_2")   # its own scene names

One dataset only: the root one with --exclude "tcar_nuscenes_2/*" on hf download.

Datasets in this repository

folder dataset scenes recordings GB
repository root tcar_nuscenes 682 54 1195
tcar_nuscenes_2/ tcar_nuscenes_2 116 8 200

Each is a complete nuScenes v1.0-trainval dataroot of its own. A dataset holds at most the 685 official train scene names, so the next one (a later volume of the same recordings series) starts the list again (scene-0001, ...): their scene names clash. assemble.py puts each together into its own folder; open each with its own NuScenes(dataroot=...). The same release (branch) holds all of them.

Some recordings only: download the tables and the recordings you want, and let assemble.py skip the rest (the tables still list every scene; the files of the others are just absent):

hf download shchon11/TCar --repo-type dataset --revision 1016 --local-dir tcar_tars \
    --include "manifest.json" --include "assemble.py" --include "meta/*" \
    --include "sensors/A-1_*/*" --include "sensors/B-2_*/*"
python tcar_tars/assemble.py --tars tcar_tars --out tcar_nuscenes --allow-missing

Updating: Coming from 1015: run the two commands above in the same directories — only the tars new in 1016 are downloaded and extracted. Nothing already extracted is changed; the tables are replaced. Add --delete-tars to assemble.py to remove each tar after extracting it (then hf download fetches it again next time).

Releases and versioning

Each release is a branch of this repository (--revision <name>), a complete dataset on its own; a release is never changed after it is published. main always holds the latest release (a copy, stored once), so hf download without --revision gets it; give --revision to stay on one release. Later releases only add data:

  • sensors/<recording>/<recording>.partNN.tar.gz — the sensor files (samples/, sweeps/) of a group of whole scenes of one recording, at most 10 GB unpacked (gzip: the LiDAR files shrink by about a third, the JPEGs not). Once published, a tar never changes and is carried into every later release (stored once).
  • meta/TCar_meta.tar.gz — the tables (v1.0-trainval/), can_bus/, maps/, the per-recording *.import.json (how each recording was converted) and curation/. The only file that changes between releases.
  • manifest.json — every tar with its recording, scene tokens, files, bytes and sha256, and the release history.
  • Scene tokens never change. Scene names (scene-0001, …) are the nuScenes train split names in recording order; the names of released scenes do not change either. All scenes are in the train split.
release date recordings added scenes added scenes in total parser commit
1002 2026-10-02 A-1, A-2, A-3, A-4, A-5, A-6, A-7, A-8, A-9, A-10, B-1, B-2, B-3, B-4, B-5, B-6, B-7, D-1, D-2, D-4, D-5 268 268 8a1f2f6
1015 2026-10-15 C-1, C-2, C-3, C-4, C-5, C-6, C-7, C-8, D-3, E-1, E-2, E-3, E-4, E-5, E-6, F-1, F-2, F-3, F-4, F-5 286 554 36fc380 (+local changes)
1016 2026-10-17 G-1, G-2, G-3, G-4, G-5, G-6, G-7, G-8, G-9, H-1, H-2, H-3, H-5 128 682 f6aa456 (+local changes)

The 0923 branch holds the calibration sample recordings of 2026-09-23 (one tar per channel, its own scene numbering); they are not part of this series.

Contents

course dates recordings scenes time GB
A 2026-09-28 10 119 40 min 224
B 2026-09-29 7 103 34 min 181
C 2026-10-06 8 133 44 min 242
D 2026-09-29 5 64 21 min 99
E 2026-10-06 6 58 19 min 95
F 2026-10-06 5 77 26 min 123
G 2026-10-12, 2026-10-14 9 83 28 min 153
H 2026-10-14 4 45 15 min 77
channel sensor data rate frames
CAM_BACK camera 1920×1080 JPEG 29 Hz 398,248
CAM_BACK_LEFT camera 1920×1080 JPEG 29 Hz 398,248
CAM_BACK_RIGHT camera 1920×1080 JPEG 29 Hz 398,248
CAM_FRONT camera 1920×1080 JPEG 29 Hz 398,248
CAM_FRONT_LEFT camera 1920×1080 JPEG 29 Hz 398,248
CAM_FRONT_RIGHT camera 1920×1080 JPEG 29 Hz 398,248
LIDAR_TOP lidar point cloud (.pcd.bin) 10 Hz 133,672

Key frames (samples/) are 2 Hz, synchronised across the seven sensors as in nuScenes; every other frame is a sweep (sweeps/). LiDAR files hold five float32 per point (x, y, z, intensity, ring), as in nuScenes. This set carries no calibration: calibrated_sensor holds placeholders (identity extrinsics, a 90° pinhole camera_intrinsic, one record per sensor and recording) and the images are as recorded, so projecting between sensors with these values is not meaningful.

Coordinate frames

ego_pose is in the location's global frame, as in nuScenes: metres, x east, y north, z up, on the tangent plane at 37.20° N, 126.83° E (height 0 on the WGS84 ellipsoid). log.json names it in the extra key global_frame (enu@37.200000,126.830000,0.000). Ego poses and the CAN bus pose come from the NovAtel INSPVA solution (100 Hz, RTK), placed at the receiver's GPS measurement time.

Recordings

recording date scenes tars GB first release
A-1_2026-09-28-14-40-58 2026-09-28 10 3 18.5 1002
A-2_2026-09-28-14-45-11 2026-09-28 10 3 18.8 1002
A-3_2026-09-28-16-32-23 2026-09-28 12 3 22.4 1002
A-4_2026-09-28-14-51-38 2026-09-28 10 3 19.1 1002
A-5_2026-09-28-14-55-45 2026-09-28 12 3 23.1 1002
A-6_2026-09-28-15-02-17 2026-09-28 15 4 28.6 1002
A-7_2026-09-28-15-08-17 2026-09-28 12 3 21.7 1002
A-8_2026-09-28-15-13-01 2026-09-28 10 3 18.4 1002
A-9_2026-09-28-15-19-08 2026-09-28 12 3 23.1 1002
A-10_2026-09-28-16-03-14 2026-09-28 16 4 30.4 1002
B-1_2026-09-29-11-30-09 2026-09-29 12 3 21.5 1002
B-2_2026-09-29-11-37-49 2026-09-29 10 3 18.5 1002
B-3_2026-09-29-11-42-12 2026-09-29 17 5 31.1 1002
B-4_2026-09-29-11-50-32 2026-09-29 12 3 20.8 1002
B-5_2026-09-29-11-55-19 2026-09-29 13 4 22.5 1002
B-6_2026-09-29-12-02-16 2026-09-29 24 6 40.9 1002
B-7_2026-09-29-12-19-37 2026-09-29 15 4 25.8 1002
C-1_2026-10-06-11-04-57 2026-10-06 16 4 30.3 1015
C-2_2026-10-06-11-10-33 2026-10-06 21 5 34.1 1015
C-3_2026-10-06-11-20-51 2026-10-06 16 4 29.0 1015
C-4_2026-10-06-11-45-54 2026-10-06 12 3 21.9 1015
C-5_2026-10-06-11-33-51 2026-10-06 12 3 21.1 1015
C-6_2026-10-06-11-58-21 2026-10-06 22 6 42.2 1015
C-7_2026-10-06-12-09-56 2026-10-06 17 5 32.1 1015
C-8_2026-10-06-12-15-48 2026-10-06 17 5 31.5 1015
D-1_2026-09-29-17-08-46 2026-09-29 8 2 10.5 1002
D-2_2026-09-29-17-15-57 2026-09-29 13 3 20.6 1002
D-3_2026-09-29-17-20-32 2026-09-29 18 4 28.7 1015
D-4_2026-09-29-17-33-25 2026-09-29 17 4 28.7 1002
D-5_2026-09-29-17-44-05 2026-09-29 8 2 10.7 1002
E-1_2026-10-06-15-05-45 2026-10-06 7 2 11.2 1015
E-2_2026-10-06-15-09-30 2026-10-06 10 2 16.0 1015
E-3_2026-10-06-15-13-04 2026-10-06 12 3 20.2 1015
E-4_2026-10-06-15-17-20 2026-10-06 11 3 18.3 1015
E-5_2026-10-06-15-21-16 2026-10-06 12 3 19.8 1015
E-6_2026-10-06-15-25-25 2026-10-06 6 2 9.5 1015
F-1_2026-10-06-15-36-52 2026-10-06 20 5 33.2 1015
F-2_2026-10-06-15-51-37 2026-10-06 16 4 25.2 1015
F-3_2026-10-06-16-05-27 2026-10-06 5 1 7.6 1015
F-4_2026-10-06-16-10-18 2026-10-06 19 4 29.7 1015
F-5_2026-10-06-16-18-39 2026-10-06 17 4 27.3 1015
G-1_2026-10-12-16-21-54 2026-10-12 10 2 15.8 1016
G-2_2026-10-12-16-26-33 2026-10-12 7 2 12.0 1016
G-3_2026-10-12-16-29-07 2026-10-12 8 2 13.2 1016
G-4_2026-10-14-11-42-42 2026-10-14 7 2 11.6 1016
G-5_2026-10-14-11-46-28 2026-10-14 8 2 13.3 1016
G-6_2026-10-14-11-54-18 2026-10-14 10 3 19.0 1016
G-7_2026-10-14-11-57-41 2026-10-14 8 2 16.6 1016
G-8_2026-10-14-12-10-23 2026-10-14 12 4 24.8 1016
G-9_2026-10-14-12-23-07 2026-10-14 13 4 27.0 1016
H-1_2026-10-14-13-43-16 2026-10-14 12 3 21.8 1016
H-2_2026-10-14-13-52-59 2026-10-14 11 3 17.6 1016
H-3_2026-10-14-13-59-19 2026-10-14 11 3 18.7 1016
H-5_2026-10-14-14-23-06 2026-10-14 11 3 18.9 1016

Maintainers: making the next release

Releases are made with scripts/hf_release.py of the parser repository (ROSbag_nuscenes_parser, branch tcar-gui; the commit of each release is in the table above):

# new recordings: parse them, curate them in the TCAR Parser app, press 최종 확정, then
python scripts/hf_release.py --branch <new> --from 1016 --token-file <hf token file>            # plan
python scripts/hf_release.py --branch <new> --from 1016 --token-file <hf token file> --upload   # build + upload

It refuses to publish unless every scene is locked and the dataset passes the checks (table references, devkit, CAN bus), and unless every tar already published still matches the dataset. Only the new recordings' tars are built and uploaded (one commit each, resumable); the tables, manifest, this card and assemble.py go last. First release of this series: 1002.

Downloads last month
107