Browse State-of-the-Art › Lane Detection

Lane Detection

103 papers with code · 13 benchmarks · 17 datasets archive 2025-07-28

Computer Vision

Lane Detection is a computer vision task that involves identifying the boundaries of driving lanes in a video or image of a road scene. The goal is to accurately locate and track the lane markings in real-time, even in challenging conditions such as poor lighting, glare, or complex road layouts.

Lane detection is an important component of advanced driver assistance systems (ADAS) and autonomous vehicles, as it provides information about the road layout and the position of the vehicle within the lane, which is crucial for navigation and safety. The algorithms typically use a combination of computer vision techniques, such as edge detection, color filtering, and Hough transforms, to identify and track the lane markings in a road scene.

( Image credit: End-to-end Lane Detection )

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

13 leaderboard tables shown for this task, 13 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 13 until expanded.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
CULane (63 rows) DLNet DLNet: Direction-Aware Feature Integration for Robust Lane... code — Compare
TuSimple (43 rows) SCNN_UNet_Attention_PL* Robust Lane Detection through Self Pre-training with Masked... — — Compare
CurveLanes (19 rows) CondLSTR (ResNet-101) Generating Dynamic Kernels via Transformers for Lane Detection code — Compare
BDD100K val (11 rows) TwinLiteNetPlus-Large TwinLiteNetPlus: A Stronger Model for Real-time Drivable Area and... code — Compare
LLAMAS (10 rows) CLRNet (DLA-34) CLRNet: Cross Layer Refinement Network for Lane Detection code Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified Compare
nuScenes (3 rows) DSLP Learning to Predict Navigational Patterns from Partial Observations code — Compare
OpenLane (3 rows) CondLSTR (ResNet-18) Generating Dynamic Kernels via Transformers for Lane Detection code — Compare
Caltech Lanes Cordova (2 rows) VPGNet VPGNet: Vanishing Point Guided Network for Lane and Road Marking... code Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified Compare
Caltech Lanes Washington (2 rows) VPGNet VPGNet: Vanishing Point Guided Network for Lane and Road Marking... code Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified Compare
DET (1 row) LDNet LDNet: End-to-End Lane Marking Detection Approach Using a Dynamic... code — Compare
K-Lane (1 row) LLDN-GFC K-Lane: Lidar Lane Dataset and Benchmark for Urban Roads and Highways code Syntology official (archive's flag): 3 ran · 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 2 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified Compare
OpenLane-V2 val (1 row) TopoLogic TopoLogic: An Interpretable Pipeline for Lane Topology Reasoning... code — Compare
tvtLane (1 row) SCNN_UNet_Attention_PL* Robust Lane Detection through Self Pre-training with Masked... — — 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

17 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.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 251 · with a code link: 103 · where Syntology ran a sample: 29 (28 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (29 of 251 tagged: 28 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument)

Page 1 of 3: papers 1 to 100 of 251, 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 30 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