Skip to content

Brute-force descriptor matching

Compare each query descriptor with every training descriptor using a chosen distance.

Try it on your image ↓

VISUAL WALKTHROUGHMatching
REFERENCE INPUTOne query, six descriptors

A short binary descriptor makes pairwise differences visible. Orange is the query; violet rows are candidates.

RESULTKeep the nearest candidates

The best match is evidence of similar appearance. Ambiguity filtering and geometric verification remain separate steps.

STEP 03 / 03

Filter ambiguous candidates and validate them with image geometry.

Illustrative example. The stages explain the method; they are not a live OpenCV execution.

Try it on an image

YOUR IMAGE · REAL OPENCV

Experiment at pixel level

Open full lab ↗

Compute ORB descriptors in both images, match using Hamming cross-check, and draw the best correspondences side by side.

The engine loads on your first run. Your images stay in this browser.

Input448 × 320
OutputWaiting for a result

Scroll over either image to zoom at the pointer. Use the scrollbars to pan both views over the same relative area. Zoom is relative to the input; pixel coordinates belong to each image. Warps can change scene correspondence.

Pixel inspector RGBA · native values · matched scale · 9 × 9 output pixels
Hover to inspect. Click to pin a pixel.
Input
Select a pixel

Output
Select a pixel

Sample models and licenses

When to use it

Establish candidate correspondences before estimating a geometric transformation.

How it works

  1. 01Compute descriptor distances.
  2. 02Select the nearest match or nearest k neighbours.
  3. 03Filter ambiguous candidates and validate them with image geometry.

best match = argmin descriptor distance

What to tune

Use L2 for floating descriptors, Hamming for ordinary binary descriptors, and Hamming2 for ORB configurations that require it.

Where it breaks down

A nearest descriptor is not automatically the same physical point. Use cross-checking, ratio tests where appropriate, and robust geometric verification.

TypeScript API

Open an entry for its exact overloads, parameter descriptions, result ownership and pinned upstream source.

All of these calls execute on the CPU. Native objects need explicit disposal. See matrices and ownership and build compatibility.