I've been noticing more incorrect digits in our Cloud OCR results lately. They're cases which are pretty clear-cut and should be easily recognized. Lots of 3's instead of 9's and some 5's instead of 6's.

Here's one example:

example

The 6 is recognized as a 5. The char rec variants don't even include 6 as one option. Seems very wrong.

Another example:

example

Both of the trailing 9's are interpreted as 3's.

In the past, I feel like the API would have handled all of these cases just fine. Has something changed?

asked 13 Feb, 21:07

G%20Moore's gravatar image

G Moore
318


We haven't changed anything that may affect your results. Moreover, I have processed these two images using the processImage method with the profile=*textExtraction and imageSource=*photo parameters and the results are fine:

alt text

So, would you be so kind to send the source images to CloudOCRSDK@abbyy.com for our testing on our side?

link

answered 14 Feb, 15:00

Oksana%20Serdyuk's gravatar image

Oksana Serdyuk ♦♦
1.5k16

Sure, have just emailed these two images! Thanks!

(14 Feb, 15:21) G Moore
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×195

Asked: 13 Feb, 21:07

Seen: 147 times

Last updated: 14 Feb, 15:21

© 2016 ABBYY. All rights Reserved. www.ABBYY.com | Privacy Policy | Legal