How Delhi's Digital Archives Became a Graveyard of Duplicate Images — And What's Being Done to Fix It

Delhi's public record system is drowning in copies of itself. Across at least three separate digitisation initiatives run by different arms of the Delhi government between 2018 and 2024, the same photographs, scanned maps and satellite images were uploaded repeatedly into incompatible databases — creating a sprawl of duplicate files that administrators, urban planners and journalists have spent years trying to navigate. The problem is not abstract: it has delayed heritage documentation in Old Delhi, slowed environmental assessments along the Yamuna floodplain and complicated infrastructure planning for Delhi Metro Phase 4 corridor work.

The issue matters urgently now because the Delhi government's consolidated e-governance portal — the Unified Delhi Data Repository, announced in the 2025-26 budget cycle — is scheduled to go live before the end of this financial year. Before that happens, technical teams must decide which images are canonical records and which are redundant noise. Getting it wrong means legally binding planning documents could reference superseded imagery, a problem that urban land lawyers describe as a litigation time-bomb waiting to detonate.

Three Schemes, No Shared Standard

The duplication crisis has a traceable origin. The Delhi Heritage Conservation Committee, operating out of offices near Kashmere Gate, ran its own photographic survey of 1,655 listed structures in Old Delhi between 2019 and 2021. Simultaneously, the Delhi Development Authority launched a separate GIS mapping programme covering the same geography. The Municipal Corporation of Delhi — then still divided into three bodies before its reunification in May 2022 — ran a third digitisation drive focused on building-permission records in areas including Chandni Chowk and Darya Ganj. None of the three programmes used a common file-naming protocol or a shared image metadata standard. The result was that photographs of landmarks such as the Jama Masjid precinct and the Fatehpuri Masjid streetscape appeared in all three databases under different filenames, different resolution settings and, in some cases, different geotagging coordinates.

The MCD reunification in 2022 was supposed to consolidate civic data, but the technical merger of the three corporations' digital holdings has moved slowly. As of early 2026, officials familiar with the process have indicated that duplicate-image resolution across the combined MCD database alone runs into tens of thousands of individual files — though no audited figure has been made public. Each unresolved duplicate adds to storage costs billed against the Delhi government's IT budget, which was pegged at roughly Rs 1,247 crore in the 2025-26 Union Budget allocation to the National Capital Territory.

The Yamuna Factor and What Comes Next

The practical consequences sharpened around the Yamuna cleanup debate. The Delhi Jal Board's photographic evidence base — used to track encroachment and sewage outfall points along the riverbank from Wazirabad Barrage down to Okhla — contains imagery that researchers at IIT Delhi's Centre for Urban Science and Engineering flagged in a 2024 internal review as containing significant duplication, with some riverbank sections photographed under as many as four separate project codes. When the same image appears under multiple project identifiers, establishing a chronological baseline for environmental change becomes unreliable, which matters enormously when the Yamuna cleanup is a political flashpoint between the AAP government at the Delhi Secretariat and central ministries on Raisina Hill.

Delhi Metro Rail Corporation's Phase 4 corridor planning, which covers new lines through Janakpuri West, Tughlakabad and R.K. Ashram Marg, has also required planners to cross-reference satellite and ground-level imagery from multiple earlier DMRC surveys. Duplicate or mislabelled images have required manual verification at several alignment-sensitive points along the proposed routes, adding weeks to individual site-assessment timelines.

The Unified Delhi Data Repository team is now piloting an automated duplicate-detection algorithm across heritage and land-use image sets, starting with a test batch covering the Shahjahanabad zone. Administrators advise departments that still maintain standalone image archives — particularly zonal offices in South Delhi and East Delhi — to hold off on any fresh uploads until the deduplication protocol is formally gazetted, expected in the October-November 2026 window. For citizens and researchers accessing public records through the Delhi e-District portal, the practical advice is simpler: cross-check any imagery-based document against its upload date and the originating department code before treating it as a current reference.