Table of Contents

Image recognition difficulty rating

Before formally adding images to the cloud recognition (CRS) gallery, best practice is to conduct a pre-evaluation of their quality.

If the target image has insufficient recognizable areas (such as white walls or solid color blocks) or overly simplistic textures, its recognition success rate will significantly decrease. This chapter details CRS's rating mechanism to help you select high-quality AR recognition materials.

Rating mechanism and score meaning

Score Evaluation Suggestion
0 - 1 Excellent Extremely rich texture, fast recognition speed, highly stable tracking.
2 Good Sufficient feature points for normal AR operations.
3 Average Recognition rate may be affected by lighting or angles; texture optimization recommended.
4 Poor Extremely difficult to recognize; not recommended for production environment.
-1 Error Unsupported image format or corrupted file.
Important

Actual testing principle: If the image gallery contains a small number of targets, higher-rated images may still work in specific environments. Real-device testing should be the ultimate criterion.

Core comprehensive indicators

We primarily focus on the following two comprehensive indicators, each with its own dedicated API interface providing an overall rating:

  • DetectableRate comprehensive level (detectableRate):

    • The most core indicator. Determines the success rate of cloud-based "image search".
    • The comprehensive rating provided by the /grade/detection API interface
  • TrackableRate comprehensive level (trackableRate):

    • If you use the EasyAR Sense SDK for local tracking in Unity/App, this indicator determines the stability of AR content overlay.
    • The comprehensive rating provided by the /grade/tracking API interface

Other detail metrics

  • detectableDistinctiveness
  • detectableFeatureCount
  • trackableDistinctiveness
  • trackableFeatureCount
  • trackableFeatureDistribution
  • trackablePatchContrast
  • trackablePatchAmbiguity

These metrics are rated from an image algorithm dimension, with each metric still scored on a difficulty scale from 0 to 4.

How to browse rating results

Detailed ratings for each target image in the database are available on the target image detail page. You can view them either through the API when retrieving target image attributes, or through the EasyAR cloud recognition management platform.

View through EasyAR web

  • Log in to EasyAR web and enter the development center
  • Cloud recognition management
  • Select the activated image library
  • Click Manage to enter image library management
  • Select the target image
  • Click Manage to view details of the target image.

As shown below, the details page displays two core comprehensive metrics, and a five-pointed shape presents five detailed metrics.

  • Detectability: Corresponds to a five-star rating based on the original comprehensive detection difficulty score (detectableRate). A lower original difficulty score yields more stars, indicating easier detection.
  • Trackability: Corresponds to a five-star rating based on the original comprehensive tracking difficulty score (trackableRate). A lower original difficulty score yields more stars, indicating easier tracking.

detail

API rating results —— Target list interface

Through the Target list interface or by retrieving details, you can obtain all detailed algorithm metrics for each target image (including detectableRate, texture distribution, feature point count, etc.).

Best practices: API pre-rating

When building an automated upload backend, it is recommended to call the rating interface before the actual upload.

Reference documentation: Image recognition difficulty rating API interface

Rating interface classification

  1. Detection rating (/grade/detection):Only returns detection difficulty. (Most commonly used)
  2. Tracking rating (/grade/tracking):Only returns tracking difficulty.
  3. Detailed rating (/grade/detail):Returns multi-dimensional metrics for reference by professional algorithm developers.

Preparation for invocation

  • Preparation checklist is as follows. For preparation details, refer to Invocation Preparation Checklist

    • CRS AppId
    • Authentication credentials: API Key / API Secret or Token
    • Server-end URL: Target image management URL address, using port 443 for https
    • Test image: JPEG/PNG format, size must not exceed 2 MB
  • First convert the local target image to Base64 (macOS/Linux), save the result to image_base64.txt
base64 -i ./target.jpg | tr -d '\n' > image_base64.txt
  • Replace placeholders with actual parameters and run the curl script
    • Your-Server-side-URL → Actual API Host
    • Your-Token → Actual API Key Authorization Token
    • Your-CRS-AppId → Your appId
curl -X POST "https://<Your-Server-side-URL>/grade/detail" \
  -H "Content-Type: application/json" \
  -H "Authorization: <YOUR-TOKEN>" \
  -d '{
    "appId": "<Your-CRS-AppId>",
    "image": "'"$(cat image_base64.txt)"'"
  }'

Related topics:

Next topic: