| Literature DB >> 25608217 |
Shouyi Yin1, Peng Ouyang2, Leibo Liu3, Yike Guo4, Shaojun Wei5.
Abstract
Robust and fast traffic sign recognition is very important but difficult for safe driving assistance systems. This study addresses fast and robust traffic sign recognition to enhance driving safety. The proposed method includes three stages. First, a typical Hough transformation is adopted to implement coarse-grained location of the candidate regions of traffic signs. Second, a RIBP (Rotation Invariant Binary Pattern) based feature in the affine and Gaussian space is proposed to reduce the time of traffic sign detection and achieve robust traffic sign detection in terms of scale, rotation, and illumination. Third, the techniques of ANN (Artificial Neutral Network) based feature dimension reduction and classification are designed to reduce the traffic sign recognition time. Compared with the current work, the experimental results in the public datasets show that this work achieves robustness in traffic sign recognition with comparable recognition accuracy and faster processing speed, including training speed and recognition speed.Entities:
Mesh:
Year: 2015 PMID: 25608217 PMCID: PMC4327121 DOI: 10.3390/s150102161
Source DB: PubMed Journal: Sensors (Basel) ISSN: 1424-8220 Impact factor: 3.576
Figure 1.Different kinds of traffic signs from GTSRB data set.
Figure 2.Illustration of the rotation invariant binary pattern based feature computing to achieve fast and robust traffic sign detection.
Figure 3.Matching rate.
Figure 4.Processing time.
Performance comparison for feature clustering.
| K-means | / | 100% (baseline) | 0.6 s |
| ANN based K-means | 16->16->1 | 99.59% | 0.001 s |
| ANN based K-means | 16->8->2 | 98.64% | 0.0015 s |
| ANN based K-means | 16->4->4 | 96.53% | 0.001 s |
Performance comparison with 320 × 240 image size.
| ANN | 16->16->1 | 98.62% | 500 |
| ANN | 16->8->2 | 97.44% | 435 |
| ANN | 16->4->4 | 95.32% | 500 |
| SVM | Kernel based | 98.64% | 25 |
| Random Forest | Decision tree based | 97.54% | 125 |
| Full matching | Point to point | 99.89% | 0.1 |
Performance comparison when changing the image size.
|
| |||||
|---|---|---|---|---|---|
| ANN | CA | 98.62% | 98.60% | 98.59% | 97.55% |
| CS(fps) | 500 | 150 | 58 | 16 | |
|
| |||||
| SVM | CA | 98.64% | 98.63% | 98.60% | 98.56% |
| CS(fps) | 25 | 7.3 | 2.6 | 0.52 | |
|
| |||||
| Random Forest | CA | 97.54% | 97.52% | 97.44% | 97.41% |
| CS(fps) | 125 | 33 | 9.1 | 2.3 | |
|
| |||||
| Full matching | CA | 99.89% | 99.86% | 99.83% | 99.81% |
| CS(fps) | 0.1 | 0.045 | 0.013 | 0.004 | |
Figure 5.The whole computation flow of traffic sign recognition. The image embedded in the graph is from the GTSRB data set.
Figure 6.Parts of recognition results on GTSRB data set: (a) original image; (b) preprocessing to locate the candidate regions; (c) traffic sign recognition; (e) original image; (f) preprocessing to locate the candidate regions; (g) traffic sign recognition.
Processing times.
| Speed limit signs | 810 ms | 420 ms | 31 ms | 25.1× | 12.5× |
| Unique signs | 1300 ms | 610 ms | 54 ms | 23.1× | 10.3× |
| Danger Signs | 1010 ms | 530 ms | 44 ms | 22.0× | 11.0× |
| Mandatory signs | 580 ms | 230 ms | 12 ms | 47.3× | 18.2× |
| Derestriction signs | 940 ms | 490 ms | 37 ms | 24.4× | 12.2× |
| Other prohibitory signs | 856 ms | 460 ms | 38 ms | 21.5× | 11.1× |
Correctly matched points comparison.
| Speed limit signs | 23 | 15 | 19 |
| Unique signs | 39 | 21 | 36 |
| Danger Signs | 31 | 24 | 29 |
| Mandatory signs | 31 | 24 | 29 |
| Derestriction signs | 89 | 70 | 84 |
| Other prohibitory signs | 32 | 26 | 31 |
Comparison with other works for the GTSRB data set.
| HOG+ANN | 36 | 96.77% | 1740 s | 50 fps |
| LBP+ANN | 59 | 96.59% | 1260 s | 100 fps |
| SIFT+ANN | 128 | 97.74% | 1980 s | 1 fps |
| SURF+ANN | 64 | 97.46% | 1680 s | 2 fps |
| Proposed feature +ANN | 64 | 98.62% | 600 s | 200 fps |
Comparison with other works for the STS data set.
| HOG+ANN | 36 | 95.41% | 2349 s | 12 fps |
| LBP+ANN | 59 | 95.62% | 1944 s | 21 fps |
| SIFT+ANN | 128 | 97.10% | 2911 s | 0.2 fps |
| SURF+ANN | 64 | 97.52% | 2014 s | 0.5 fps |
| Proposed feature +ANN | 64 | 98.33% | 923 s | 52 fps |
Comparison with other works for the GTSRB data set.
| Jin [ | GPU C2075&6-CORE | 99.65% | >7 h | >1 s |
| Zaklouta [ | / | 96.14% | / | <0.02 s |
| Tang [ | 98.65% | 3600 s | 0.04 s | |
| This work | 98.62% | 1800 s | 0.005 s |
Comparison with other works for the STS data set.
|
| ||||
|---|---|---|---|---|
| Pedestrian crossing | 98.0% | 0 | 99.0% | 0 |
| Designated lane right | 95.8% | 0 | 96.1% | 0 |
| No standing or parking | 100.0% | 0 | 100.0% | 0 |
| 50 kph | 91.7% | 2 | 93.2% | 2 |
| 30 kph | 95.8% | 1 | 97.4% | 1 |
| Priority road | 95.7% | 0 | 96.78% | 0 |
| Give way | 94.7% | 0 | 95.9% | 0 |
Figure 7.Testing in real conditions to obtain performance averages, and make a comparison with the work by Tang [22].
Comparison in real conditions.
| Tang [ | TI DM6467 | 5400 s | 10 fps |
| This work | TI DM6467 | 2100 s | 43 fps |