How Delhi's Public Records Ended Up Riddled With Duplicate Images — And Why Officials Are Only Now Scrambling to Fix It

Delhi's municipal and heritage databases contain tens of thousands of duplicate image files — the same photograph of a crumbling haveli in Shahjahanabad logged four times over, the same pothole on Outer Ring Road stored under three separate case numbers — and administrators at the Delhi Urban Shelter Improvement Board and the Archaeological Survey of India's Delhi Circle are now under pressure to clean up the mess before Phase 4 of the Delhi Metro project generates yet another wave of site-documentation photography.

The problem did not appear overnight. It accumulated across roughly twelve years of parallel digitisation drives launched by competing agencies that never spoke to each other. The Delhi government's own e-District portal, the Municipal Corporation of Delhi's property-tax image system, and the National Informatics Centre's Delhi node each built separate repositories with separate naming conventions, no shared metadata standard, and no automated deduplication tool. The result is institutional digital clutter on a scale that is now measurably slowing down planning approvals in areas like Lutyens' Delhi and the Walled City of Old Delhi, where heritage clearances require cross-referencing photographic evidence held across at least three different servers.

How the Duplication Crisis Grew

The first serious warning came in 2019, when the Delhi Development Authority's land-records digitisation wing flagged that roughly 34 percent of images uploaded during the 2014–2018 scanning drive for Lal Dora village boundaries were redundant copies — a figure cited in an internal DDA progress note that circulated among senior planners at the Vikas Sadan headquarters in INA. No corrective action followed. The 2020 lockdown then pushed every government department to accelerate digital filing, and staff working from homes in Dwarka and Rohini uploaded documents through whatever consumer-grade app was available, compounding the redundancy problem exponentially.

The Yamuna Rejuvenation Authority's monitoring cell, which photographs river-bank encroachments from Wazirabad Barrage down to Okhla, separately documented a storage crisis in a 2023 internal review: its image repository had ballooned to an estimated 2.1 terabytes, of which project managers believed a significant portion — though no precise verified figure has been made public — consisted of near-identical drone frames taken during overlapping survey passes. That review reportedly recommended adopting perceptual hashing software to flag duplicates before archiving, but procurement stalled.

Meanwhile, civil-society groups working in Chandni Chowk under the aegis of the Indian National Trust for Art and Cultural Heritage pressed the Delhi government repeatedly to establish a unified photographic standard for heritage documentation. Their concern was practical: when duplicate images carry different metadata tags — one file dated 2021, an identical file dated 2023 — it creates false evidence of change that can either inflate or deflate the case for conservation status. The Intach Delhi chapter submitted a formal representation to the Delhi Heritage Conservation Committee in March 2025 on precisely this point, though the committee's public minutes do not record a substantive response.

What Happens Now — and What It Costs

The Metro Phase 4 corridor, which cuts through sensitive zones including the Civil Lines neighbourhood and portions of the Trans-Yamuna area toward Janakpuri West, requires environmental and heritage photography at every stage of construction. The Delhi Metro Rail Corporation has indicated it will use its own in-house documentation team rather than relying on shared government repositories — a decision that insulates the project from existing database chaos but guarantees that yet another siloed archive will grow alongside the others.

Fixing the underlying problem requires more than software. Three things need to happen in sequence: agencies must agree on a shared metadata standard, a single nodal body must be designated to hold master copies, and legacy files must be processed through deduplication algorithms before any new material is ingested. IT consultants familiar with similar projects in Mumbai's municipal corporation and in Bengaluru's BBMP system estimate that a project of Delhi's scale — covering MCB, DDA, and ASI holdings together — could take 18 to 24 months and cost upward of several crore rupees depending on the volume of files ultimately catalogued.

For residents trying to push heritage applications through the South Delhi Municipal Corporation office in Mehrauli, or property owners waiting on title-deed verifications in Karol Bagh, the practical advice from legal aid groups is blunt: submit physical photographs alongside any digital filing, maintain your own dated, numbered archive, and do not assume that an image uploaded to a government portal has been correctly stored, cross-referenced, or preserved against future database merges.