What is re-identification (ReID)?

What is re-identification?

Re-identification answers whether two sightings, perhaps from different cameras or minutes apart, are the same individual object or person. Rather than assigning a fixed class, ReID compares learned appearance representations and decides which observations belong to the same identity. It must cope with changes in pose, lighting, viewpoint, and partial occlusion.

It is what lets a multi-camera system maintain consistent identities across gaps in coverage.

Key takeaways

ReID matches the same instance across cameras or over time.
It relies on appearance embeddings, not a fixed label set.
It must handle changes in pose, lighting, and viewpoint.

How it works

A model maps each detected object or person to an embedding, so that images of the same identity land close together and different identities land far apart, typically learned with contrastive or metric-learning objectives. At query time, a new observation is matched to known identities by embedding similarity. ReID is frequently paired with tracking to reconnect objects after they are occluded or leave and re-enter the frame.

Why it matters

Real deployments span many cameras and long time spans, and ReID is what keeps identities consistent across them, which is essential for multi-camera tracking and analytics. Because it is embedding-based, it connects directly to the representation-learning and similarity-search techniques used across visual AI.

Frequently asked questions

How is ReID different from classification?

Classification assigns a fixed category, while ReID matches specific instances by appearance similarity, even for identities never seen during training.

How does ReID relate to multi-object tracking?

Tracking follows objects within a view, and ReID helps re-associate them across cameras or after occlusions, keeping identities consistent.

Jesse Mostipak is the SEO and Content Manager at Voxel51, where the work is helping humans find and trust what the brand knows, and teaching the Google knowledge graph and the LLMs answering on their behalf to do the same. That question, how knowledge gets built inside a system, is one Jesse has been chasing for years. Earlier versions of it ran through a New York City high school science classroom, data science and machine learning, and developer relations at Kaggle, Posit (formerly RStudio), and Baseten. The answer doesn't change much depending on whether the learner is a teenager, a software engineer, or a knowledge graph. Jesse holds a Master's in Education from CUNY Hunter College. LinkedIn

Re-identification

Building visual or physical AI? 
Let's talk.