TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0767Certified recordPeer-reviewed

Efficient video-based traffic conflict prediction and interpretable risk analysis at signalized intersections via deep learning

Objectives To achieve accurate and real-time prediction of traffic conflicts at signalized intersections and identify their key contributing factors, thereby supporting proactive safety management and reducing accident risks. Methods This study proposes a novel multi-stage traffic-conflict prediction framework that integrates a real-time video image processing system and an advanced conflict-prediction model. Specifically, a real-time video analysis system integrating the YOLOv8 object detection framework and th…

Policy · G Space — documented gain · certified 2026-08-15 · v1 · article view · machine-readable

Current reading — gain

A multi-stage framework integrating YOLOv8 detection, OC-SORT tracking, dynamic CROI filtering, and ST-GAT prediction enables accurate real-time traffic-conflict prediction at signalized intersections to enhance safety and mitigate accident risks.

What this doesn’t fix

Evaluation is limited to field video data from a single representative signalized intersection in Nanning, China, which constrains generalizability to other intersection designs, traffic mixes, and environmental conditions.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0767, v1: “Efficient video-based traffic conflict prediction and interpretable risk analysis at signalized intersections via deep learning.” Truvace, 2026-08-15. /record/TRV-2026-0767 (accessed at citation time). sha256 661a88c277ec56fa

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1661a88c277ec

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0767 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.