Papers › Where in the World is this Image? Transformer-based Geo-localization in the Wild

Where in the World is this Image? Transformer-based Geo-localization in the Wild

29 Apr 2022arXiv:2204.13861archive 2025-07-28

Shraman Pramanick, Ewa M. Nowara, Joshua Gleason, Carlos D. Castillo, Rama Chellappa

Predicting the geographic location (geo-localization) from a single ground-level RGB image taken anywhere in the world is a very challenging problem. The challenges include huge diversity of images due to different environmental scenarios, drastic variation in the appearance of the same location depending on the time of the day, weather, season, and more importantly, the prediction is made from a single image possibly having only a few geo-locating cues. For these reasons, most existing works are restricted to specific cities, imagery, or worldwide landmarks. In this work, we focus on developing an efficient solution to planet-scale single-image geo-localization. To this end, we propose TransLocator, a unified dual-branch transformer network that attends to tiny details over the entire image and produces robust feature representation under extreme appearance variations. TransLocator takes an RGB image and its semantic segmentation map as inputs, interacts between its two parallel branches after each transformer layer, and simultaneously performs geo-localization and scene recognition in a multi-task fashion. We evaluate TransLocator on four benchmark datasets - Im2GPS, Im2GPS3k, YFCC4k, YFCC26k and obtain 5.5%, 14.1%, 4.9%, 9.9% continent-level accuracy improvement over the state-of-the-art. TransLocator is also validated on real-world test images and found to be more effective than previous methods.

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 1 code sample harvested from 1 repository linked to this paper: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

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

shramanpramanick/transformer_based_geo-localization officialmentioned in paperpytorchMITSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 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

1 sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 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

Licence: 0 of the 1 sample 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 shramanpramanick/transformer_based_geo-localization. “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.

shramanpramanick/transformer_based_geo-localization official repository 1 sample, 1 ran (0 instrument-failed) · 0 unverified
topk_accuracy in 14 papers experiment_codes/ViT_RGB_train.py ran MIT (permissive) · 374dfca88d741d74 · report fixture: signature target:ndarray/1/int, output:ndarray/2/float, k:int/0/int · returned float64 · level recorded 2026-09-24

Tasks

DiversityPhoto geolocation estimationScene RecognitionSemantic Segmentationgeo-localization

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Photo geolocation estimation GWS15k Translocator City level (25 km) 1.1 #4 of 5 Archive leaderboard report
Photo geolocation estimation GWS15k Translocator Continent level (2500 km) 48.3 #4 of 5 Archive leaderboard report
Photo geolocation estimation GWS15k Translocator Country level (750 km) 25.5 #4 of 5 Archive leaderboard report
Photo geolocation estimation GWS15k Translocator Region level (200 km) 8.0 #4 of 5 Archive leaderboard report
Photo geolocation estimation GWS15k Translocator Street level (1 km) 0.5 #4 of 5 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator City level (25 km) 31.1 #5 of 14 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator Continent level (2500 km) 80.1 #5 of 14 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator Country level (750 km) 58.9 #5 of 14 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator Region level (200 km) 46.7 #5 of 14 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator Street level (1 km) 11.8 #5 of 14 Archive leaderboard report
Photo geolocation estimation Im2GPS3k Translocator Training Images 4.7M #5 of 14 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator City level (25 km) 17.8 #4 of 6 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator Continent level (2500 km) 60.6 #4 of 6 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator Country level (750 km) 41.3 #4 of 6 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator Region level (200 km) 28.0 #4 of 6 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator Street level (1 km) 7.2 #4 of 6 Archive leaderboard report
Photo geolocation estimation YFCC26k Translocator Training Images 4.7M #4 of 6 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