READ OCR Bounding Box Accuracy

Question

I am using the basic Code for the READ OCR that Microsoft gives in their getting started guide. The only modification is that I am running that program with multiprocessing with 4 cores so I am making multiple calls to the API at the same time.

The READ OCR sometimes gives me a Bounding Box of a word that is either too large or too small for that word. You can see in the screenshot below that the word "40.00" was completely found but the bounding box is too small and does not cover the entire word. The same issue happens with the word "Current". There is cases where the bounding box is too large as well.

Any help would be appreciated!

Answer 1

I have found the same as well, the below image shows Tesseract bounding boxes in Blue and Azure Read API bounding boxes in Red. Almost every bounding box from azure is taller than the actual text and nearly all shifted to the left slightly.

Is there any update for a fix to this issue? @GiftA-MSFT

Answer 2

I am struggling with the same problem as @Mitchell . Bounding boxes are inaccurate and often shifted to the left.
Is there any progress on this? Can we expect this problem to be fixed at some point? @GiftA-MSFT
As my use case is depending on exact bounding boxes, I'd need to find another solution if fixing this is not on the roadmap.

Thanks!

Answer 3

I too am have the same problem with the bounding boxes often being too spacious on the left/top/bottom sides and not properly encompassing the text on the right side.

Answer 4

I also have same problem. in most of documents 1, D and 5 is extracting wrong.

Answer 5

Dear all,

I see the same problem, both for the Azure Read API V3 and the Azure Document Intelligence Read API.

@Microsoft-Team, can you please give an update on this (do you consider this as a problem, will or won't you fix this)?

Thanks and all the best,
Nico