atlas

Research map / Point clouds / Point cloud classification

TAPVid-3D: A Benchmark for Tracking Any Point in 3D

NeurIPS 2024 · Point clouds › Point cloud classification · approach: Point cloud detection and tracking · 6 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Introduces TAPVid-3D, a real-world benchmark of 4,000+ clips for long-range 3D point tracking built from Aria Digital Twin, DriveTrack and Panoptic Studio, with new 3D-AJ/APD/OA metrics and baseline evaluations of 2D trackers combined with depth estimators.

Problem

Existing real-world tracking-any-point benchmarks only evaluate 2D tracking because they lack metric 3D ground-truth trajectories, so 3D point tracking from monocular video cannot be measured on real footage.

Approach

Derive metric 3D point trajectories and visibility from three existing real-world datasets (digital-twin annotations, LIDAR plus 3D boxes, and dynamic Gaussian splat reconstructions), and extend the TAP Average Jaccard metric to 3D with depth-adaptive thresholds and several scale-alignment schemes.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Use COLMAP instead of ZoeDepth for depth estimation2D point trackers on TAPVid-3D DriveTrack · DriveTrack3D-AJ: 5.4 -> 11.8Helped
Use ZoeDepth instead of COLMAP for depth estimation2D point trackers on TAPVid-3D Panoptic Studio · Panoptic Studio3D-AJ: 6.9 -> 11.3Helped
Use BootsTAPIR instead of TAPIR with ZoeDepth2D point tracking plus depth estimation · TAPVid-3D full_eval (Average)3D-AJ: 8.3 -> 8.8Helped
Use global median scaling instead of per-trajectory scaling (ablation)BootsTAPIR + COLMAP · TAPVid-3D full_eval (Average)3D-AJ: 9.3 -> 20.6Hurt
Use global median scaling instead of local neighborhood scaling (ablation)BootsTAPIR + COLMAP · TAPVid-3D full_eval (Average)3D-AJ: 9.3 -> 17.8Hurt
Use per-trajectory scaling instead of global median scaling (ablation)TAPIR-3D · TAPVid-3D full_eval (Average)3D-AJ: 3.1 -> 8.6Helped
Use local neighborhood scaling instead of global median scaling (ablation)TAPIR-3D · TAPVid-3D full_eval (Average)3D-AJ: 3.1 -> 6.1Helped
Use per-trajectory scaling instead of global median scaling (ablation)BootsTAPIR + ZoeDepth · TAPVid-3D full_eval (Average)3D-AJ: 8.8 -> 12.3Helped

Surprising findings

Limitations

Experimental setup

Datasets: Aria Digital Twin DriveTrack Panoptic Studio Waymo Open Dataset Kubric

Benchmarks: TAPVid-3D TAPVid-DAVIS

Metrics: 3D-AJ APD OA 2D-AJ

Baselines: TAPIR + COLMAP CoTracker + COLMAP BootsTAPIR + COLMAP TAPIR + ZoeDepth CoTracker + ZoeDepth BootsTAPIR + ZoeDepth TAPIR-3D SpatialTracker Static Baseline

Builds on: TAP-Vid TAPIR BootsTAPIR CoTracker COLMAP ZoeDepth SpatialTracker

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy