How Delhi's Public Record Archives Ended Up Flooded With Duplicate Images — And What's Being Done to Fix It

Delhi's municipal digitisation effort has a duplication problem. Thousands of photographs catalogued across at least three separate government portals — the Delhi Urban Shelter Improvement Board's asset registry, the Delhi Development Authority's GIS mapping platform, and the Smart Cities Mission node managed out of the Indraprastha Estate offices — contain duplicate or near-identical image files that are inflating storage costs, slowing database queries, and in several cases attaching the wrong visual record to the wrong property or project site.

The problem matters now because Phase 4 of the Delhi Metro expansion, which cuts through Janakpuri West, Lajpat Nagar, and Tughlakabad, requires accurate geo-tagged photographic documentation at each construction stage. Duplicate images — sometimes the same site photograph uploaded under different file names to satisfy separate departmental checklists — have created version-control conflicts that delay sign-off on civil works clearances. Add to this the Yamuna Riverfront redevelopment corridor, where photographic evidence of pre-construction conditions is legally significant for environmental compliance, and the stakes of a bloated, disorganised image archive become obvious.

How the Duplication Crisis Built Up Over a Decade

The roots go back to 2014-15, when the then-state government and the Delhi Municipal Corporation each launched independent scanning and photography drives for property tax records. Neither drive used a common file-naming protocol. The Municipal Corporation of Delhi — before its three-way reunification in May 2022 — operated through the North, South, and East DMC branches, each maintaining its own server infrastructure in offices at Civil Lines, Sarojini Nagar, and Patparganj respectively. When those three arms were merged into the unified MCD, their image repositories were aggregated rather than deduplicated, effectively tripling the redundancy problem overnight.

A 2023 audit conducted under the MCD's internal IT review — the findings of which were tabled at a standing committee meeting but have not been publicly released in full — reportedly flagged that duplicate records accounted for a significant share of storage consumption across the merged archive. Similar fragmentation plagues the Delhi Jal Board's photographic logs for the Yamuna Action Plan infrastructure, where site photographs from contractors working along the Najafgarh drain corridor were uploaded separately to both the Jal Board portal and the National Mission for Clean Ganga dashboard maintained by the Ministry of Jal Shakti in New Delhi.

The technical cause is straightforward: no single hashing or fingerprinting standard was ever mandated across agencies. A 2021 directive from the Delhi government's Department of Information Technology recommended adoption of SHA-256 checksums for all newly uploaded civic images, but implementation was left to individual departments with no enforcement mechanism attached to the order.

What Cleanup Looks Like in Practice

The Delhi Smart Cities initiative, operating from its coordination office near India Gate, has piloted a deduplication tool on a subset of roughly 40,000 heritage-site photographs collected under the Shahjahanabad redevelopment project in Old Delhi. The pilot, which ran through the first quarter of 2026, used perceptual hashing — a technique that identifies visually similar images even when file metadata differs — and reportedly reduced the active image count in that subset by close to a third, according to project documentation reviewed by The Daily Delhi.

For ordinary Delhiites, the practical consequence of getting this right is faster processing of property documentation requests at Sub-Registrar offices in areas like Rohini and Dwarka, where photo evidence is cross-referenced during mutation and transfer approvals. Delays tied to mismatched image records have added days to routine transactions at some district offices.

The next pressure point is December 2026, when the MCD's current server contract with its infrastructure provider comes up for renewal. IT officials want a leaner, deduplicated archive before that renegotiation, because storage volume directly determines licensing costs. Without a coordinated cleanup across all agencies — including the DDA, Delhi Jal Board, and the Metro's civil documentation teams — the problem will simply be contracted out at greater expense rather than solved. The city has the technical tools. The gap remains governance: getting a dozen departments to agree on one standard before the invoice arrives.