Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Introduction

In this article, you will find additional information and best practices for data capture with Anyline. For any comments or questions, please get in touch with your contact person at Anyline.


Quality Drivers

Challenging conditions and tire degradations can lead to a suboptimal scanning performance. This can be reflected through lower scan accuracy or a longer time needed to complete a successful scan result. Below, you will find a list of the most common factors which can be the cause of suboptimal scanning performance.

A very simple rule applies for all quality drivers in general: “If the human eye can’t read the text, the technology will most likely struggle too.”

Conditions and Factors

Correct Practice

Incorrect Practice

Good and Consistent Lighting Conditions

Low light reduces the contrast of the image, making it harder to separate the characters from the background.

Make sure that the image was taken under good and consistent lighting conditions. Avoid shadows or reflections in the image.

Camera Positioning

To achieve more accurate results and a better overall scanning experience, please ensure that the image has the tire directly in line and not angled incorrectly. If the angle is too low or too high, the characters may not be as clear to get an accurate read.

Also, avoid using angles where any textured backgrounds could surround the scannable area.

Focus

Make sure that the focus of the shot is on the tire. Improper focus caused by a poor auto-focus or incorrect handling will result in a blurry image.

Likewise, make sure that no strong image compression is applied to the image. As a rule of thumb, the DOT number must still be readable after zooming in on the image.

Distance

Dirt can affect the scanner in various ways. If dirt partially or fully covers characters, they may be misread, or not detected at all (leading to no result).

In that case, try to remove the dirt from the tire and scan again.

Tire Positioning

Position the tire in the centre of the image, making sure that the tire is completely in the image and not cut off. Make sure that only one tire is visible in the image. The image should be taken as parallel as possible to the tire.

Make sure that the background of the shot is as neutral as possible and that the tire stands out well against the background. Avoid particularly bright objects in the background or backlighting.

Dirt and Damages

Make sure that relevant information on the tire is clearly visible and not covered by dirt. Damage that makes relevant information unreadable will degrade the reading rate.

Some Extra Tips:

  • The resolution of the camera directly influences how much information is available to be processed by the recognition system. The higher the resolution of the camera, the higher the probability of more accurate result.

  • Make sure that the images are not larger than 8 MB.


Video Examples

Below, you will find a comparison between two video examples with one showing how to correctly use the Cloud API and the other showing the incorrect way to use the Cloud API:

RPReplay_Final1691066077.MP4RPReplay_Final1691066146.MP4


Integration Tips for both E-Commerce and Tire Hotel Applications

To ensure that you give your website visitors the best user experience and at the same time increase your conversion rate, we recommend you take into consideration the following tips:

 Guide your users to take good pictures

Make sure your users are taking good pictures. For example, show good and bad examples, or show an instruction video before they take the image in the process. Since the method of capturing (described in the "Quality Drivers" section) has a great influence on the quality of the results, it is important to instruct the users well.

Among other things, you can place an overlay of a tire over the camera stream in the image capture process that will help both your website visitors and workers to aim correctly and therefore take the perfect picture. This can increase the likelihood that you gather all tire sidewall info.

Our Anyline experts are happy to consult you during the integration process to ensure the best possible user experience for your users.

 Define a confidence level

After a photo is taken, uploaded and processed we will give you a confidence level for each detected item (DOT/TIN, Tire Size, Tire Make & Model). This confidence score shows you how accurate our Cloud API is and that we have scanned the right values for each item. You may configure it so that if we provide a confidence score below a certain threshold, you remove this item from the result screen on your website or avoid showing this in your application. Another option is to mark the low confidence values as "unconfident" in your user interface, so that the user has to pro-actively reconfirm them before continuing with the process.
Please see following examples below:

Example 1:
After the user takes a photo of a tire, the Cloud API returns DOT/TIN with 100% confidence, Tire Size with 98% confidence, Tire Model with 68% confidence and Tire Manufacturer with 97% confidence.
In this case, you could remove Tire Model from showing up as it has less than a 90% confidence score.

Example 2:
After the user takes a photo of a tire, the Cloud API returns DOT/TIN with 68% confidence,
Tire Size with 0% confidence, Tire Model with 20% confidence and Tire Manufacturer with 60% confidence.
In this case, it is likely that the user has not taken a good image and you should ask them to take the image again.

We also recommend that you set the confidence score to at least 90%. 

 Show only relevant information

It is completely up to you to use or display only the information that is required for your use case. To optimise the user experience of your application, you should only use the information that is actually needed.


Links to Documentation

If you require any further information or details on our Tire Sidewall Data Capturing Module (on Cloud API), please click here to see our documentation page: https://documentation.anyline.com/main-component/index.html

  • No labels