Papers › CrossLoc3D: Aerial-Ground Cross-Source 3D Place Recognition

CrossLoc3D: Aerial-Ground Cross-Source 3D Place Recognition

31 Mar 2023ICCV 2023 1arXiv:2303.17778archive 2025-07-28

Tianrui Guan, Aswath Muthuselvam, Montana Hoover, Xijun Wang, Jing Liang, Adarsh Jagan Sathyamoorthy, Damon Conover, Dinesh Manocha

We present CrossLoc3D, a novel 3D place recognition method that solves a large-scale point matching problem in a cross-source setting. Cross-source point cloud data corresponds to point sets captured by depth sensors with different accuracies or from different distances and perspectives. We address the challenges in terms of developing 3D place recognition methods that account for the representation gap between points captured by different sources. Our method handles cross-source data by utilizing multi-grained features and selecting convolution kernel sizes that correspond to most prominent features. Inspired by the diffusion models, our method uses a novel iterative refinement process that gradually shifts the embedding spaces from different sources to a single canonical space for better metric learning. In addition, we present CS-Campus3D, the first 3D aerial-ground cross-source dataset consisting of point cloud data from both aerial and ground LiDAR scans. The point clouds in CS-Campus3D have representation gaps and other features like different views, point densities, and noise patterns. We show that our CrossLoc3D algorithm can achieve an improvement of 4.74% - 15.37% in terms of the top 1 average recall on our CS-Campus3D benchmark and achieves performance comparable to state-of-the-art 3D place recognition method on the Oxford RobotCar. The code and CS-CAMPUS3D benchmark will be available at github.com/rayguan97/crossloc3d.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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 15 code samples harvested from 1 repository linked to this paper: 11 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 15 samples from 1 repository, 11 ran (10 with no instrument failure; 1 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

rayguan97/crossloc3d officialmentioned in papermentioned on GitHubpytorchSyntology: 15 samples, 11 ran (1 instrument-failed) · 4 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

15 samples harvested: 11 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; 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
10ran
4unverified

Licence: 0 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from rayguan97/crossloc3d. “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”. For 4 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

rayguan97/crossloc3d official repository 15 samples, 11 ran (1 instrument-failed) · 4 unverified
DiffTransformerBlock models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · 49a28a91da28cd6a · report fixture: returned DiffTransformerBlock · level recorded 2026-09-22
GatingContext models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · 25dfda388912d104 · report fixture: returned GatingContext · level recorded 2026-09-22
GeM in 5 papers models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · 039a0681e332e8c7 · report fixture: returned GeM · level recorded 2026-09-22
MAC models/ours/model.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · a137e6ae7a2306dc · report fixture: returned MAC · level recorded 2026-09-22
NetVLADLoupe models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · d9300c949a291ace · report fixture: returned NetVLADLoupe · level recorded 2026-09-22
NetVladWrapper models/ours/model.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 44a4c9c114054f04 · report fixture: returned NetVladWrapper · level recorded 2026-09-22
RandomOrLearnedSinusoidalPosEmb models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · 4611d53e8f11052e · report fixture: returned RandomOrLearnedSinusoidalPosEmb · level recorded 2026-09-22
SPoC models/ours/model.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 004ffb97f34d150e · report fixture: returned SPoC · level recorded 2026-09-22
SinusoidalPosEmb in 18 papers
census: 6 implementations from 6 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind float, dtype float32
models/ours/model.py ran · metamorphic tier: invariant fingerprinted MIT (permissive) · f97842720e968c4b · report fixture: signature x:Tensor/1/float · returned Tensor · level recorded 2026-09-22
TCenterAttentionLayer models/ours/model.py ran · metamorphic tier: deterministic MIT (permissive) · 7b1d62857496e935 · report fixture: returned TCenterAttentionLayer · level recorded 2026-09-22
l2norm in 84 papers
census: 12 implementations from 20 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/ours/model.py ran · our draft was wrong fingerprinted MIT (permissive) · 8deabf7913c20741 · report fixture: signature inp:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded 2026-09-22
ECALayer models/ours/model.py unverified MIT (permissive) · 5a185e87c545019a · report
GatedInceptionBlock models/ours/model.py unverified MIT (permissive) · de332b4043605765 · report
Ours models/ours/model.py unverified MIT (permissive) · 05dd8633cd267827 · report
Ours3DFPN models/ours/model.py unverified MIT (permissive) · 2a6a78f87852fb30 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for CROSSLOC3D (graph method: CROSSLOC3D). 15 bricks; individually on a fixture: 11 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

  1. Ours entry · level 0 · unverified · 05dd8633cd267827
  2. GeM helper · level 1 · ran · 039a0681e332e8c7
  3. MAC helper · level 1 · ran · a137e6ae7a2306dc
  4. NetVladWrapper model · level 1 · ran · 44a4c9c114054f04
  5. Ours3DFPN model · level 0 · unverified · 2a6a78f87852fb30
  6. SPoC helper · level 1 · ran · 004ffb97f34d150e
  7. NetVLADLoupe model · level 1 · ran · d9300c949a291ace
  8. DiffTransformerBlock model · level 1 · ran · 49a28a91da28cd6a
  9. GatedInceptionBlock model · level 0 · unverified · de332b4043605765
  10. GatingContext helper · level 1 · ran · 25dfda388912d104
  11. RandomOrLearnedSinusoidalPosEmb helper · level 1 · ran · 4611d53e8f11052e
  12. SinusoidalPosEmb helper · level 1 · ran · f97842720e968c4b
  13. TCenterAttentionLayer model · level 1 · ran · 7b1d62857496e935
  14. ECALayer model · level 0 · unverified · 5a185e87c545019a
  15. l2norm helper · level 1 · ran · our draft was wrong · 8deabf7913c20741

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2303.17778") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

3D Place RecognitionMetric Learning

Datasets

Introduced by this paper, per the archive.

CS-Campus3D

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Place Recognition CS-Campus3D CrossLoc3D AR@1 74.12 #1 of 7 Archive leaderboard report
3D Place Recognition CS-Campus3D CrossLoc3D AR@1 cross-source 70.73 #1 of 7 Archive leaderboard report
3D Place Recognition CS-Campus3D CrossLoc3D AR@1% 83.04 #1 of 7 Archive leaderboard report
3D Place Recognition CS-Campus3D CrossLoc3D AR@1% cross-source 85.74 #1 of 7 Archive leaderboard report
3D Place Recognition Oxford RobotCar Dataset CrossLoc3D AR@1 94.36 #1 of 10 Archive leaderboard report
3D Place Recognition Oxford RobotCar Dataset CrossLoc3D AR@1% 98.59 #1 of 10 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.

Methods

ConvolutionDiffusion

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