atlas

Research map / 3D vision / Depth and stereo

Fully Geometric Panoramic Localization

CVPR 2024 · 3D vision › Depth and stereo · approach: Scene coordinate regression for localization · 5 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.

Fully geometric panoramic localization that matches 2D lines from a panorama against a 3D line map using line distance and line-intersection point distance functions, with no visual descriptors or training.

Problem

Visual localization against 3D maps typically relies on visual descriptors, which are costly to store, raise privacy concerns, and fail under illumination or scene changes; line-only localization has been ambiguous and less accurate.

Approach

Uses line intersections labeled by principal direction clusters as point distance functions, decouples rotation and translation by caching canonicalized 3D distance functions and interpolating 2D distance functions, and refines poses by aligning intersection points and line directions, all without learned or hand-crafted descriptors.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
add point distance functions to line distance functions (ablation)Pose search · Stanford 2D-3D-S Area 1accuracy (0.1m, 5°): 0.57 -> 0.61Helped
decouple rotation and translation for 3D distance functions (ablation)Pose search · Stanford 2D-3D-S Area 1runtime (s), GPU: 45.049 -> 2.890Helped
decouple rotation and translation for 3D distance functions (ablation)Pose search · Stanford 2D-3D-S Area 1accuracy (0.1m, 5°): 0.62 -> 0.61No clear effect
enable canonicalization of 2D distance functions (ablation)Pose search · Stanford 2D-3D-S Area 1runtime (s), GPU: 0.396 -> 0.007Helped
add interpolation to canonicalized 2D distance functions (ablation)Pose search · Stanford 2D-3D-S Area 1runtime (s), GPU: 0.007 -> 0.004Helped
add rotation refinement after translation refinement (ablation)Pose refinement · OmniScenes Room 2rotation error: 1.56 -> 1.05Helped
add intersection cluster-guided matching (ablation)Pose refinement · OmniScenes Room 2accuracy (0.1m, 5°): 0.63 -> 0.77Helped
use line intersections and their geometric matching instead of visual descriptorsOurs · OmniScenes and Stanford 2D-3D-Saccuracy (0.1m, 5°): 0.67 vs 0.79Mixed
localize using line geometry under lighting changesOurs · OmniScenes, varying lighting conditionsaccuracy (0.1m, 5°): 0.77, 0.74, 0.74, 0.77No clear effect

Surprising findings

Limitations

Experimental setup

Datasets: Stanford 2D-3D-S OmniScenes Structured3D

Benchmarks: OmniScenes Stanford 2D-3D-S Structured3D

Metrics: localization accuracy at (0.1m, 5°) accuracy at (0.2m, 10°) accuracy at (0.3m, 15°) recall curves search runtime refinement runtime map size translation error rotation error

Baselines: LDL SFRS CosPlace PICCOLO CPO Chamfer LightGlue SuperGlue GlueStick GoMatch LoFTR Line Transformer

Builds on: LDL ICP Kabsch algorithm

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