Browse State-of-the-Art › Depth Completion

Depth Completion

96 papers with code · 9 benchmarks · 11 datasets archive 2025-07-28

Computer Vision

The Depth Completion task is a sub-problem of depth estimation. In the sparse-to-dense depth completion problem, one wants to infer the dense depth map of a 3-D scene given an RGB image and its corresponding sparse reconstruction in the form of a sparse depth map obtained either from computational methods such as SfM (Strcuture-from-Motion) or active sensors such as lidar or structured light sensors.

Source: LiStereo: Generate Dense Depth Maps from LIDAR and Stereo Imagery , Unsupervised Depth Completion from Visual Inertial Odometry

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

9 leaderboard tables shown for this task, 9 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 1 placed): VOID (1 judged, 0 placed), NYU-Depth V2 (1 judged, 0 placed), KITTI (1 judged, 1 placed), VOID-150 (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
KITTI Depth Completion (16 rows) SemAttNet SemAttNet: Towards Attention-based Semantic Aware Guided Depth Completion code — Compare
VOID (6 rows) NLSPN Non-Local Spatial Propagation Network for Depth Completion code Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified Compare
NYU-Depth V2 (3 rows) NLSPN Non-Local Spatial Propagation Network for Depth Completion code Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified Compare
Matterport3D (2 rows) DM-LRN-b4 Decoder Modulation for Indoor Depth Completion — — Compare
KITTI (1 row) FusionDepth Advancing Self-supervised Monocular Depth Learning with Sparse LiDAR code Syntology official (archive's flag): 15 ran · 15 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 1 honoured, 1 violated, 11 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified Compare
KITTI Depth Completion Eigen Split (1 row) DSN On Deep Learning Techniques to Boost Monocular Depth Estimation... — — Compare
KITTI Depth Completion 500 points (1 row) CFCNet Deep RGB-D Canonical Correlation Analysis For Sparse Depth Completion code — Compare
PLAD (1 row) Struct-MDC Struct-MDC: Mesh-Refined Unsupervised Depth Completion Leveraging... code — Compare
VOID-150 (1 row) Struct-MDC Struct-MDC: Mesh-Refined Unsupervised Depth Completion Leveraging... code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

11 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 242 · with a code link: 96 · where Syntology ran a sample: 15 (13 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (15 of 242 tagged: 13 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument)

Page 1 of 3: papers 1 to 100 of 242, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 16 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections