This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 18%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
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!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 45%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi, can you please provide steps to reproduce this issue? If you have a repo to share that would be helpful as well. Thanks.
Using the sample, I'm able to get great accuracy. Please share steps to reproduce the issue you've described above, thanks.
I have a parent program that creates 6-8 forks of the Sample code that Microsoft has for the Cognitive Service READ. The files that are being passed to Microsoft are on my local machine. The only difference I have in my code from the Sample code is the output is saved to a file in a specific format.
The actual results are good but the accuracy of the "boundingbox" for each word seems to be off. You can see in the image posted in the question that the value "40.00" was found read correctly but the bounding box is not aligned correctly.
Thank you
Hi, thanks for your feedback. We are still reviewing your feedback, will share updates as soon as possible. Thanks.
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 50%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
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!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 71%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EET%3C/text%3E%3C/svg%3E)
it is 2024 and this problem is still there. we have it on thousands of documents. what is even more strange is that in the document intelligence studio on hover you can see the correct values displayed. it also correctly highlights the words. but the results in the json via api or in the "result" tab in studio are slightly off
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I also have same problem. in most of documents 1, D and 5 is extracting wrong.