Assigned
Status Update
No update yet.
Comments
wi...@google.com
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]
[Deleted User] <[Deleted User]>
I also need this problem solved :)
Description
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.
Problem you have encountered: The customer encounters an issue with the recognition of the digits in a Speech to Text v2 API for Polish language. They found that when using an audio sample that contains repeated digits, the model is not accurate when outputting the text result.
What you expected to happen: The customer expects the records to be accurate, with all the digits transcribed to text as it is on the audio sample in Polish language.
Steps to reproduce: The model processed an audio sample that contained “555” throughout other digits, and the output was “55” along with the other digits.