Papers › Learning RoI Transformer for Detecting Oriented Objects in Aerial Images

Learning RoI Transformer for Detecting Oriented Objects in Aerial Images

1 Dec 2018arXiv:1812.00155archive 2025-07-28

Jian Ding, Nan Xue, Yang Long, Gui-Song Xia, Qikai Lu

Object detection in aerial images is an active yet challenging task in computer vision because of the birdview perspective, the highly complex backgrounds, and the variant appearances of objects. Especially when detecting densely packed objects in aerial images, methods relying on horizontal proposals for common object detection often introduce mismatches between the Region of Interests (RoIs) and objects. This leads to the common misalignment between the final object classification confidence and localization accuracy. Although rotated anchors have been used to tackle this problem, the design of them always multiplies the number of anchors and dramatically increases the computational complexity. In this paper, we propose a RoI Transformer to address these problems. More precisely, to improve the quality of region proposals, we first designed a Rotated RoI (RRoI) learner to transform a Horizontal Region of Interest (HRoI) into a Rotated Region of Interest (RRoI). Based on the RRoIs, we then proposed a Rotated Position Sensitive RoI Align (RPS-RoI-Align) module to extract rotation-invariant features from them for boosting subsequent classification and regression. Our RoI Transformer is with light weight and can be easily embedded into detectors for oriented object detection. A simple implementation of the RoI Transformer has achieved state-of-the-art performances on two common and challenging aerial datasets, i.e., DOTA and HRSC2016, with a neglectable reduction to detection speed. Our RoI Transformer exceeds the deformable Position Sensitive RoI pooling when oriented bounding-box annotations are available. Extensive experiments have also validated the flexibility and effectiveness of our RoI Transformer. The results demonstrate that it can be easily integrated with other detector architectures and significantly improve the performances.

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 11 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 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: community (archive-listed): 11 samples from 1 repository, 10 ran (5 with no instrument failure; 5 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

dingjiansw101/RoITransformer_DOTA mentioned on GitHubmxnetMITSyntology: 11 samples, 10 ran (5 instrument-failed) · 1 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

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

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

Licence: 11 of the 11 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 dingjiansw101/RoITransformer_DOTA. “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.

dingjiansw101/RoITransformer_DOTA community (archive-listed) 11 samples, 10 ran (5 instrument-failed) · 1 unverified
GetFileFromThisRootDir dota_kit/dota_utils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · dd71e1e52b5d28fb · report fixture: signature dir:str/0/str, ext:list/1/str · returned list · level recorded 2026-09-26
TuplePoly2Poly dota_kit/dota_utils.py ran MIT recorded; this copy not marked cleared · pointer only · 2b316d21aea8f5d2 · report fixture: signature poly:list/1/list · returned list · level recorded 2026-09-26
cal_line_length dota_kit/ImgSplit.py ran · our draft was wrong fingerprinted MIT recorded; this copy not marked cleared · pointer only · 334c71c1848e108a · report fixture: signature point1:tuple/1/float, point2:tuple/1/float · returned float · level recorded 2026-09-22
choose_best_pointorder_fit_another dota_kit/ImgSplit.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT recorded; this copy not marked cleared · pointer only · 787051d64e55a326 · report fixture: signature poly1:ndarray/1/float, poly2:ndarray/1/float · returned ndarray · level recorded 2026-09-22
custombasename dota_kit/dota_utils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 7d7ac32f4cdc59c0 · report fixture: signature fullname:str/0/str · returned str · level recorded 2026-09-26
parse_gt in 7 papers dota_kit/dota_evaluation_task1.py ran · our draft was wrong MIT recorded; this copy not marked cleared · pointer only · 0f59174083876439 · report fixture: signature filename:str/0/str · returned list · level recorded 2026-09-22
parse_gt in 7 papers dota_kit/dota_evaluation_task2.py ran MIT recorded; this copy not marked cleared · pointer only · 8e139e53cdf13750 · report fixture: signature filename:str/0/str · returned list · level recorded 2026-09-26
py_cpu_nms in 13 papers dota_kit/ResultMerge.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT recorded; this copy not marked cleared · pointer only · 5502a789c2da0e5e · report fixture: signature dets:ndarray/2/float, thresh:float/0/float · returned list · level recorded 2026-09-22
voc_ap in 44 papers
census: 5 implementations from 10 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind float, dtype float64 · arg 2: rank 1, kind float, dtype float64
dota_kit/dota_evaluation_task1.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT recorded; this copy not marked cleared · pointer only · 95c31c78be42f723 · report fixture: signature rec:ndarray/1/float, prec:ndarray/1/float, use_07_metric:bool/0/bool · returned float64 · level recorded 2026-09-22
voc_eval in 19 papers dota_kit/dota_evaluation_task2.py ran MIT recorded; this copy not marked cleared · pointer only · 4e5a4521cdd33b64 · report fixture: signature detpath:str/0/str, annopath:str/0/str, imagesetfile:str/0/str, classname:str/0/str, ovthresh:float/0/float, use_07_metric:bool/0/bool · returned tuple · level recorded 2026-09-26
iou_poly dota_kit/polyiou.py unverified MIT recorded; this copy not marked cleared · pointer only · 187d78f33372a950 · report

Tasks

General ClassificationObjectObject DetectionObject Detection In Aerial ImagesOriented Object Detectionobject-detection

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Object Detection In Aerial Images DOTA RoI Transformer mAP 69.56% #54 of 58 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

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerReLUResidual ConnectionSoftmaxTransformer

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