Assigned
Status Update
No update yet.
Comments
mo...@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]
je...@gmail.com
I also need this problem solved :)
sy...@gmail.com
same :D
ab...@google.com
+1
je...@gmail.com
+1
sy...@gmail.com
This needs more attention. It's not just a display issue as described in the report. The co-ordinates returned in 'boundingPoly' are incorrect if the image was taken on a phone. All the x points should be y and vice versa.
The workaround does not make sense as "boundingPoly" [1] "vertices" for "textAnnotations" does not indicate the image dimensions - it indicates the dimensions of the relevant text block inside the image.
The workaround does not make sense as "boundingPoly" [1] "vertices" for "textAnnotations" does not indicate the image dimensions - it indicates the dimensions of the relevant text block inside the image.
Description
For example:
Item 1: "The quick brown fox"
Item 2: "jumped over the lazy dog."
If sent in one request, fox will depend on jumped in the dependency tree. Having this feature would allow for one request to include both items albeit them being independent.
The Natural Language API team have been notified about the possible implementation of this feature. Kindly note that there are no guarantees or ETAs for the implementation of this feature. All future communication regarding this matter will be posted on this thread.