5.6.4. Google Cloud Integration. (Google Vision OCR and Google Geolocation API)

Some Google Cloud services can be integrated into ChronoScan Capture:

There are two ways of using the Google Cloud Services with ChronoScan Capture.

Using the ChronoScan Service account
Using an external Google Vision Cloud application owned and managed by third parties

1. Using the ChronoScan Service account

When using the ChronoScan Service account credits are required and must be bought as a plug-in package.
The ChronoScan service account is already configured to use both Google Vision OCR and Google Geolocation API and it provides user customization within ChronoScan Desktop.

1.1 Activation

Buy Google Vision credits
Open ChronoScan Desktop > 'Scan/Input' tab > 'OCR Read' menu > 'Active OCR engine' submenu > Select 'Google Vision OCR'

Now our active OCR is the Google Vision OCR, and we can configure it and make sure the endpoint server is working properly

3.1. In 'Scan/Input' tab > 'OCR Read' menu > Select the 'Active OCR Settings' option and the configuration window opens

3.2. These are the configuration options for the ChronoScan Service account:

Property	Value	Description
Service account configuration / Service account	Type: String Default: ChronoScan integrated service (Requires credits)	Here is where we choose the type of integration with Google Vision. Since we are configuring the ChronoScan Service account, make sure the selected option is: ChronoScan integrated service (Requires credits)
OCR settings / Endpoint	Type: String Default: EU	Enpoint server location for Google server to execute. EU / Europe US / United States of America
OCR settings / Compression level	Type: String Default: Auto	Compression level for processed files for Google Vision OCR Auto / Prioritizes performance over speed Low / Prioritizes speed over performance * Google Vision API has a file size limit. Documentation about it here.
OCR settings / Deskew image	Type: Boolean Default: False	If True Chronoscan will deskew the images before sending to process.
OCR settings / Fallback OCR	Type: String Default: No	Choose an available OCR fallback here if you want to retry the OCR processing in case a Google Vision request fails.
OCR settings / Allow analytics and image storage	Type: Boolean Default: False	If True, you allow ChronoScan organization to save processed files for analytical, labbing and debugging purposes only. Request with this active will be slightly slower.
OCR settings / Language Hints	Type: Checkbox Default: Auto	Google Vision OCR language hints. Please refer to their documentation for more info.

4. The endpoint connection can be checked by clicking on the 'Test server button'. If the status code is 200, Google Vision OCR can be used in ChronoScan as any other OCR engine.

2. Using an external Google Vision Cloud application owned and managed by third parties

Requires an advanced or enterprise license

An external Google Cloud application can be used in ChronoScan through and API_KEY
When using a Google Cloud external application, creating, configuring, managing and billing for the Google Cloud application are completely a responsability of the owner of that external application

2.1 Activation

Important: To be able to use Google vision OCR and Google Geolocation API, both APIS must be enabled on your Google Cloud app.

Create/ have a Google Cloud application.

2. Generate a valid API_KEY external application console and provide it to ChronoScan in the configuration window

3. Open ChronoScan Desktop > 'Scan/Input' tab > 'OCR Read' menu > 'Active OCR engine' submenu > Select 'Google Vision OCR'

4. Now our active OCR is the Google Vision OCR, and we can configure it and make sure the endpoint server is working properly

4.1. In 'Scan/Input' tab > 'OCR Read' menu > Select the 'Active OCR Settings' option and the configuration window opens

4.2. These are the configuration options for the External Google Cloud Application

Property	Value	Description
Service account configuration / Service account	Type: String Default: External Google Cloud Application. (Requires API_KEY)	Here is where we choose the type of integration with Google Vision. Since we are configuring the External Google Cloud, make sure the selected option is: External Google Cloud Application. (Requires API_KEY)
Service account configuration / API_KEY	Type: String	A valid API_KEY provided by the user to connect to the desired Google Cloud application.
OCR settings / Compression level	Type: String Default: Auto	Compression level for processed files for Google Vision OCR Auto / Prioritizes performance over speed Low / Prioritizes speed over performance * Google Vision API has a file size limit. Documentation about it here.
OCR settings / Deskew image	Type: Boolean Default: False	If True Chronoscan will deskew the images before sending to process.
OCR settings / Fallback OCR	Type: String Default: No	Choose an available OCR fallback here if you want to retry the OCR processing in case a Google Vision request fails.

5. The endpoint connection can be checked by clicking on the 'Test server button'. If the status code is 200 and the provided API_KEY is valid, Google Vision OCR can be used in ChronoScan as any other OCR engine.

Google Geolocation API

To use the Google Geolocation engine, configure a service account as explained above.
Geolocation services are available through the Visual Basic scripting object HubGeoAPI

Examples and documentation here.