High School Track

Pothole detection

High School Track


Overview & Challenge

The High School Track introduces students to artificial intelligence and computer vision by tackling a real-world problem: pothole detection. This beginner-friendly competition emphasizes teamwork, creativity, and hands-on learning. Participants will collaborate in teams to develop AI models that automatically identify and localize potholes in road images, contributing to safer roads and smarter infrastructure.


Teamwork

Form teams of 2-3 students to collaborate, brainstorm, and learn together.

Challenge Summary

Your mission: Build an Object Detection model that detects and localizes potholes in road images by drawing bounding boxes around each pothole. You will use a curated subset of the Image Dataset—specifically, images from country1 and country2 containing pothole damage.

  • Input: Road scene images
  • Output: For each pothole, predict its location as a bounding box (class x y w h)
  • Focus: Only pothole detection (other damage types excluded for this track)

About the Dataset

The Road Dataset provides thousands of annotated road images from multiple countries. For the High School Track, you will use a simplified subset:

  • Countries: country1 and country2
  • Damage Type: Pothole
  • Annotations: Each image is labeled with bounding boxes around potholes

Training Dataset Distribution

High School Dataset Distribution by Country

Distribution of pothole labels across countries for the High School Track. Total: 1,956 pothole labels (country1: 1,025, country2: 931)

Training Images by Country

High School Image Count by Country

Number of training images available for each country. Total: 1,956 images (country1: 1,025, country2: 931)

Timeline & Schedule

Competition Overview

Start Date

7th July 2025

Competition Phases

Phase 1: Kickoff & Team Formation

7th July 2025

Phase 2: Train Dataset release

14th July 2025

Phase 3: Test Images release

24th July 2025

Phase 4: Presentations

26th July 2025

Judging Criteria

Evaluation Process

Submission Requirements

Code Requirements

  • Complete source code with clear structure
  • Requirements.txt or equivalent dependency file
  • Working implementation that can be executed
  • Comments explaining key algorithms and decisions
  • Version control history (Git recommended)

Documentation Requirements

  • Comprehensive README.md file
  • Installation and setup instructions
  • Data preprocessing and feature engineering explanation
  • Model architecture and parameter choices
  • Results analysis and interpretation

Results Requirements

  • folder with predicted results
  • Expected content format: class x y w h confidence

Expected Output Example

Example of expected YOLO annotation format showing bounding boxes around detected potholes

Example showing expected bounding box annotations for pothole detection (class x y w h confidence format)