Papers › Revisit Anything: Visual Place Recognition via Image Segment Retrieval

Revisit Anything: Visual Place Recognition via Image Segment Retrieval

26 Sep 2024arXiv:2409.18049archive 2025-07-28

Kartik Garg, Sai Shubodh Puligilla, Shishir Kolathaya, Madhava Krishna, Sourav Garg

Accurately recognizing a revisited place is crucial for embodied agents to localize and navigate. This requires visual representations to be distinct, despite strong variations in camera viewpoint and scene appearance. Existing visual place recognition pipelines encode the "whole" image and search for matches. This poses a fundamental challenge in matching two images of the same place captured from different camera viewpoints: "the similarity of what overlaps can be dominated by the dissimilarity of what does not overlap". We address this by encoding and searching for "image segments" instead of the whole images. We propose to use open-set image segmentation to decompose an image into `meaningful' entities (i.e., things and stuff). This enables us to create a novel image representation as a collection of multiple overlapping subgraphs connecting a segment with its neighboring segments, dubbed SuperSegment. Furthermore, to efficiently encode these SuperSegments into compact vector representations, we propose a novel factorized representation of feature aggregation. We show that retrieving these partial representations leads to significantly higher recognition recall than the typical whole image based retrieval. Our segments-based approach, dubbed SegVLAD, sets a new state-of-the-art in place recognition on a diverse selection of benchmark datasets, while being applicable to both generic and task-specialized image encoders. Finally, we demonstrate the potential of our method to ``revisit anything'' by evaluating our method on an object instance retrieval task, which bridges the two disparate areas of research: visual place recognition and object-goal navigation, through their common aim of recognizing goal objects specific to a place. Source code: https://github.com/AnyLoc/Revisit-Anything.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 6 ran (2 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 6 samples that ran has no recorded date.

anyloc/revisit-anything officialmentioned in papermentioned on GitHubpytorchBSD-3-ClauseSyntology: 9 samples, 6 ran (4 instrument-failed) · 3 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
3ran; the contract check could not run
2ran
3unverified

Licence: 5 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 5 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from anyloc/revisit-anything. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

anyloc/revisit-anything official repository 9 samples, 6 ran (4 instrument-failed) · 3 unverified
calc_recall place_rec_pca_finetuned.py ran BSD-3-Clause (permissive) · e642533d58d111fd · report fixture: signature pred:list/1/list, gt:list/1/list, n:int/0/int, analysis:bool/0/bool · returned list · level recorded 2026-09-24
first_k_unique_indices place_rec_pca_finetuned.py ran · our draft was wrong fingerprinted BSD-3-Clause (permissive) · d0a8a0cd6c16fac9 · report fixture: signature ranked_indices:list/1/int, K:int/0/int · returned list · level recorded 2026-09-24
get_matches place_rec_pca_finetuned.py ran BSD-3-Clause (permissive) · 8e50745b36bf52b1 · report fixture: signature matches:list/1/ndarray, gt:list/1/int, sims:list/1/ndarray, segRangeQuery:list/1/int, imIndsRef:ndarray/1/int, n:int/0/int, method:str/0/str · returned list · level recorded 2026-09-24
get_rel_pos in 54 papers
census: 3 implementations from 6 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
sam/segment_anything/modeling/image_encoder.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant BSD-3-Clause (permissive) · 733d7f0bedcb74c2 · report fixture: signature q_size:int/0/int, k_size:int/0/int, rel_pos:Tensor/2/float · returned Tensor · level recorded, date not recorded
window_partition in 377 papers
census: 13 implementations from 17 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
sam/segment_anything/modeling/image_encoder.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic fingerprinted BSD-3-Clause (permissive) here; the stored copy is pointer only · 105fa08885dc36cc · report fixture: signature x:Tensor/4/float, window_size:int/0/int · returned tuple · level recorded 2026-09-22
window_unpartition in 56 papers sam/segment_anything/modeling/image_encoder.py ran; the contract check could not run (RAISES) BSD-3-Clause (permissive) here; the stored copy is pointer only · 50f37d517e2be27f · report fixture: signature windows:Tensor/4/float, window_size:int/0/int, pad_hw:tuple/1/int, hw:tuple/1/int · returned Tensor · level recorded 2026-09-22
build_sam_vit_b in 53 papers sam/segment_anything/build_sam.py unverified BSD-3-Clause (permissive) here; the stored copy is pointer only · f9bc5f31ce61cee8 · report
build_sam_vit_h in 54 papers sam/segment_anything/build_sam.py unverified BSD-3-Clause (permissive) here; the stored copy is pointer only · 6b77c1f11fff3ed6 · report
build_sam_vit_l in 53 papers sam/segment_anything/build_sam.py unverified BSD-3-Clause (permissive) here; the stored copy is pointer only · 3f8890e695469246 · report

Tasks

Image SegmentationNavigateRetrievalSemantic SegmentationVisual Place Recognition

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Visual Place Recognition 17 Places SegVLAD-FineT (M) Recall@1 95.3 #1 of 8 Archive leaderboard report
Visual Place Recognition AmsterTime SegVLAD-FineT (M) Recall@1 60.2 #6 of 8 Archive leaderboard report
Visual Place Recognition Baidu Mall SegVLAD-PreT (M) Recall@1 80.4 #1 of 8 Archive leaderboard report
Visual Place Recognition Inside Out SegVLAD-FineT (M) Recall@1 7.2 #1 of 1 Archive leaderboard report
Visual Place Recognition Pittsburgh-30k-test SegVLAD-FineT (M) Recall@1 93.1 #8 of 22 Archive leaderboard report
Visual Place Recognition VP Air SegVLAD-PreT (M) Recall@1 67.2 #1 of 1 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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