Papers › SCORE: Scene Context Matters in Open-Vocabulary Remote Sensing Instance Segmentation

SCORE: Scene Context Matters in Open-Vocabulary Remote Sensing Instance Segmentation

17 Jul 2025arXiv:2507.12857archive 2025-07-28

Shiqi Huang, Shuting He, Huaiyuan Qin, Bihan Wen

Most existing remote sensing instance segmentation approaches are designed for close-vocabulary prediction, limiting their ability to recognize novel categories or generalize across datasets. This restricts their applicability in diverse Earth observation scenarios. To address this, we introduce open-vocabulary (OV) learning for remote sensing instance segmentation. While current OV segmentation models perform well on natural image datasets, their direct application to remote sensing faces challenges such as diverse landscapes, seasonal variations, and the presence of small or ambiguous objects in aerial imagery. To overcome these challenges, we propose SCORE (Scene Context matters in Open-vocabulary REmote sensing instance segmentation), a framework that integrates multi-granularity scene context, i.e., regional context and global context, to enhance both visual and textual representations. Specifically, we introduce Region-Aware Integration, which refines class embeddings with regional context to improve object distinguishability. Additionally, we propose Global Context Adaptation, which enriches naive text embeddings with remote sensing global context, creating a more adaptable and expressive linguistic latent space for the classifier. We establish new benchmarks for OV remote sensing instance segmentation across diverse datasets. Experimental results demonstrate that, our proposed method achieves SOTA performance, which provides a robust solution for large-scale, real-world geospatial analysis. Our code is available at https://github.com/HuangShiqi128/SCORE.

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

HuangShiqi128/SCORE found in paper text by SyntologyApache-2.0Syntology: 9 samples, 8 ran (6 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

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

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

Licence: 0 of the 9 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 HuangShiqi128/SCORE. “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.

HuangShiqi128/SCORE found in paper text by Syntology 9 samples, 8 ran (6 instrument-failed) · 1 unverified
batch_dice_loss in 60 papers score/modeling/matcher.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · bc2cb481a75c370d · report fixture: signature inputs:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-25
bbox_overlaps in 20 papers score/evaluation/ins_seg_evaluation_gzero_utils/bbox_overlaps.py ran Apache-2.0 (permissive) · ff38c0c0ab1871da · report fixture: signature bboxes1:ndarray/2/int, bboxes2:ndarray/2/int, mode:str/0/str · returned ndarray · level recorded 2026-09-25
calculate_uncertainty in 37 papers score/modeling/criterion.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · 2dcb8123d89bb1ff · report fixture: signature logits:Tensor/4/float · returned Tensor · level recorded 2026-09-25
dice_loss in 193 papers
census: 10 implementations from 16 papers, 7 distinct outputs across 4 buckets, one shared input per bucket
score/modeling/criterion.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 89f75e54ff128be0 · report fixture: signature inputs:Tensor/2/float, targets:Tensor/2/float, num_masks:float/0/float · returned Tensor · level recorded 2026-09-25
nested_tensor_from_tensor_list in 60 papers score/utils/misc.py ran · our draft was wrong Apache-2.0 (permissive) · 58cc9ff3bf75e753 · report fixture: signature tensor_list:list/1/Tensor · returned NestedTensor · level recorded 2026-09-25
set_recall_param score/evaluation/ins_seg_evaluation_gzero_utils/recall.py ran · violated contract Apache-2.0 (permissive) · e41f7604e432c210 · report fixture: signature proposal_nums:list/1/int, iou_thrs:list/1/float · returned tuple · level recorded 2026-09-25
sigmoid_ce_loss in 70 papers
census: 4 implementations from 8 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
score/modeling/criterion.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · d0c61e8dba511aa3 · report fixture: signature inputs:Tensor/2/float, targets:Tensor/2/float, num_masks:float/0/float · returned Tensor · level recorded 2026-09-25
xyxy2xywh in 19 papers score/evaluation/ins_seg_evaluation_gzero_utils/coco_utils.py ran · our draft was wrong Apache-2.0 (permissive) · 141b13358e6b0894 · report fixture: signature bbox:Tensor/1/float · returned list · level recorded 2026-09-25
batch_sigmoid_ce_loss in 48 papers score/modeling/matcher.py unverified Apache-2.0 (permissive) · 1edd24985036b0bf · report

Tasks

Earth ObservationInstance SegmentationSegmentationSemantic Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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