Assigned
Status Update
Comments
ji...@indegene.com <ji...@indegene.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]
sj...@google.com <sj...@google.com>
sj...@google.com <sj...@google.com> #3
I also need this problem solved :)
ji...@indegene.com <ji...@indegene.com> #4
same :D
sj...@google.com <sj...@google.com> #5
+1
Description
The problems we have encountered are listed below:
- OCR is unable identify superscripts
- it is not recognizing symbols ex: §,¶,±,ǂ, * etc.
- it is not recognizing bullet points
- Symbols like dagger (ǂ) is read as 't'
- Not extracting text properly when image contain one or more column, text will not be in the same order
- if image has hidden text then we cant read the text properly
- losing characters
if we have 300px resolution images we are missing some chars,
same image if we reduce to 150 or 100 we will get chars which are missed in 300pixels resolution but we
may loss some other chars
- getting additional characters in text block
What you expected to happen:
- All the above problems needs to be resolved and the images should return the exact characters
Steps to reproduce:
- Attached image for reproducing the issue
Other information (workarounds you have tried, documentation consulted, etc):
We couldnt find any work around