Datasets:
File size: 1,957 Bytes
6b119be dce6b4c d0036b3 dce6b4c | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 | ---
dataset_name: PPE Detection
datasets:
- <your-username>/ppe-detection
license: cc-by-4.0
task_categories:
- object-detection
tags:
- computer-vision
- object-detection
- safety
- ppe
- yolo
pretty_name: PPE Detection Dataset
size_categories:
- 10K<n<100K
---
# PPE Detection Dataset 🦺🪖😷
A high-quality, annotated dataset for **Personal Protective Equipment (PPE)** detection in industrial and construction environments.
The dataset is suitable for training **object detection models** such as YOLOv8, YOLOv5, Detectron2, etc.
---
## 1. Dataset Summary
This dataset contains images annotated with **6 PPE classes**:
- Vest
- Safety Shoe
- Mask
- Helmet
- Goggles
- Gloves
It is designed for:
- Construction site safety compliance
- Industrial worker monitoring
- Automated PPE detection for CCTV / RTSP cameras
- Real-time analytics on edge devices (Jetson, Raspberry Pi, etc.)
### Class Distribution
| Class | Count |
|-------------|-------|
| Vest | 4,418 |
| Safety Shoe | 2,006 |
| Mask | 2,763 |
| Helmet | 2,703 |
| Goggles | 1,431 |
| Gloves | 2,693 |
| **Total Objects** | **16,014** |
> Note: Counts refer to **annotated objects**, not number of images.
---
## 2. Supported Tasks and Leaderboards
**Task type:** `Object Detection`
Typical use cases:
- PPE presence/absence detection
- Safety rule enforcement
- Worker compliance monitoring
- Scene understanding in industrial environments
No official leaderboard is maintained yet.
---
## 3. Dataset Structure
The dataset follows a **YOLO-style folder structure**, typically like:
```text
PPE/
├── train/
│ ├── images/
│ └── labels/
├── valid/
│ ├── images/
│ └── labels/
├── test/
│ ├── images/
│ └── labels/
└── data.yaml
---
🤝 Thanks / Contact
For improvements, issues, or contributions—open a Pull Request or Discussion.
|