Browse State-of-the-Art › Point Cloud Registration

Point Cloud Registration

229 papers with code · 24 benchmarks · 12 datasets archive 2025-07-28

Computer Vision

Point Cloud Registration is a fundamental problem in 3D computer vision and photogrammetry. Given several sets of points in different coordinate systems, the aim of registration is to find the transformation that best aligns all of them into a common coordinate system. Point Cloud Registration plays a significant role in many vision applications such as 3D model reconstruction, cultural heritage management, landslide monitoring and solar energy analysis.

Source: Iterative Global Similarity Points : A robust coarse-to-fine integration solution for pairwise 3D point cloud registration

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

24 leaderboard tables shown for this task, 24 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. 10 shown of 24 until expanded.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
ETH (trained on 3DMatch) (20 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
3DMatch Benchmark (15 rows) IMFNet IMFNet: Interpretable Multimodal Fusion for Point Cloud Registration code — Compare
3DMatch (at least 30% overlapped - FCGF setting) (14 rows) NgeNet Leveraging Inlier Correspondences Proportion for Point Cloud Registration code — Compare
KITTI (trained on 3DMatch) (14 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
3DLoMatch (10-30% overlap) (13 rows) CoFF Cross-modal feature fusion for robust point cloud registration... code — Compare
3DMatch (at least 30% overlapped - sample 5k interest points) (11 rows) NgeNet Leveraging Inlier Correspondences Proportion for Point Cloud Registration code — Compare
KITTI (FCGF setting) (11 rows) GeoTransformer Geometric Transformer for Fast and Robust Point Cloud Registration code Syntology community repositories only · 4 ran (of which 4 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified; every one of the 4 samples that ran constructed an object rather than computing a result Compare
FPv1 (8 rows) Greedy Grid Search Challenging the Universal Representation of Deep Models for 3D... code — Compare
FP-O-E (6 rows) FPFH+SC2-PCR SC2-PCR: A Second Order Spatial Compatibility for Efficient and... — — Compare
FP-O-H (6 rows) FPFH+SC2-PCR SC2-PCR: A Second Order Spatial Compatibility for Efficient and... — — Compare
FP-O-M (6 rows) Exhaustive Grid Search Addressing the generalization of 3D registration methods with a... code — Compare
FP-R-E (6 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
FP-R-H (6 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
FP-R-M (6 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
FP-T-E (6 rows) FPFH+SC2-PCR SC2-PCR: A Second Order Spatial Compatibility for Efficient and... — — Compare
FP-T-H (6 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
FP-T-M (6 rows) Exhaustive Grid Search Addressing the generalization of 3D registration methods with a... code — Compare
KITTI (6 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
RotKITTI Registration Benchmark (6 rows) UMERegRobust UMERegRobust -- Universal Manifold Embedding Compatible Features... code — Compare
3DMatch (trained on KITTI) (5 rows) GeDi Learning general and distinctive 3D local deep descriptors for... code — Compare
KITTI (Distant PCR) (4 rows) GCL+KPConv Density-invariant Features for Distant Point Cloud Registration code — Compare
nuScenes (Distant PCR) (4 rows) GCL+KPConv Density-invariant Features for Distant Point Cloud Registration code — Compare
ScanNet++ (trained on 3DMatch) (3 rows) CoFF Cross-modal feature fusion for robust point cloud registration... code — Compare
3RScan (2 rows) SG-PGM SG-PGM: Partial Graph Matching Network with Semantic Geometric... 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

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

Subtasks archive 2025-07-28

1 subtask in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 447 · with a code link: 229 · where Syntology ran a sample: 55 (50 with a run with no instrument failure, 5 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (55 of 447 tagged: 50 with a run with no instrument failure, 5 where every run was a failure of Syntology's instrument)

Page 1 of 5: papers 1 to 100 of 447, 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 30 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