Assigned
Status Update
Comments
sa...@google.com <sa...@google.com>
sa...@google.com <sa...@google.com> #2
I have informed our engineering team of this feature request. There is currently no ETA for its implementation.
A current workaround would be to check the returned "boundingPoly" [1] "vertices" for the returned "textAnnotations". If the calculated rectangle's heights > widths, than your image is sideways.
[1]https://cloud.google.com/vision/reference/rest/v1/images/annotate#boundingpoly
A current workaround would be to check the returned "boundingPoly" [1] "vertices" for the returned "textAnnotations". If the calculated rectangle's heights > widths, than your image is sideways.
[1]
sa...@google.com <sa...@google.com>
[Deleted User] <[Deleted User]> #3
I also need this problem solved :)
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
I am working on a project on a portal to translate documents from English to six other languages. So far I have been very happy with the experience.
Problem you have encountered: Some of our documents have checkboxes in them. If the alignment between the checkboxes and the corresponding text is clear and extra space is available then everything works fine. But if space is more limited then the API seems to keep the position of the boxes fixed and make the text overlapping instead on the boxes instead
What you expected to happen: I assume that the model tries to hold the layout of the document and fill in text wherever possible. But holding position rigidly(as it seems to be happening now) seems counterintuitive.
Steps to reproduce: I have attached screenshots of the pdfs I tried with this issue
Other information (workarounds you have tried, documentation consulted, etc): My question is if there are any measures(apart from ensuring ample spacing) to try and mitigate this errors