Papers › UASTHN: Uncertainty-Aware Deep Homography Estimation for UAV Satellite-Thermal Geo-localization

UASTHN: Uncertainty-Aware Deep Homography Estimation for UAV Satellite-Thermal Geo-localization

3 Feb 2025arXiv:2502.01035archive 2025-07-28

Jiuhong Xiao, Giuseppe Loianno

Geo-localization is an essential component of Unmanned Aerial Vehicle (UAV) navigation systems to ensure precise absolute self-localization in outdoor environments. To address the challenges of GPS signal interruptions or low illumination, Thermal Geo-localization (TG) employs aerial thermal imagery to align with reference satellite maps to accurately determine the UAV's location. However, existing TG methods lack uncertainty measurement in their outputs, compromising system robustness in the presence of textureless or corrupted thermal images, self-similar or outdated satellite maps, geometric noises, or thermal images exceeding satellite maps. To overcome these limitations, this paper presents UASTHN, a novel approach for Uncertainty Estimation (UE) in Deep Homography Estimation (DHE) tasks for TG applications. Specifically, we introduce a novel Crop-based Test-Time Augmentation (CropTTA) strategy, which leverages the homography consensus of cropped image views to effectively measure data uncertainty. This approach is complemented by Deep Ensembles (DE) employed for model uncertainty, offering comparable performance with improved efficiency and seamless integration with any DHE model. Extensive experiments across multiple DHE models demonstrate the effectiveness and efficiency of CropTTA in TG applications. Analysis of detected failure cases underscores the improved reliability of CropTTA under challenging conditions. Finally, we demonstrate the capability of combining CropTTA and DE for a comprehensive assessment of both data and model uncertainty. Our research provides profound insights into the broader intersection of localization and uncertainty estimation. The code and models are publicly available.

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

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

arplaboratory/UASTHN officialmentioned on GitHubpytorchMITSyntology: 8 samples, 8 ran (3 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

8 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 3 honoured, 0 violated, 2 with no contract checked; 3 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

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

Licence: 0 of the 8 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 arplaboratory/UASTHN. “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.

arplaboratory/UASTHN official repository 8 samples, 8 ran (3 instrument-failed) · 0 unverified
calc_overlap global_pipeline/h5_transformer.py ran; the contract check could not run (RAISES) MIT (permissive) · 44bf5ced04fc8132 · report fixture: signature database_region:list/1/int, query_region:list/1/int · returned list · level recorded 2026-09-24
collate_fn in 500 papers global_pipeline/datasets_ws.py ran · our draft was wrong MIT (permissive) · 247429ce34fc3671 · report fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-24
load_and_preprocess_satellite UASTHN_demo.py ran · honoured contract MIT (permissive) · 2d86f6c4f9c9d299 · report fixture: signature image_path:str/0/str, database_size:int/0/int · returned Tensor · level recorded 2026-09-24
load_and_preprocess_thermal UASTHN_demo.py ran · honoured contract MIT (permissive) · 2ed2d9477dedd236 · report fixture: signature image_path:str/0/str, resize_width:int/0/int · returned Tensor · level recorded 2026-09-24
mac in 8 papers global_pipeline/model/functional.py ran · our draft was wrong fingerprinted MIT (permissive) · 0b387e5979c78d55 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-24
path_to_pil_img in 10 papers global_pipeline/datasets_ws.py ran · honoured contract MIT (permissive) · f0db6d80ebf12bfa · report fixture: signature path:str/0/str · returned Image · level recorded 2026-09-25
sare_ind global_pipeline/model/functional.py ran fingerprinted MIT (permissive) · 463b2f96158e03a8 · report fixture: signature query:Tensor/2/float, positive:Tensor/2/float, negative:Tensor/2/float · returned Tensor · level recorded 2026-09-24
sare_joint global_pipeline/model/functional.py ran fingerprinted MIT (permissive) · d15fdc91eec37e29 · report fixture: signature query:Tensor/2/float, positive:Tensor/2/float, negatives:Tensor/2/float · returned Tensor · level recorded 2026-09-24

Tasks

Homography EstimationUncertainty Quantificationgeo-localization

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ALIGNDeep EnsemblesGPS

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