Assigned
Status Update
No update yet.
Comments
va...@google.com
pu...@google.com
Hello,
To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue:
- Has this scenario ever worked as expected in the past?
- Do you see this issue constantly or intermittently ?
- If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
- To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
- It would be greatly helpful if you could attach screenshots of the output related to this issue.
Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.
Thank you for your understanding and cooperation.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Better organization of the text results in OCR. The UI provides a good order of the text, but the json response through the API has the text out of order. The logic already exists in the UI and looking to implement the same logic in the json.
How this might work:
Parse the location of the text in the boundingPolly before delivering the result in the json. This eliminates the need to have to code the logic or at least minimizes it and users can use the results right away with better results.
If applicable, reasons why alternative solutions are not sufficient:
Order of the text is critical and currently every usage of OCR with Document AI requires to implementation of the logic to set the correct order of the text.
Other information (workarounds you have tried, documentation consulted, etc):
Vision AI does a much better job at providing the right order, but this only works on images.