Source-linked AI summary
Smartphone-Based Method for Automated Speed Enforcement
Keya Li, Jahnavi Malagavalli, Lamha Goel, Tong Wang, Kara M. Kockelman
TL;DR
Fixed speed cameras are costly to deploy across all road segments, and enforcement agencies face constraints in identifying violators. This paper tests a smartphone-video computer-vision pipeline for speed estimation and vehicle identification, with performance varying substantially across tasks. The results report limited accuracy for speed and plate recognition alongside higher reported color and make accuracy.
Problem
Fixed speed cameras are expensive to purchase and maintain, limiting deployment across road segments, while agencies have limited resources to identify violators and issue tickets on-site.
Source: §1 · pp. 2–3Method
The paper builds a smartphone-video pipeline combining speed inference with automated license-plate, color, make, and model identification.
Source: §1 · p. 3, §3.3 · p. 7Results
Performance varied by task: 16.33% speed-estimation accuracy within a 20% error range, 29.70% plate recognition, and up to 60.81% color and 48.65% make accuracy.
Source: §6 · p. 13Takeaways & Limitations
The study presents smartphone-based computer vision as a potentially practical supplement for automated speed enforcement and vehicle identification.
Source: §5 · p. 12, §6 · p. 13The study calls for testing nighttime and moving-camera scenarios and exploring scalability in dense observation environments.
Source: §6 · p. 13
Abstract
from arXiv · showhide
Smartphone cameras and computer vision (CV) hold significant promise in assisting public agencies with enforcing traffic laws and enhancing road safety. This work designs and tests a smartphone-based method for automated speed estimation and vehicle identification (license plate, make/model, and color recognition) via an automated pipeline to assist enforcement agencies in reliably identifying speeders. The CV code accurately recognizes nearly half (46%) of the license plates' text on 1,800 images from a Brazil open-source dataset, called UFPR-ALPR. Code tests on daytime recordings from hand-held smartphone videos (n = 73) and roadside cameras (n = 42) in Austin, Texas yield 60.8% accuracy for color detection (among all possible RGB color categories), 48.6% on vehicle make/manufacturer identification, and 16.89% on vehicle make and model identification. Prediction accuracy for speed estimation (within a 20% range), vehicle make (within the top 3 predictions), and license plate recognition (within the top 10 predictions) are 16.3%, 16.9%, and 29.7%, respectively. This paper also illuminates the legal, technological, and practical aspects of using smartphones for enforcement, including the potential use of recordings for enforcement purposes, emphasizing the need to transform the potential of smartphone-based CV technologies into practical tools for vital information on traffic violations.
1. INTRODUCTION
Road crashes and speeding deaths motivate stronger enforcement, but expensive fixed cameras cannot cover every road segment. The paper proposes smartphone video and computer vision as a lower-cost way to identify speeding vehicles and report information to agencies.
1. INTRODUCTION
- 28.7% of U.S. traffic fatalities in 2021 were related to speeding, while real-time enforcement by police is difficult and costly.Automated speed enforcement and other countermeasures are increasingly used, but remain rare in the U.S.Source: §1 · p. 2
- As of July 2024, 19 U.S. states and the District of Columbia permitted speed cameras, while 247 U.S. communities had speed safety programs.At fixed NYC camera locations, speeding had dropped an average of 73 percent in school zones by December 2021.Source: §1 · pp. 2–3, Figure 1 · p. 3
- According to New York City’s Independent Budget Office (2016), stationary-camera costs averaged roughly $120,000 for hardware plus installation and over $150,000 for five years of operation and maintenance, making coverage of all road segments unaffordable for cities and states.Source: §1 · p. 3
- The paper designs a smartphone-based system for speed inference and automated vehicle identification, reporting speed, license plate, color, make, and model to enforcement agencies.The paper also outlines prior work, methods, Austin application results, survey findings, and future work.Source: §1 · p. 3
2. SYNTHESIS OF RELATED WORK
Prior work describes computer-vision methods for estimating speeds and identifying vehicles, while noting that mobile-phone recordings remain insufficiently validated. Vehicle identification can combine plate recognition with vehicle attributes when plates are unreadable.
2.1 Speed Inference
- Speed-estimation methods use video, detection and tracking, scaled travel distance, and frame intervals; camera calibration, often using vanishing points, maps image coordinates to the world.The reviewed calibration methods were developed for fixed traffic cameras and require further analysis for mobile cameras.Source: §2.1 · p. 4
2.2 Vehicle Identification
- Vehicle detection includes one-stage and two-stage approaches, while DeepSort associates detections across frames using velocity and appearance to predict vehicle positions.YOLOv7 was reported to outperform two-stage detectors in both time and accuracy in one cited study.Source: §2.2 · pp. 4–5
- Automatic license plate recognition localizes a plate, segments characters, and recognizes text, but its accuracy and applicability had not been validated for mobile-phone video recordings.Poor image quality and low-resolution cameras hinder plate recognition.Source: §2.2 · p. 5
- When plates are illegible, vehicle color, make, and model can help narrow identification possibilities; general-phone-camera make/model recognition systems were not available in the reviewed work.The cited limitations include darkness, occlusion, fake or missing plates, lens quality, and zoom level.Source: §2.2 · p. 5
3. VEHICLE SPEED DETECTION AND IDENTIFICATION
The method estimates speed from vehicle motion and vanishing points, then uses a multi-stage computer-vision pipeline to identify plates and vehicle attributes. It assumes phones are held still during recording.
3. VEHICLE SPEED DETECTION AND IDENTIFICATION
- The method assumes phones remain still while recording, so inclination and phone movement can be neglected across the short frame-by-frame intervals.Source: §3 · p. 6
3.1 Obtaining VPs and Estimating Speeds
- Vehicle speed is estimated by scaling bounding-box displacement between frames by an assumed 4.5-meter passenger-vehicle length, then multiplying distance by the 30-fps frame rate.Two vanishing points are detected in the first frame and used to construct vehicle bounding boxes and rectify the scene for motion estimation.Source: Figure 3 · p. 6, §3.1 · p. 6
3.2 Training Data for Vehicle Make and Model
- The training data combines 15,639 scraped make/model images with 300 images of fronts, sides, and backs from the 100 most-used passenger vehicles.Source: §3.2 · p. 7, Table 1 · p. 7
3.3 Overall System Implementation
- YOLOv8 detects vehicles, DeepSort and StrongSort track them, and speed is estimated from bounding boxes and vanishing points before cropped vehicles enter the identification pipeline.Plate crops pass through YOLOv7 detection, super-resolution, and EasyOCR; color is inferred using ColorDetect and histogram/KNN techniques.Source: §3.3 · p. 7
- The model was pretrained on VMMRDb, then its final layer was replaced by a 100-node fully connected layer and retrained on collected data, with augmentation during fine-tuning.The consolidated output includes mean speed, most frequent color, top 3 frequent makes and models, and top 10 frequent license plates.Source: §3.3 · pp. 8–9
4. RESULTS
The system’s overall accuracy varied substantially across vehicle features, while license-plate text recognition improved with super-resolution and fine-tuning. The tests also identified image and vehicle-detection conditions that constrained performance.
4.1 Performance of License Plate Recognition Model
- 47.06% accuracy was reached after Easy-OCR was fine-tuned on a small UFPR license-plate subset and synthetic data.The UFPR-ALPR evaluation used 1,800 images; the dataset contains moving cameras and vehicles.Source: §4.1 · p. 10
- Super-resolution improved the example OCR output from no correctly identified characters to 4 of 7, while the table compares three recognition pipelines.The pipelines combine YOLOv7 detection with Easy-OCR, super-resolution plus Easy-OCR, or super-resolution plus fine-tuned Easy-OCR.Source: Figure 5 · p. 10, §4.1 · pp. 10–11, Table 4 · p. 10
4.2 Performance of Overall System
- Color codes confused paint and body colors because they covered the full bounding box, including tires and rims; parked cars and blurry or moving-camera images also affected speed and plate accuracy.Speed accuracy is measured within 20% of true speed; the reported speed and plate accuracies were 16.3% and 29.7%.Source: §4.2 · p. 11
- 16.3% speed estimation within 20% of true speed, 29.7% plate recognition, 60.8% color identification, 48.6% manufacturer identification, and 16.9% model identification using top 3 estimates.The overall system was evaluated on 115 daytime videos containing 148 vehicles.Source: Table 5 · p. 11, §4.2 · p. 11
5. SURVEY FINDINGS
The survey gathered U.S. law-enforcement views on automated enforcement, including private-phone video and enforcement beyond speeding. Respondents named public perception, privacy, safety, and practicality as leading concerns, while the discussion considers potential uses and implementation constraints.
Survey findings
- Officers identified European time-over-distance cameras and U.S. speed and red-light cameras as effective and defensible systems.The section proposes private-phone video as a possible safety input, including use to guide patrols by location and time.Source: §5 · pp. 11–12
- Public perception, privacy, safety, and practicality were listed as top challenges for automated enforcement.The survey also asked about major challenges, observed applications, private smartphone use, and enforcement of non-speeding behaviors.Source: §5 · pp. 11–12, Table 6 · p. 12
- Private recordings could inform patrols at particular locations and times, while participants recommended public buy-in and framing submissions as a safety campaign rather than revenue collection.The paper likens video submissions to reports made through 911 or 311.Source: §5 · p. 12
- Although built-in speed governors appear easier than camera installation, segment-based limit changes can leave drivers in difficult situations if governors function imperfectly.A monitoring-only app is discussed as more suitable for some drivers, but maintaining it would require a comprehensive road-segment and speed-limit database.Source: §5 · pp. 12–13
6. CONCLUSIONS AND FUTURE WORK
The study concludes that smartphone-based methods show potential for automated speed enforcement, while reporting modest system accuracies and proposing specific improvements. Further work is needed across more challenging recording conditions and on implementation hurdles.
Conclusions
- 16.33% speed-estimation accuracy within a 20% error range, 29.70% license-plate recognition, 60.81% color detection, and 48.65% make detection were reported for the system.On 1,800 UFPR-ALPR images, license-plate text accuracy was 47.1%.Source: §6 · p. 13
Future work
- Using each vehicle’s make/model length rather than one average or median assumption is proposed to improve speed estimation, especially for unusually long or short vehicles.Other proposed improvements include focusing color detection on vehicle parts, training with moving-camera data, collecting and labeling more data, reducing nearby-vehicle noise, and testing camera aperture and shutter speed.Source: §6 · p. 13
- Future research should test nighttime and moving-camera videos, develop an app for submitting flagged clips with recording-time locations, and assess scalability in dense settings.The authors expect nighttime speed and plate inference to be more difficult and identify expressways and city centers as scalability settings to explore.Source: §6 · p. 13
- Private-phone enforcement support may face privacy concerns and fake submissions, and many U.S. states currently do not allow traffic or speed cameras for law enforcement.The authors also identify comprehensive maps for agency response as a future endeavor.Source: §6 · pp. 13–14