About TriNetra
A city-wide answer to one question: where has this vehicle been, and what does that mean for the roads around it right now.
What TriNetra is
TriNetra reads every automatic number plate recognition (ANPR) camera in a city as one system rather than as a set of independent feeds. A plate seen at one camera and again at another six kilometres away becomes a single trajectory, drawn along the real road network the vehicle actually took — not a straight line between two points on a map. That trajectory feeds three linked engines: Smriti, the recorded past; Drishti, live conditions now; and Bhavishya, a short-horizon forecast of what the road network does next. Every query any of them answers is written to an accountability ledger that cannot be edited after the fact.
The problem it addresses
A city's traffic police and municipal planners typically hold camera footage, but not a joined-up record of where any one vehicle has been. Investigators build a vehicle's movements by hand, camera by camera. Planners see congestion after it forms rather than as it forms. TriNetra closes that gap: plate sightings become identities, identities become trajectories, and trajectories become origin-destination flow, junction health, and closure impact — all read from one dataset instead of four disconnected tools.
Built for SIH26127
TriNetra was built against problem statement SIH26127 — city-wide ANPR trajectory and urban traffic analytics — set by Bharat Electronics Limited for Smart India Hackathon. The reference deployment runs against New Delhi's road network: 45 cameras and a 7,362-edge street graph, used to validate that trajectories, forecasts and closure simulations all hold against a real city rather than a synthetic grid.
Who uses it
The console is a single instrument read by five roles, each seeing only what its work requires: patrol (live camera and vehicle density), investigator (trajectory search and review), analyst (forecasting and the digital twin), auditor (the accountability ledger), and super_admin (all of the above). Role boundaries are enforced on the server, not just hidden in the interface — see how it works for the accountability model behind that.