Hi,
I am using Aspose.OCR in my .net application. I have taken a trial version. Initially when i have tested it looks working fine. But when i have started using bigger rectangles, it started producing wrong results.
For example in my attached image if i use (x,y,width, height) as (50,440,150,30) it gives me correct result which is “James Donovan” but if i increase the width (50,440,300,30) it shows text as blank.
Also if i use rectangle 53,533,820,30 then text supposed to be “South Boston, MA 02127” but it is coming as "SQurh Bosron, MA 02127"
I am using .net 4.5 framework and using aspose dll version 3.5.0.0
Regards,
Manish
Hi Manish,
Thank you for your inquiry and providing sample file.
We have evaluated the attached image at our end. While testing it was found that the image has very low DPI value i.e. 96. Please note that the current implementation of the Aspose.OCR API works well with images having resolution of at least 300 DPI and the accuracy rate tends to decrease by decreasing the resolution. Your provided image has resolution of 96 DPI therefore it will not be possible to get 100% accuracy.
Furthermore the issue has been logged into our system with ID OCR-34250. We are continuously improving recognition quality. Low DPI images will work once issue OCR-34250 is fixed.
Hi,
Thanks for response.
I have changed the DPI of my image now it is of 300 dpi, still i am facing following issue.
if i use rectangle 53,533,820,30 then text supposed to be “South Boston, MA 02127” but it is coming as "SQurh Bosron, MA 02127"
I ma attaching new image in my earlier message, as here i do not have option to attach image.
Regards,
Manish
Hi Manish,
Thank you for writing us back.
You can send us the sample image to perform OCR by replying the post and using “add/update” button under File attachment heading. Sharing sample image will help us to further investigate the issue.
Hi Manish,
Thank you for providing sample image. We will use the sample image during investigation and will update you accordingly about our findings via this forum thread.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.