In this assignment, your task is to implement OCR on car images in order to "read" the license plates. To do this, you will need to extract the letters from car images, perform character identification using either template matching or feature matching, and finally perform spatial analysis to put the letters in the correct order.
In src/hw3/letters you will find license plate images with two examples of each letter from A..Z and numbers from 0..9. These images will names of the form: A-1.jpg, A-2.jpg, ... 9-1.jpg, 9-2.jpg. In src/hw3/cars you will find several car images with license plates roughly centered within the image. Your task is to read in the letter images save everything you need for template matching or feature matching, and then perform OCR on each of the car images to "read" the license plates. Your program should output something like "car36.jpg has plate ABC 123".
In this project, we will be making use of the character identification functions from your previous assignment to perform OCR. Students have the option of using their code from the previous assignment or borrowing anything they need from the sample solution in src/hw2/hw2.cpp. This code is described below:
You can implement this program using either a bottom-up approach or a top-down approach. If you go for a bottom-up approach, start by creating basic methods and classes, and test theses methods using a simple main program that calls each method. When this is working, you can create the main program that uses these methods to solve the problem above.
If you go for a top-down approach, start by creating your main program that reads user input, and calls empty methods to pretend to solve the problem. Then add in the code for these methods one at a time. This way, you will get an idea of how the whole program will work before you dive into the details of implementing each method and class.
Regardless of which technique you choose to use, you should develop your code incrementally adding code, compiling, debugging, a little bit at a time. This way, you always have a program that "does something" even if it is not complete.
When you think you are about 1/2 way through the program, upload a copy of your source code and your program output at that point. Be sure to hand in something that compiles even if it does not do much when it runs.
Test your program to check that it operates correctly for all of the requirements listed above. Also check for the error handling capabilities of the code. Try your program on 2-3 input documents, and save your testing output in text files for submission on the program due date.
When you have completed your C++ program, write a short report (1-2 pages long) describing what the objectives were, what you did, and the status of the program. Does it work properly for all test cases? Are there any known problems? Save this report in a separate text file to be submitted electronically.
In this class, we will be using electronic project submission to make sure that all students hand their programming projects and labs on time, and to perform automatic analysis of all programs that are submitted. When you have completed the tasks above go to the class web site to "submit" your documentation, C++ program, and testing files.
The dates on your electronic submission will be used to verify that you met the due date above. All late projects will receive reduced credit (50% off if less than 24 hours late, no credit if more than 24 hours late), so hand in your best effort on the due date.
You should also PRINT a copy of these files and hand them into your teaching assistant in your next lab. Include a title page which has your name and uaid, and attach your hand written design notes from above.