Browse State-of-the-Art › Reading Order Detection
Reading Order Detection
4 papers with code · 2 benchmarks · 3 datasets archive 2025-07-28
Reading order detection aims to capture the word sequence which can be naturally comprehended by human readers from visually-rich documents. It is a fundamental task for visually-rich document understanding.
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
2 leaderboard tables shown for this task, 2 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.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| ROOR (4 rows) | LayoutLMv3-GlobalPointer (large) | Modeling Layout Reading Order as Ordering Relations for... | code | — | Compare |
| ReadingBank (2 rows) | TPP (LayoutMask) | Reading Order Matters: Information Extraction from Visually-rich... | code | — | Compare |
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
3 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Papers archive 2025-07-28
archive papers tagged: 6 · with a code link: 4 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 6 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 6 of 6, 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.
-
17 Oct 2023 2 repositories listedHowever, BIO-tagging scheme relies on the correct order of model inputs, which is not guaranteed in real-world NER on scanned VrDs where text are recognized and arranged by OCR systems.
-
1 Jun 2025 1 repository listedAutomated parsing of scanned documents into richly structured, machine-readable formats remains a critical bottleneck in Document AI, as traditional multi-stage pipelines suffer from error propagation and limited…
-
29 Sep 2024 1 repository listedHowever, we argue that this formulation does not adequately convey the complete reading order information in the layout, which may potentially lead to performance decline in downstream VrD tasks.
-
26 Aug 2021 1 repository listedReading order detection is the cornerstone to understanding visually-rich documents (e. g., receipts and forms).
-
LayerDoc: Layer-wise Extraction of Spatial Hierarchical Structure in Visually-Rich Documents7 Jan 2023 0 repositories listedDigital documents often contain images and scanned text.
-
Relational Representation Learning in Visually-Rich Documents5 May 2022 0 repositories listedRelational understanding is critical for a number of visually-rich documents (VRDs) understanding tasks.
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