Bug P2
Status Update
Comments
nr...@google.com <nr...@google.com>
nr...@google.com <nr...@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]
mi...@google.com <mi...@google.com> #3
I also need this problem solved :)
co...@marcinstecki.pl <co...@marcinstecki.pl> #4
same :D
aa...@google.com <aa...@google.com>
ni...@copyrightagent.com <ni...@copyrightagent.com> #5
+1
co...@marcinstecki.pl <co...@marcinstecki.pl> #6
+1
jo...@gmail.com <jo...@gmail.com> #7
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.
co...@marcinstecki.pl <co...@marcinstecki.pl> #8
+1
Description
Problem we have encountered:
Our product is usinghttps://cloud.google.com/vision/docs/detecting-web to moderate user content and detect it's presence over the web. Last 4-6 weeks we are observing inconsistent results from the api. Sending the same exact image twice can yield different results in regards to web presence.
What you expected to happen: We expected the api we pay for to behave in deterministic manner. We don't mind getting an incorrect response or a false positive in web detection, but random results are unacceptable.
Steps to reproduce:
Type 1 of response you will get (correct, detects images):
Type 2 (incorrect no pagesWithMatchingImages field - no images detected)