Browse State-of-the-Art › Change Detection

Change Detection

369 papers with code · 17 benchmarks · 20 datasets archive 2025-07-28

Computer Vision

Change Detection is a computer vision task that involves detecting changes in an image or video sequence over time. The goal is to identify areas in the image or video that have undergone changes, such as appearance changes, object disappearance or appearance, or even changes in the scene's background.

Image credit: "A TRANSFORMER-BASED SIAMESE NETWORK FOR CHANGE DETECTION"

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

18 leaderboard tables shown for this task, 17 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted. 10 shown of 18 until expanded.

Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): LEVIR-CD (1 judged, 0 placed), WHU-CD (1 judged, 0 placed), S2Looking (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
LEVIR-CD (28 rows) SChanger-base SChanger: Change Detection from a Semantic Change and Spatial... code — Compare
WHU-CD (22 rows) CLAFA-LWGANet L2 LWGANet: A Lightweight Group Attention Backbone for Remote Sensing... code — Compare
CDD Dataset (season-varying) (18 rows) P2V-CD Transition Is a Process: Pair-to-Video Change Detection Networks... code — Compare
SYSU-CD (12 rows) SChanger-small SChanger: Change Detection from a Semantic Change and Spatial... code — Compare
S2Looking (11 rows) SChanger-base SChanger: Change Detection from a Semantic Change and Spatial... code — Compare
DSIFN-CD (9 rows) DDPM-CD DDPM-CD: Denoising Diffusion Probabilistic Models as Feature... code Syntology official (archive's flag): 11 ran · 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 2 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 2 unverified Compare
LEVIR+ (9 rows) ChangeMamba ChangeMamba: Remote Sensing Change Detection With Spatiotemporal... code Syntology official (archive's flag): 5 ran · 5 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; 3 where Syntology's instrument failed) · 4 unverified Compare
WHU Building Dataset (7 rows) IMP+MTP(InternImage-XL) MTP: Advancing Remote Sensing Foundation Model via Multi-Task Pretraining code Syntology official (archive's flag): 1 ran · 5 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; 3 where Syntology's instrument failed) · 0 unverified Compare
OSCD - 13ch (6 rows) FC-Siam-Diff Fully Convolutional Siamese Networks for Change Detection code — Compare
OSCD - 3ch (6 rows) MAE+MTP(ViT-L+RVSA) MTP: Advancing Remote Sensing Foundation Model via Multi-Task Pretraining code Syntology official (archive's flag): 1 ran · 5 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; 3 where Syntology's instrument failed) · 0 unverified Compare
GoogleGZ-CD (4 rows) C2FNet C2F-SemiCD: A Coarse-to-Fine Semi-Supervised Change Detection... code — Compare
GVLM (4 rows) BTC Be the Change You Want to See: Revisiting Remote Sensing Change... code — Compare
CLCD (3 rows) BTC Be the Change You Want to See: Revisiting Remote Sensing Change... code — Compare
EGY-BCD (3 rows) MTP (VIT-B+RVSA) MTP: Advancing Remote Sensing Foundation Model via Multi-Task Pretraining code Syntology official (archive's flag): 1 ran · 5 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; 3 where Syntology's instrument failed) · 0 unverified Compare
SECOND (2 rows) ChangeMamba ChangeMamba: Remote Sensing Change Detection With Spatiotemporal... code Syntology official (archive's flag): 5 ran · 5 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; 3 where Syntology's instrument failed) · 4 unverified Compare
ChangeSim (1 row) C-3PO How to Reduce Change Detection to Semantic Segmentation code Syntology official (archive's flag): 10 ran · 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified Compare
PCD (1 row) C-3PO How to Reduce Change Detection to Semantic Segmentation code Syntology official (archive's flag): 10 ran · 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified Compare
Brazilian Amazon (2020–2021) (0 rows) no rows in the archive — —

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

20 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

1 subtask in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 919 · with a code link: 369 · where Syntology ran a sample: 47 (40 with a run with no instrument failure, 7 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (47 of 919 tagged: 40 with a run with no instrument failure, 7 where every run was a failure of Syntology's instrument)

Page 1 of 10: papers 1 to 100 of 919, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 20 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

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