Bug P2
Status Update
Comments
ti...@google.com <ti...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
ph...@aluma.io <ph...@aluma.io> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
zo...@google.com <zo...@google.com> #4
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
ph...@aluma.io <ph...@aluma.io> #5
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
zo...@google.com <zo...@google.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
jp...@google.com <jp...@google.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
ph...@aluma.io <ph...@aluma.io> #8
Any progress in here?
ph...@aluma.io <ph...@aluma.io> #9
I would like this feature as well.
is...@google.com <is...@google.com>
lj...@gmail.com <lj...@gmail.com> #10
Hello, any progress in here? Please is very frustrating.
Description
Hi,
We're using the DOCUMENT_TEXT_DETECTION in production to perform OCR on documents. We've found that the quality of OCR of PDF documents compared to the exact same TIFF to be very poor (with missing characters, extra whitespace etc).
I've attached an example test image in both PDF and TIFF formats. You can see the text is very legible and the OCR from the TIFF is 100% correct. The OCR from the PDF has multiple missing characters.
This leads me to believe that the internal rendering of PDFs performed by the cloud vision API is buggy.
Can anyone shed any light?
Correct OCR results from TIFF:
Poor read from PDF:
See missing hyphen, missing 'ME' from 'PAYMENT', and various lost hash/pound characters with extra newlines.
The pdf and tiff are attached to this message.