Assigned
Status Update
Comments
jo...@google.com <jo...@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]
ja...@gmail.com <ja...@gmail.com> #3
I also need this problem solved :)
gu...@gmail.com <gu...@gmail.com> #4
same :D
ds...@google.com <ds...@google.com>
ds...@google.com <ds...@google.com>
mm...@gannett.com <mm...@gannett.com> #5
+1
Description
We would like to run Vision API on images from our buckets. Images are rotated with EXIF orientation that corrects the rotation. We cannot influence how the images are stored. Currently, our "hotfix" is to read the EXIF orientation from the image in our service, to know how to rotate Vision API result.
How this might work:
Vision API should respect EXIF orientation flag
If applicable, reasons why alternative solutions are not sufficient:
It is suboptimal to read images from the bucket twice, it increases our total cloud cost, and reduces performance.
Other information (workarounds you have tried, documentation consulted, etc):
This recent release removed that functionality:
This one recommends creating an issue if we rely on that functionality: