Delhi's municipal and state government servers are carrying tens of thousands of duplicate photographs — the same faces, the same building facades, the same potholed lanes filed and re-filed across incompatible systems — and the mess has been quietly accumulating since at least 2009, when the city's various agencies first began digitising their paper records in earnest.
The problem matters now because Delhi is in the middle of rolling out Phase 4 of its Metro expansion, with new corridors cutting through Janakpuri, Inderlok, and Tughlakabad, and every land acquisition, heritage survey, and displaced-vendor record requires verified photographic documentation. When the same image sits in three separate databases under three different reference numbers, the verification chain breaks down, approvals stall, and projects slip.
How the Duplication Happened
The root cause is structural. The Delhi Development Authority, the Municipal Corporation of Delhi, and the Delhi government's own Directorate of Information and Publicity each built their own digital repositories in separate phases, using different software vendors and different metadata standards. None of the three systems talked to each other. A photograph taken at a heritage property survey in Shahjahanabad — the dense, historically layered neighbourhood that tourists know as Old Delhi — might be uploaded by a DDA field officer, then re-uploaded by an MCD ward official, then scanned again from a printed copy by a state government archivist. Three entries. One image. No flag.
The Delhi Secretariat at ITO has been aware of the redundancy problem since at least a 2019 internal audit, according to public procurement records visible on the Central Public Procurement Portal. That audit recommended a unified digital asset management system, but the tender was cancelled twice — once in 2020 during the Covid-19 lockdown and once in 2022 amid a budget dispute between the AAP state government and the BJP-controlled central agencies that oversee several Delhi land bodies.
The Yamuna riverfront redevelopment files illustrate the scale precisely. The stretch between the Signature Bridge in Wazirabad and the Nizamuddin Bridge has been surveyed photographically at least six times since 2015 by different agencies, each producing its own image archive. Cross-referencing those archives to produce a single clean record for the current cleanup project, administered under the Delhi Jal Board, has taken contractors an estimated four months longer than originally scheduled, according to procurement timelines published by the DJB in March 2026.
What a Fix Actually Requires
Digital archivists who work with large municipal bodies say the technical solution is not complicated — automated perceptual hashing can identify near-identical images in hours — but the political solution is. Each agency has guarded its own data infrastructure as a budget line and a bureaucratic turf. Merging them means one department loses headcount or procurement authority, and in Delhi's fractious inter-agency environment, that negotiation has repeatedly stalled.
The Delhi government floated a fresh Request for Proposal in February 2026 for a unified Digital Asset Management System, with a stated budget ceiling of ₹34 crore over three years. The deadline for bids closed on 30 April 2026. As of this week, no award has been publicly announced on the CPPP portal.
For residents and small businesses, the practical consequences show up in delays at the Delhi e-District portal, where property mutation requests and trader-licence renewals require photographic identity verification. When backend image databases are inconsistent, the automated matching fails and applicants are sent back to resubmit documents they have already filed — sometimes multiple times.
The immediate pressure is the Metro Phase 4 timeline. The Delhi Metro Rail Corporation has set an internal target of completing land-record digitalisation for the Janakpuri West to Krishna Park Extension corridor by September 2026. If the state government's image-database tender remains unawarded through July and August, that corridor's documentation window narrows sharply. The fix exists. The question is whether three agencies and two governments can agree on who runs it before the deadline forces the answer.