During this week, I collected traffic signs on the web and finally found a very nice complete database maintained by Richard C. Moeur, who is a voting member of the National Committee on Uniform Traffic Control Devices (NCUTCD). I zipped his database and uploaded at my site for your information. You can download the database at Construct the traffic sign database. Please be advised that Moeur had placed a copyright rule limited to recreational or study purposes.
Within those numerous signs (336 samples), you can see all types of warning signs at one place -- Select a number of sign candidates for a priori algorithm testing. Now it is easy to understand that our problem is not limited to predefined structured pattern recognition but OCR. It should be more discussed whether we should treat the characters located inside the warning frames as computer-generated fonts or just special line features. Anyway, I also found fonts database that can be used to generate the traffic sings as we want (Check http://www.triskele.com/fonts/). This font set may be used for OCR training.
In addition, several neural network computing packages for the general purposes are also reviewed and tested -- Neural Network. However, it should be noted that there is a possibility that we may need to devise a specially designed neural network, which means that we should developed the neural computing code by ourselves.
Besides, I am collecting various information related with traffic signs and this TSPR (Traffic Sign Pattern Recognition) project Wiki is rapidly growing up. Please take a look the main page and follows links in there. If you have any questions or suggestions, just send me an email or you can directly edit it. This Wiki engine provides the document versioning system that can provide complete document protection from any modification when it is necessary to recover.
This week, I wish to discuss with members on several points including: