chrome-lens-py 1.2.2

Library to use Google Lens OCR for free via API used in Chromium on python

Chrome Lens API for Python

English | Русский

This project provides a Python library and CLI tool for interacting with Google Lens's OCR functionality via the API used in Chromium. This allows you to process images and extract text data, including full text, coordinates, and stitched text using various methods.

Features

• Extract the full text: Extract the full text from the image.
• Coordinate Extraction: Extract the text along with its coordinates.
• Stitched text: Restore text from coordinate blocks using various methods:
  • Old method: Sequential stitching of text.
  • New method: Improved text stitching by calculating them line by line. It is not recommended on rotated texts. Use the past one.
• Scan images from URLs: Process images directly from URLs without downloading them manually.
• Cookie Management: Download and manage cookies from a file in Netscape format or directly through the configuration.
• Proxy Support: Supports HTTP, HTTPS, and SOCKS4/5 proxies to make requests over different networks.

PS: Lens has a problem with the way it displays full text, which is why methods have been added that stitch text from coordinates.

Installation

You can install the package using pip:

From PyPI

pip install chrome-lens-py

Update from PyPI

pip install -U chrome-lens-py

From GIT

pip install git+https://github.com/bropines/chrome-lens-py.git

From source

Clone the repository and install the package:

git clone https://github.com/bropines/chrome-lens-api-py.git
cd chrome-lens-api-py
pip install -r requirements.txt
pip install .

Usage

You can use the lens_scan command from the CLI to process images and extract text data, or you can use the Python API to integrate this functionality into your own projects.

CLI Usage

lens_scan <image_source> <data_type>

• <image_source>: Path to the image file or URL.
• <data_type>: Type of data to extract (see below).

Data Types

• all: Get all data (full text, coordinates, and stitched text using both methods).
• full_text_default: Get only the default full text.
• full_text_old_method: Get stitched text using the old sequential method.
• full_text_new_method: Get stitched text using the new enhanced method.
• coordinates: Get text along with coordinates.

Examples

To extract text using the new method for stitching from a local file:

lens_scan path/to/image.jpg full_text_new_method

To extract text using the new method for stitching from a URL:

lens_scan https://example.com/image.jpg full_text_new_method

To get all available data from a local file:

lens_scan path/to/image.jpg all

To get all available data from a URL:

lens_scan https://example.com/image.jpg all

CLI Help

You can use the -h or --help option to display usage information:

lens_scan -h

Programmatic API Usage

In addition to the CLI tool, this project provides a Python API that can be used in your scripts.

Basic Programmatic Usage

First, import the LensAPI class:

from chrome_lens_py import LensAPI

Example Programmatic Usage

1. Instantiate the API:

   api = LensAPI()
   

2. Process an image:

   • Get all data from a local file:

     result = api.get_all_data('path/to/image.jpg')
     print(result)
     

   • Get all data from a URL:

     result = api.get_all_data('https://example.com/image.jpg')
     print(result)
     

   • Get the default full text from a local file:

     result = api.get_full_text('path/to/image.jpg')
     print(result)
     

   • Get the default full text from a URL:

     result = api.get_full_text('https://example.com/image.jpg')
     print(result)
     

   • Get stitched text using the old method from a local file:

     result = api.get_stitched_text_sequential('path/to/image.jpg')
     print(result)
     

   • Get stitched text using the old method from a URL:

     result = api.get_stitched_text_sequential('https://example.com/image.jpg')
     print(result)
     

   • Get stitched text using the new method from a local file:

     result = api.get_stitched_text_smart('path/to/image.jpg')
     print(result)
     

   • Get stitched text using the new method from a URL:

     result = api.get_stitched_text_smart('https://example.com/image.jpg')
     print(result)
     

   • Get text with coordinates from a local file:

     result = api.get_text_with_coordinates('path/to/image.jpg')
     print(result)
     

   • Get text with coordinates from a URL:

     result = api.get_text_with_coordinates('https://example.com/image.jpg')
     print(result)
     

Cookie Management

This project supports the management of cookies through various methods.

To receive cookies in Netscape format, you can use the following extensions:

• Chrome (Chromium): Cookie Editor
• Firefox: Cookie Editor

1. Loading Cookies from a Netscape Format File:

   • You can load cookies from a Netscape format file by specifying the file path.

   Programmatic API:

   config = {
       'headers': {
           'cookie': '/path/to/cookie_file.txt'
       }
   }
   api = LensAPI(config=config)
   

   CLI:

   lens_scan path/to/image.jpg all -c /path/to/cookie_file.txt
   

2. Passing Cookies Directly as a String:

   • You can also pass cookies directly as a string in the configuration or via CLI.

   Programmatic API:

   config = {
       'headers': {
           'cookie': '__Secure-ENID=17.SE=-dizH-; NID=511=---bcDwC4fo0--lgfi0n2-'
       }
   }
   api = LensAPI(config=config)
   

   or

   config = {
       'headers': {
           'cookie': {
               '__Secure-ENID': {
                   'name': '__Secure-ENID',
                   'value': '',
                   'expires': 1756858205,
               },
               'NID': {
                   'name': 'NID',
                   'value': '517=4.......',
                   'expires': 1756858205,
               }
           }
       }
   }
   api = LensAPI(config=config)
   

Proxy Support

You can make requests through a proxy server using the API or CLI. The library supports HTTP, HTTPS, and SOCKS4/5 proxies.

• Set Proxy in API:

  config = {
      'proxy': 'socks5://127.0.0.1:2080'
  }
  api = LensAPI(config=config)
  

• Set Proxy in CLI:

  lens_scan path/to/image.jpg all -p socks5://127.0.0.1:2080
  

Programmatic API Methods

• get_all_data(image_source): Returns all available data for the given image source (file path or URL).
• get_full_text(image_source): Returns only the full text from the image source.
• get_text_with_coordinates(image_source): Returns text along with its coordinates in JSON format from the image source.
• get_stitched_text_smart(image_source): Returns stitched text using the enhanced method from the image source.
• get_stitched_text_sequential(image_source): Returns stitched text using the basic sequential method from the image source.

Working with Coordinates

In our project, coordinates are used to define the position, size, and rotation of text on an image. Each text region is described by a set of values that help accurately determine where and how to display the text. Here's how these values are interpreted:

1. Y Coordinate: The first value in the coordinates array represents the vertical position of the top-left corner of the text region on the image. The value is expressed as a fraction of the image's total height, with 0.0 corresponding to the top edge and 1.0 to the bottom.

2. X Coordinate: The second value indicates the horizontal position of the top-left corner of the text region. The value is expressed as a fraction of the image's total width, where 0.0 corresponds to the left edge and 1.0 to the right.

3. Width: The third value represents the width of the text region as a fraction of the image's total width. This value determines how much horizontal space the text will occupy.

4. Height: The fourth value indicates the height of the text region as a fraction of the image's total height.

5. Fifth Parameter: In the current data, this parameter is always zero and appears to be unused. It might be reserved for future use or specific text modifications.

6. Sixth Parameter: Specifies the rotation angle of the text region in degrees. Positive values indicate clockwise rotation, while negative values indicate counterclockwise rotation.

Coordinates are measured from the top-left corner of the image. This means that (0.0, 0.0) corresponds to the very top-left corner of the image, while (1.0, 1.0) corresponds to the very bottom-right corner.

Example of Coordinate Usage

{
    "text": "Sample text",
    "coordinates": [
        0.5,
        0.5,
        0.3,
        0.1,
        0,
        -45
    ]
}

In this example:

• 0.5 — Y coordinate (50% of the image height, text centered vertically).
• 0.5 — X coordinate (50% of the image width, text centered horizontally).
• 0.3 — width of the text region (30% of the image width).
• 0.1 — height of the text region (10% of the image height).
• 0 — not used, default value (possibly reserved for future use).
• -45 — rotation angle of the text counterclockwise by 45 degrees.

These values are used to accurately place, scale, and display the text on the image.

Using Coordinate Format

You can choose the coordinate output format: percentages or pixels. By default, coordinates are output in percentages, but you can switch to pixels using the appropriate settings.

In Console

When using the command line, you can specify the coordinate format using the --coordinate-format flag. Acceptable values are 'percent' or 'pixels'.

Usage Examples:

• Output coordinates in percentages (default):

  lens_scan image.jpg coordinates
  

• Output coordinates in pixels:

  lens_scan image.jpg coordinates --coordinate-format=pixels
  

In API

When using the programmatic API, you can pass the coordinate_format parameter to the methods of the LensAPI class. Acceptable values are 'percent' or 'pixels'.

Usage Example:

from lens_api import LensAPI

api = LensAPI()

# Path to the image
image_path = 'image.jpg'

# Get data with coordinates in pixels
result = api.get_all_data(image_path, coordinate_format='pixels')

print(result)

Important

• When selecting the 'pixels' format, coordinates will be calculated relative to the original dimensions of the image, even if the image was resized for processing.
• If the format is not specified, coordinates are output in percentages by default.
• When working with pixel coordinates, ensure you use the original image for accurate placement of text regions.

Debugging and Logging

When using the CLI tool lens_scan, you can control the logging level using the --debug flag. There are two levels available:

• --debug=info: Enables logging of informational messages, which include general information about the processing steps.
• --debug=debug: Enables detailed debugging messages, including verbose output and the saving of the raw response from the API to a file named response_debug.txt in the current directory.

Example Usage:

• To run with informational logging:

  lens_scan path/to/image.jpg all --debug=info
  

• To run with detailed debugging logging:

  lens_scan path/to/image.jpg all --debug=debug
  

When using --debug=debug, the library will save the raw response from the API to response_debug.txt in the current working directory. This can be useful for deep debugging and understanding the exact response from the API.

Programmatic Debugging

When using the API in your Python scripts, you can control the logging level by configuring the logging module and by passing the logging_level parameter when instantiating the LensAPI class.

Example Usage:

import logging
from chrome_lens_py import LensAPI

# Configure logging
logging.basicConfig(level=logging.DEBUG)

# Instantiate the API with the desired logging level
api = LensAPI(logging_level=logging.DEBUG)

# Process an image
result = api.get_all_data('path/to/image.jpg')
print(result)

The logging_level parameter accepts standard logging levels from the logging module, such as logging.INFO, logging.DEBUG, etc.

When the logging level is set to DEBUG, the library will output detailed debugging information and save the raw API response to response_debug.txt in the current directory.

The --debug-out flag will allow you to specify the path where to save the response from the server, in the case of the debug level DEBUG. By default, it is saved, as described above, in the folder where the console is launched, that is, in CWD

Notes on Logging Levels

• INFO level: Provides general information about the process, such as when requests are sent and responses are received.
• DEBUG level: Provides detailed information useful for debugging, including internal state and saved responses.

Configuration Management

Configuration Priority

When running the CLI tool lens_scan, the application determines settings based on the following priority order (from highest to lowest):

1. Command-line arguments (CLI): Options specified directly when running the command have the highest priority.
2. Environment variables: If a setting is not specified in the CLI, the application will check for corresponding environment variables.
3. Configuration file: If a setting is not found in the CLI arguments or environment variables, the application will look into the configuration file.
4. Default values: If a setting is not specified in any of the above, default values are used.

Default Configuration File

• The default configuration file is located in the user's configuration directory, which varies by operating system:
  • Windows: C:\Users\<YourUserName>\.config\chrome-lens-py\config.json
  • Unix/Linux: /home/<YourUserName>/.config/chrome-lens-py/config.json
  • macOS: /Users/<YourUserName>/Library/Application Support/chrome-lens-py/config.json

Specifying a Custom Configuration File

• You can specify a custom configuration file using the --config-file flag:

  lens_scan --config-file path/to/your/config.json <image_source> <data_type>
  

• When a custom configuration file is specified, it is treated as read-only and will not be modified by the application.

Configuration Settings

The configuration file is a JSON file that can include the following settings:

• proxy: Specify a proxy server to route requests.

  {
    "proxy": "socks5://username:[e-mail]:1080"
  }
  

• cookies: Specify cookies to use with requests. This can be a path to a cookies file or a cookie string.

  {
    "cookies": "path/to/your/cookie_file.txt"
  }
  

  or

  {
    "cookies": "__Secure-ENID=17.SE=-dizH-; NID=511=---bcDwC4fo0--lgfi0n2-"
  }
  

• coordinate_format: Set the format of output coordinates. Acceptable values are "percent" or "pixels".

  {
    "coordinate_format": "pixels"
  }
  

• debug: Set the logging level. Acceptable values are "info" or "debug".

  {
    "debug": "debug"
  }
  

• data_type: Set the type of output data.

  {
    "data_type": "all"
  }
  

Complete Example Configuration File

Here is an example of a configuration file that includes all possible configuration parameters:

{
  "proxy": "socks5://username:[e-mail]:1080",
  "cookies": "path/to/your/cookie_file.txt",
  "coordinate_format": "pixels",
  "debug": "debug"
}

Updating the Configuration File

• To update the default configuration file with new settings from the CLI, use the -uc or --update-config flag.

  lens_scan <image_source> <data_type> [options] -uc
  

• Note: The configuration file will only be updated if it's the default configuration file (i.e., not specified via --config-file).

• Only specific settings will be updated:

  • Settings that can be updated:

    • coordinate_format
    • debug
    • data_type

  • Settings that will not be updated:

    • proxy
    • cookies
    • image_source

• This allows you to persist certain settings across runs without affecting critical configurations like proxy settings or cookies.

Example Usage

• Updating the coordinate format in the default configuration file:

  lens_scan path/to/image.jpg all --coordinate-format=pixels -uc
  

  • This command will set the coordinate format to pixels for the current run and update the default configuration file so that future runs will also use pixels as the coordinate format.

• Using a proxy without updating the configuration file:

  lens_scan path/to/image.jpg all -p socks5://127.0.0.1:2080
  

  • The proxy setting will be used for this run but will not be saved to the configuration file.

• Specifying a custom configuration file (read-only):

  lens_scan --config-file path/to/config.json path/to/image.jpg all
  

  • The application will use settings from the specified configuration file but will not modify it, even if the -uc flag is used.

Environment Variables

You can also specify settings via environment variables:

• LENS_SCAN_PROXY: Set the proxy server.

  export LENS_SCAN_PROXY="socks5://username:[e-mail]:1080"
  

• LENS_SCAN_COOKIES: Provide cookies.

  export LENS_SCAN_COOKIES="__Secure-ENID=17.SE=-dizH-; NID=511=---"
  

• LENS_SCAN_CONFIG_PATH: Specify a custom configuration file.

  export LENS_SCAN_CONFIG_PATH="path/to/your/config.json"
  

Project Structure

/chrome-lens-api-py
│
├── /src
│   ├── /chrome_lens_py
│   │   ├── __init__.py           # Package initialization
│   │   ├── constants.py          # Constants used in the project
│   │   ├── utils.py              # Utility functions
│   │   ├── image_processing.py   # Image processing module
│   │   ├── request_handler.py    # API request handling module
│   │   ├── text_processing.py    # Text processing module
│   │   ├── lens_api.py           # API interface for use in other scripts
│   │   └── main.py               # CLI tool entry point
│
├── setup.py                      # Installation setup
├── README.md                     # Project description and usage guide
└── requirements.txt              # Project dependencies

Acknowledgments

Special thanks to dimdenGD for the method of text extraction used in this project. You can check out their work on the chrome-lens-ocr repository. This project is inspired by their approach to leveraging Google Lens OCR functionality.

TODO

• Add scan by url
• Add output in pixels
• Move all methods from chrome-lens-ocr
  • cookie!?
• Do everything beautifully, and not like 400 lines of code, cut into modules by GPT chat
• Something else very, very important...

License

This project is licensed under the MIT License. See the LICENSE file for more details.

Disclaimer

This project is intended for educational purposes only. The use of Google Lens OCR functionality must comply with Google's Terms of Service. The author of this project is not responsible for any misuse of this software or for any consequences arising from its use. Users are solely responsible for ensuring that their use of this software complies with all applicable laws and regulations.

Author

Bropines - Mail / Telegram