Delhi's civic data infrastructure has a problem hiding in plain sight. Thousands of duplicate images — photographs of the same citizen, the same property, the same heritage structure — sit replicated across at least a dozen disconnected government databases, creating a logjam that delays everything from ration card renewals in Seelampur to property mutation approvals in Dwarka. The immediate question is not simply how the duplicates got there. It is what the Delhi government intends to do about it next, and who will bear the cost.
The issue has crystallised this year partly because Delhi is mid-stream on several large digitisation drives that are colliding with each other. The Delhi Metro Rail Corporation's Phase 4 corridor project requires fresh land acquisition records, complete with geotagged photographs of affected plots along the 65-kilometre network. Simultaneously, the Delhi Development Authority's updated master plan process is pulling satellite and street-level images of zones across the city. When those two databases talk to the same back-end storage systems maintained by the National Informatics Centre's Delhi state unit at CGO Complex in Lodhi Road, duplicates multiply rapidly.
What the Duplication Actually Costs
Storage is the easy metric. A single government agency managing civic records can accumulate redundant image files that inflate storage requirements by 30 to 40 percent, according to general benchmarks from the Ministry of Electronics and Information Technology's guidelines on data deduplication published in 2024. For Delhi, where the Municipal Corporation of Delhi alone administers records for nearly 11 million properties, that is not a trivial overhead. Cloud storage contracts for state government bodies have been pegged at rates between ₹2.50 and ₹4.80 per gigabyte per month under National Informatics Centre pricing schedules, meaning unchecked duplication quietly burns through budget allocations that departments rarely publicise.
The harder cost is bureaucratic. Citizens attempting to transfer property documents in localities like Lajpat Nagar and Rohini have encountered cases where two different photographs of the same address generate conflicting records, stalling approvals that should take days into waits stretching weeks. The Delhi Jal Board's customer portal, which handles connections across the city, has separately flagged mismatched identity photographs as a trigger for manual verification backlogs.
The Decisions That Cannot Wait
Three choices are now pressing. The first is whether to run a centralised deduplication exercise across all Delhi government image repositories simultaneously, or to do it agency by agency. A centralised approach requires coordination between the Delhi government's IT department, the MCD, the DDA, and the NIC — four bodies that do not share a single reporting line. An agency-by-agency rollout is slower but more politically manageable, particularly given the ongoing friction between the AAP-led state government and central bodies that answer to New Delhi's BJP-aligned ministries.
The second decision involves the audit trail. Deleting a duplicate image from a civic record is not as simple as pressing delete. Legal disputes over property, heritage status, and land use — a chronic feature of neighbourhoods from Shahjahanabad in Old Delhi to the resettlement colonies of Bawana — can hinge on photographic evidence held in official databases. Removing what looks like a duplicate could, without a comprehensive audit, erase the only surviving record of a structure at a specific point in time.
The third decision is procurement. An automated image-matching and deduplication system robust enough to handle the scale of Delhi's records would require a fresh tender. The last comparable contract — for digitisation of land records under the DILRMP scheme — took more than 14 months from notice to deployment.
The AAP government has until the end of this financial year, March 2027, to show measurable progress on its e-governance commitments or risk losing the narrative heading into the next budget cycle. Starting the deduplication process by October 2026 would leave a realistic window to demonstrate results. Failing to decide quickly means the duplicate files keep accumulating, the storage bills keep rising, and the citizen at the Seelampur ration office keeps waiting.