- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper shows that retrieval-then-localization pipelines in cross-view geolocalization throw away useful information by keeping only the top-1 aerial tile, since neighboring tiles in the top-k often overlap the same area. GeoHypLoc uses off-the-shelf sample4geo to retreive first top-5 images and then it groups the top-5 retrieved tiles by geographic adjacency and keeps the group with the highest retrieval support. It then runs CCVPE (off-the-shelf fine-grained geolocaization model) on each tile in that group, and fuses the outputs on a shared world map at every stage, and refines the final response with two small correction branches. On VIGOR it beats cascaded pipleines (Sample4Geo+CCVPE) on both splits. Gains are clear on same-area and smaller on cross-area.
Critical strengths
1- The motivation is good. The top-5 often contains several overlapping correct image tiles and current pipelines ignore them. So testing the full retrieval-plus-localization pipeline is the right way to evaluate this and give more practical large-scale cross-view geolocalization for real-world applications.
2- The analysis of failure cases is useful. The paper shows that many errors come from ambiguous responses with multiple strong peaks. This gives a clear picture of where current localizers fail and where multiple references help.
Critical weaknesses
1- I’m not convinced the gains come from the proposed idea. In Table 3, just retraining CCVPE on more retrieved tiles and testing on top-1 only (config A) gives almost the same same-area results as the full model. Joint multi-reference localization is even a bit worse than A on same-area, and the geographic grouping doesn’t do better than simple rank-based selection. Since the main claim of the paper is that multi-reference fusion with geographic grouping drives the improvement, this is a big concern. Right now it looks like much of the gain might come from the extra training.
2- The evaluation doesn’t show the method is worth its cost. The only real baseline is Sample4Geo+CCVPE, while stronger localizers like HC-Net, which is more accurate than CCVPE on VIGOR, are missing. UnifyGeo is cited but not compared, even though it’s the closest prior work and also uses multiple retrieved candidates. On top of that, the method roughly doubles latency and uses about seven times more memory than CCVPE for a fairly small gain on cross-area, and everything is tested only on VIGOR with known orientation. Without stronger baselines or a second dataset, it’s hard to tell whether the improvement holds up or justifies the extra compute.
Questions for authors
Clarifications:
1- Was the Sample4Geo+CCVPE baseline fine-tuned with the same 5-epoch schedule and DARK decoding as your model? If not, how much of the gain do you think comes from the extra training and decoding rather than from using multiple references?
2- In Table 3, joint localization (config C) is slightly worse than independent training (config A) on same-area but better on cross-area. How do you explain this, and what does it say about when multi-reference fusion actually helps?
3- How does your method differ from UnifyGeo, which also uses multiple retrieved candidates through reranking? What does your approach offer that UnifyGeo does not?
4- Why did you choose the RNG graph to form H*, rather than simpler options like using all top-5 tiles or grouping tiles within a fixed distance?
5- All results come from a single seed. How stable are they across runs, given that several cross-area differences are only 1 to 2 points?
Suggestions for future work:
1- Comparing against simpler fusion options, such as merging per-tile CCVPE heatmaps on the world map or stitching the tiles into one image, would strengthen the case for the stage-wise fusion design.
2- Testing with stronger localizers such as HC-Net, FG² or Loc², and comparing directly with UnifyGeo, would make the contribution clearer.
3- Results on a second dataset or with unknown orientation would show whether the method generalizes beyond VIGOR with known orientation.
7 comments
Response 1/4: Attribution of gains and the simpler RGB implementation
Your suggestion is valuable for clarifying how geographic observations contribute to localization.
W1, Q1-Q2 and Suggestion 1: training, geographic input and fusion.
The original CCVPE baseline used released weights and its original output, not matched five-epoch fine-tuning and DARK. The independent and joint configurations also differed in readout. We therefore agree that the original table did not isolate the effect of interaction.
We now compare Base, final-response Mean, newly evaluated Full interaction, and geographic RGB input. CC denotes Sample4Geo+CCVPE; Uni denotes UnifyGeo with official retrieval and reranking. Full and RGB use E3 checkpoints; RGB reports mean±sample standard deviation over seeds 17/2026/68. Full reports the individual seed indicated in the table.
| Split | Method | Seed | Acc@1m | Acc@3m | Acc@5m | Acc@10m | Median (m) |
|---|---|---|---|---|---|---|---|
| Same | CC Base | released | 31.681 | 66.975 | 75.909 | 83.745 | 1.618 |
| Same | GeoHypLoc (S4G+CC; Mean) | 17 | 32.111 | 63.511 | 70.912 | 77.628 | 1.671 |
| Same | GeoHypLoc (S4G+CC; Full) | 23 | 36.230 | 71.615 | 79.793 | 86.311 | 1.417 |
| Same | GeoHypLoc (S4G+CC; RGB) | 17/2026/68 | 37.118±0.031 | 71.731±0.058 | 80.058±0.040 | 86.603±0.046 | 1.373±0.003 |
| Same | GeoHypLoc (Uni; Mean) | 17 | 40.422 | 73.847 | 80.646 | 85.104 | 1.259 |
| Same | Uni Base | released | 40.797 | 76.400 | 83.604 | 88.328 | 1.235 |
| Same | GeoHypLoc (Uni; Full) | 17 | 40.869 | 75.215 | 82.017 | 85.984 | 1.242 |
| Same | GeoHypLoc (Uni; RGB) | 17/2026/68 | 42.327±0.114 | 76.932±0.015 | 83.767±0.063 | 87.967±0.070 | 1.193±0.003 |
| Cross | CC Base | released | 20.840 | 53.473 | 60.787 | 66.337 | 2.557 |
| Cross | GeoHypLoc (S4G+CC; Mean) | 17 | 20.116 | 51.056 | 57.692 | 62.245 | 2.833 |
| Cross | GeoHypLoc (S4G+CC; Full) | 23 | 21.852 | 55.932 | 63.102 | 67.562 | 2.328 |
| Cross | GeoHypLoc (S4G+CC; RGB) | 17/2026/68 | 21.854±0.172 | 55.915±0.227 | 63.294±0.155 | 68.019±0.089 | 2.336±0.022 |
| Cross | GeoHypLoc (Uni; Mean) | 17 | 26.616 | 64.134 | 68.855 | 70.997 | 1.777 |
| Cross | Uni Base | released | 26.424 | 65.335 | 70.501 | 72.643 | 1.768 |
| Cross | GeoHypLoc (Uni; Full) | 17 | 25.917 | 63.627 | 68.237 | 70.103 | 1.806 |
| Cross | GeoHypLoc (Uni; RGB) | 17/2026/68 | 27.484±0.151 | 65.679±0.148 | 70.311±0.101 | 72.358±0.054 | 1.714±0.007 |
Accuracies are percentages. CC Base uses DARK; Uni Base uses native readout. Mean independently localizes H* members with RGB seed17 E3 weights, aligns and averages their base responses, then applies DARK. Full and RGB include response correction and continuous readout. The RGB rows use the three-seed results of Table 1; Appendix D.3 compares the default single-seed configuration and describes each readout.
Following your suggestion, we adopt geographic RGB input as the main implementation: georeferenced observations are aligned before aerial encoding, valid RGB values are averaged at overlaps, and the native coarse-to-fine localizer processes the resulting region. Full interaction remains an appendix alternative. The evidence supports geographic observation organization without requiring learned stage-wise interaction.
For a matched inference comparison, we also fixed RGB seed17 E3 weights, H* and base-response DARK. RGB Acc@5m is 78.915/60.510% for CC and 83.562/70.313% for Uni (Same/Cross), exceeding the corresponding Mean rows. Mean was not separately trained. See Sec. 3.1 and Appendix D.3.
Cross-label clarification. We use the SliceMatch-corrected labels adopted by CCVPE. Our audit identified a historical Cross evaluation path that still read legacy test GT. Current training and evaluation explicitly bind the corrected labels. With the historical checkpoint fixed, Cross median changed from 2.714 m in the submission to 2.6697 m under the current evaluation.
Q2: interpretation of the original split-dependent result. Independent training already provided substantial Same-area gains. The old A-versus-C comparison changed training composition, test references and readout together; it did not isolate an interaction-induced generalization effect. The revised claim therefore concerns geographic inputs together with training and response processing. Separately, with identical natural K=1 references and DARK, RGB-trained CCVPE improves Acc@5m from 69.946% to 71.082% on Same and 49.537% to 50.184% on Cross: adaptation itself contributes. Fixed-weight member-budget tests and loss/readout analyses distinguish additional effects in Appendices E.5-E.6 and Section 4.3/5.2.
Response 2/4: Stronger baselines, UnifyGeo, and measured computational cost
Your suggestion is valuable for strengthening the comparison and separating the sources of improvement.
W2 and Suggestion 2: stronger complete-system baselines.
We added Sample4Geo+HC-Net, +FG² and +Loc², and native UnifyGeo with official retrieval and reranking. The Sample4Geo cascades receive the same retrieved Top-1; UnifyGeo retains its own retrieval path. The following complete retrieval-localization results use corrected labels (Sec. 4.2):
| Method | Same: Acc@1 / @5 / @10m | Cross: Acc@1 / @5 / @10m |
|---|---|---|
| Sample4Geo+CCVPE, DARK | 31.681 / 75.909 / 83.745 | 20.840 / 60.787 / 66.337 |
| GeoHypLoc (S4G+CC) | 37.118 / 80.058 / 86.603 | 21.854 / 63.294 / 68.019 |
| Sample4Geo+HC-Net | 38.591 / 81.346 / 86.593 | 21.349 / 65.711 / 69.257 |
| Sample4Geo+FG², no RANSAC | 39.061 / 82.673 / 89.128 | 23.064 / 66.609 / 70.781 |
| Sample4Geo+Loc², no RANSAC | 20.966 / 74.587 / 85.733 | 14.075 / 62.289 / 69.277 |
| Native UnifyGeo | 40.797 / 83.604 / 88.328 | 26.424 / 70.501 / 72.643 |
| GeoHypLoc (Uni) | 42.327 / 83.767 / 87.967 | 27.484 / 70.311 / 72.358 |
Accuracies are percentages; GeoHypLoc rows are three-seed means. Loc² excludes 2/4 failed Same/Cross queries (N=52,603/53,690); other rows use 52,605/53,694 queries. Baselines use released weights, not matched E3 fine-tuning. The direct-cascade improvement motivates applying geographic organization within the stronger UnifyGeo pipeline.
Q3: what is added beyond UnifyGeo?
UnifyGeo already uses retrieval and fine matching together and reranks candidates. We retain this capability: official global retrieval -> official reranking -> H* selection -> geographically organized RGB localization. Our additional step uses independently georeferenced candidate footprints to form one localization observation in a common geographic coordinate system, rather than passing the reranked first reference alone to localization. Its native four-stage localization path is adapted to this geographic input, with the training constraints and response processing in Secs. 3.2–3.3.
Relative to native UnifyGeo, Same/Cross Acc@1m increases by 1.530/1.060 percentage points and median error falls from 1.235/1.768 m to 1.193/1.714 m. Acc@10m decreases by 0.361/0.286 points. These gains support the design goal of improving fine localization precision. The small loss-ablation differences are reported separately in Section 4.3.
W2: is the improvement worth the additional computation?
We replaced concurrent-run estimates with isolated measurements on one RTX 4090, using 258 fixed queries per split, warmup, repeated measurements and matched batching within each backbone. Entries below are single-reference -> RGB:
| Backbone / split | Serial localization (ms/query) | Peak PyTorch allocated (GiB) |
|---|---|---|
| CCVPE / Same | 47.915 -> 87.340 | 0.385 -> 1.108 |
| CCVPE / Cross | 46.963 -> 77.200 | 0.385 -> 1.030 |
| UnifyGeo / Same | 30.295 -> 49.120 | 0.311 -> 0.516 |
| UnifyGeo / Cross | 29.582 -> 44.223 | 0.311 -> 0.480 |
Serial localization includes warm-cache image processing, device transfer, model computation and coordinate readback. It starts from cached candidates and excludes full-gallery retrieval and reranking. RGB/single-reference serial-time ratios are 1.823/1.644 for CCVPE and 1.621/1.495 for UnifyGeo. CUDA-synchronized forward-only ratios are higher: 3.246/3.127 and 2.279/2.196, respectively. Allocated memory is not total GPU-process memory. Sampled process peaks are 1.164 GiB for CCVPE Top-1 versus 4.297/3.512 GiB for RGB (Same/Cross), and 0.795 GiB for UnifyGeo Top-1 versus 1.316/1.213 GiB for RGB. Appendix F also reports reserved-memory peaks.
Overview: revised geographic input, method and manuscript organization
Thank you especially for suggesting final-response fusion and RGB stitching as comparison methods. Your suggestion directly prompted us to reconsider the central contribution: moving from retrieved Top-1 selection and reranking to organizing fine-localization observations through geographic associations among candidates. We conducted the additional experiments, adopted geographically composed RGB input as the main implementation, and revised the method and experimental sections accordingly. The revised method and principal changes are summarized below.
GeoHypLoc uses the geographic relationships among retrieved aerial references to organize the observations supplied to a fine-grained localizer. (i) From the retrieved Top-5 candidates, we use the full-gallery geographic RNG and query-specific visual support to select a spatially coherent reference set H*. (ii) Each reference has its own georeferencing. We resample its RGB observations onto a common geographic canvas, preserving their relative positions and ground sampling scale. At overlapping locations, valid RGB observations are averaged; singly covered locations retain the available observation, and a coverage mask identifies valid support. This geographically composed RGB image and the ground query form one localization sample. (iii) We retain the native coarse-to-fine localization backbone and its basic supervision, add geographic peak and continuous-coordinate objectives for training, and combine regional query visual support with localization evidence to correct the response before continuous coordinate readout.
The geographic peak objective distinguishes support within 1 m of the true position from competing responses beyond 3 m. We implement this formulation with Sample4Geo + CCVPE and with UnifyGeo; the latter retains official retrieval and reranking before reference-set selection.
The revised Section 3.1 describes reference-set selection and geographic input construction; Section 3.2 presents the native localizers and training objectives; Section 3.3 describes response correction and coordinate readout. Section 4 reports the main results, and Section 5 analyzes reference composition, geographic coverage and response correction. Loss ablations are provided in Section 4.3. The original Full interaction implementation, which aligns and exchanges per-reference responses and states during localization, is retained as an alternative implementation in the appendix, together with comparisons against RGB input and final-response Mean fusion.
We also corrected the historical Cross test-ground-truth loading path to use the SliceMatch-corrected labels adopted by CCVPE.