Feature Request P2
Status Update
Comments
ka...@google.com <ka...@google.com>
la...@google.com <la...@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]
ti...@google.com <ti...@google.com> #3
I also need this problem solved :)
Description
This will create a public issue which anybody can view and comment on.
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 NLP API is only able to extract the Date entities for data given in this format Month-day-year where year: four digit year. month:two digit month number or name, day: two digit day number. Trying different entries like yesterday, tomorrow, last week, etc. ware not captured. The API is not extracting the Date entities for relative days/dates.
What you expected to happen: NLP API identifies the relative days as Date entities.
Steps to reproduce: For this sample input:
I live in new york near times square, and work at google. I met with a friend yesterday.
The API is able to extract the entities like organization, location, and person. However, it does not recognize "yesterday" as an entity of Date or Time entity. Same happens with "tomorrow", "last week", "next year" and other relative dates.Other information (workarounds you have tried, documentation consulted, etc):