Global road-damage vision
YOLOv8n ONNX trained on 25,619 images across seven RDD2022 source sets. OpenCV 5 performs decoding, preprocessing, CPU DNN inference and class-aware suppression. Four road-damage classes.
Upload a road video. An AWS-hosted CPU runs OpenCV 5 + the global YOLO model, actively reinspects uncertain frames, compares optical flow and saves a traceable case to private S3. Lambda produces the cloud review report.
This is a publicly reachable AWS website; upload and inspection APIs require a demo access code to prevent abusive compute usage.
Use the existing cloud report to show evidence even before uploading another video.
Maximum 80 MB. The first 300 frames are processed by the existing RoadGuard agent (configurable server-side). Uploaded source video and evidence are stored privately in S3.
Load a cloud run or upload a video to see its processing stages.
Run: none selected
YOLO supplies detections. The agent chooses its next observation: it selects extra frames based on confidence and previous support, compares candidate motion with surrounding-road motion, and records every request and result.
Real images, detection classes, model scores and temporal support from the selected cloud inspection. No simulated road-damage confirmations.
Load a report to view evidence.
Original and annotated images will appear here after a cloud report loads.
Auditable decisions made after perception. Expand each step to see which frames the agent requested and how many supported the candidate.
Select an event to see its agent reasoning trace.
We built an evidence-driven inspection workflow that asks for more observations, exposes uncertainty, detects possible fixed-camera artifacts, and connects to a live AWS reporting pipeline.
YOLOv8n ONNX trained on 25,619 images across seven RDD2022 source sets. OpenCV 5 performs decoding, preprocessing, CPU DNN inference and class-aware suppression. Four road-damage classes.
The agent tests additional frame offsets when confidence is low or temporal support is insufficient. Inspection requests and matching outcomes are recorded, not hidden.
Sparse Lucas–Kanade optical flow compares candidate-region motion with surrounding road motion. It raises a possible camera-fixed artifact signal rather than asserting a reflection is proven.
Every candidate includes source frame, box, model confidence, associated observations, reinspection tool results and unmodified/annotated images. Inspectors can challenge the AI's claim.
This public UI calls an API hosted on Amazon EC2. The host runs the same CPU OpenCV/ONNX inspection code; private S3 receives source video, evidence and trace; S3 events trigger Lambda to generate review summaries.
AI findings never become automatically verified road defects. A reviewer can confirm, reject or request further evidence; a timestamped decision history is stored in private S3.
Evaluated on 3,833 held-out images. These scores do not measure UK dashcam video performance or prove real-world defect accuracy.
RoadGuard does not infer GPS location, measure crack depth, calculate repair costs or claim infrastructure safety. Temporal groups are image-space associations, not verified distinct physical defects. A camera artifact can remain undetected.
Cloud video inference is on EC2, not inside the S3-triggered Lambda function. A hosted demo is not automatically a horizontally scalable production service.
Inspectors review the model evidence and decide whether each candidate is accepted, rejected or needs further inspection. Decisions are stored in S3, not just in the browser.
Select an event in Inspection evidence.
No decisions recorded for this run.
Stored as reviews/<run-id>/decisions.json in a private S3 bucket. Record includes event ID, decision, reviewer label and UTC timestamp.