Custom OCR

Scan capability overview

With the Custom OCR scan capability, you have the ability to create your own OCR use case, on the fly with almost no effort. It offers a variety of parameters for you to adjust the scanning process to your use case.

It allows you to scan uppercase alphanumeric codes, so you can quickly identify any devices, machinery, building infrastructure, installations, etc.

You can easily customize it in order to optimize for your specific use case by adding a character whitelist, a regular expression and more.

Parameters

Custom Scripts & Models

You might receive custom files of type .any and .ale from Anyline which are tailored to your specific requirements. Our custom format .ale and .any files are encrypted resource files containing the instructions for processing your custom use.

{
  "ocrConfig": {
    "customCmdFile": "path/to/the/script.ale", (1)
    "models": [ "path/to/model1.any", "path/to/model2.any" ] (2)
  }
}
1 customCmdFile is the parameter to set a custom Anyline script. A custom script is created by the Anyline engineers for your tailored use-case, and may require a model or multiple models depending on that solution. You will receive your specific integration instructions alongside the resources by Anyline.
2 with models you can set multiple Anyline models for your specific use-case. As mentioned, the models to set depend on the solution offered to you by Anyline and you will receive specific integration instructions for this feature.
Without a custom script, you can only use up to one custom model.

Integrating the files in your project

The Anyline scripts & models need to be added to your project as a resource so that they will be deployed alongside your application. The relative path and resource type depend on the platform, for example, for Android, the root path points to src/main/assets/ of your project. For Windows, this path points to the root of the project.

Plugin configuration and result

Plugin configuration

  • Find the PluginConfig parameters here.

Plugin result

  • Find the PluginResult parameters here.