TDI — Re-ID technical guide: hardware, data types & project planning
This article covers the technical details of TDI Re-ID deployments — what hardware is needed, what data is produced, and how to plan a Re-ID project. Source: TDI EMEA Wiki R&D Center.
Re-ID hardware requirements
Re-ID requires a TD4001 Edge AI Computing Unit paired with compatible sensors. The TD4001 processes all Re-ID locally at the edge — no cloud required.
TD4001 T2 | 1–4 sensors. <500 unique visitors/day. Small stores. |
TD4001 T6 | 5–8 sensors. <1,000 unique visitors/day. Medium stores / food & beverage. |
TD4001 T21 / G2 | 9–16 sensors. <5,000 unique visitors/day. Large stores, department stores. |
TD4001 Custom | Unlimited sensors. Shopping malls, airports, large campuses. |
Re-ID is NOT supported on TD2000B series (only TD2000 G2/G3 and TD1501/TD1502 series). Always verify the sensor model supports Re-ID before quoting a Re-ID project.
Re-ID compatible sensors
TD2000 G2 | ✅ Re-ID supported |
TD2000 G3 | ✅ Re-ID supported |
TD1501 G1 / G2 | ✅ Re-ID supported (tilt-view) |
TD1502 / TD1502 G2 | ✅ Re-ID supported (vertical-view) |
TD2000B / B G2 / B G3 | ❌ No Re-ID |
TD1001 / TD1002 | ❌ No Re-ID |
Re-ID data types
With Re-ID enabled, the system produces two additional data streams beyond basic counting:
1. Track Data (heatmaps and path analysis)
Real-time X/Y trajectory coordinates of every person tracked
Used to build heatmaps showing where people spend time
Used for path flow analysis — which route did visitors follow?
Stored per identity over their full visit duration
2. Body Data (person attributes)
Age estimation, gender estimation, clothing colour
Used by the Re-ID engine to match the same person across different cameras
No facial data — privacy compliant
Assigned anonymously to each Re-ID identity
What Re-ID enables per use case
Daily footfall | ✅ Basic counting — no Re-ID needed |
Peak hour analysis | ✅ Basic counting — no Re-ID needed |
Unique visitor count | ✅ Re-ID required |
Customer journey tracking | ✅ Re-ID required |
Heatmap visualisation | ✅ Re-ID required (Track Data) |
Repeat visitor detection | ✅ Re-ID required |
Cross-camera tracking | ✅ Re-ID required |
Average dwell time | ✅ Available without Re-ID on 3D sensors (Dwell Statistics) |
Data output format
TDI sensors output data in XML format via HTTP/FTP push or API pull. Vemtrack receives and processes this data. Key data structures:
Basic traffic counting (all sensors, no GPU needed)
Fields: Enters, Exits, StartTime, EndTime per zone and time interval. 3D sensors with extensions also provide EntersFemaleCustomer, EntersMaleCustomer, EntersStaff, EntersIndividual.
Dwell statistics (3D sensors, no GPU needed)
Fields: NumberServed, SecondsOccupied, TotalSecondsOccupied per zone. Also provides per-person dwell records with exact entry/exit timestamps and duration in seconds.
Re-ID data (GPU required)
Per unique identity: assigned UUID, appearance attributes (age, gender, clothing colour), full movement trajectory (X/Y coordinates from all cameras), entry/exit timestamps per camera, total visit duration. This data powers unique visitor reports, journey maps, and heatmaps in Vemtrack.
Planning a Re-ID project
Count entrances — how many camera positions are needed to cover all entrances and key zones?
Estimate daily traffic — how many unique visitors per day? Use this to size the TD4001 model.
Select sensors — use TD2000 G3 for ceiling-mount, TD1501 G2 for tilt-mount or where ceiling access is limited
Size the TD4001 — match model to sensor count and daily traffic capacity (see table above)
Use planning tools — TD1501 Re-ID Design Tool and Coverage Calculators are available in the TDI wiki Tools section
Validate Re-ID accuracy — use the Re-ID Accuracy Analysis Tool post-deployment. TDI also offers a paid Re-ID Validation Report service.
TrafficPro — TDI analytics platform
Traffic Pro is TDI's standalone analytics platform — separate from Vemtrack — used for direct data visualisation from TDI sensors. Two versions available:
TrafficPro Retail 3.0 | Single store analytics — footfall, gender, age, group counting, virtual zone analysis, email alerts |
TrafficPro Mall 3.0 | Shopping mall version — multi-store, mall-level analytics, tenant reporting |
For Vemco Group deployments, Vemtrack is the primary platform and TrafficPro is not typically needed unless the customer specifically requests it.
TDI wiki resources (partner login required)
Re-ID & Heatmap Deployment Playbook | 4.8MB PDF — complete Re-ID deployment methodology |
Re-ID Accuracy Analysis Tool | Excel tool for post-deployment accuracy validation |
TD1501 Re-ID Design Tool | Pre-deployment planning for TD1501 Re-ID projects |
Heatmap Mapping Tool | For TD4001/TD1501 heatmap visualisation setup |
Re-ID PoC Checklist | Excel checklist for Proof of Concept deployments |
R&D Center | Full API documentation — Device API, TrafficPro API, XML protocol, Re-ID data pipeline |
7PM
GMT+2
7PM
GMT+2
7PM
GMT+2
Who We Are
Aliquam Dui Diam, Tincidunt Eget Nulla Eget, Dictum Feugiat Felis. Cras Mattis Eget Tellus Quis Fringilla. Morbi Molestie Enim
Sed dictum ligula luctus intum Vivamus.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Lorem ipsum dolor
Sed quis massa leo. Quisque tristique tellus sit amet arcu tempor ultrices. Nulla ullamcorper.
Become Our Supplier Or Partner
Mauris tempor libero massa, at vulputate velit aliquet eget. Fusce et tortor ex. Nullam venenatis, quam vel blandit molestie.
