Washington DC's Duplicate Image Problem: How the Capital Stacks Up Against London, Seoul and São Paulo

Washington DC's Office of the Chief Technology Officer is midway through a citywide audit of government-facing digital assets, working to identify and remove duplicate images embedded across agencies ranging from the Department of Motor Vehicles on C Street NW to the DC Department of Buildings permit portal. The problem is neither glamorous nor new, but the cost of ignoring it — in server overhead, misfiled records, and delayed permitting decisions — has become harder to justify as the city faces federal funding uncertainty tied to the Trump administration's DOGE-driven restructuring of the broader federal workforce.

Duplicate image accumulation typically happens the same way in every city: staff upload photos of properties, vehicles, or individuals multiple times across disconnected legacy systems, and without automated deduplication tools, the redundant files sit unchecked for years. For DC, the stakes are higher than in most American cities because so many municipal data systems are intertwined with federal databases. When federal agencies purge or migrate records — as has happened repeatedly since early 2025 — orphaned image files proliferate on the city side, creating mismatches that slow down everything from housing inspections in Anacostia to business license renewals along H Street NE.

A Problem Other Cities Solved Differently

London's Government Digital Service began a similar deduplication initiative in 2021, ultimately reducing redundant image files across the Greater London Authority's property-facing systems by roughly 34 percent over 18 months, according to figures published in the GLA's 2023 digital infrastructure review. Seoul, operating through its Smart City data center in the Sangam Digital Media City district, deployed a hash-based automated deduplication layer in 2022, cutting storage costs across municipal portals. São Paulo's city technology secretariat has taken a different approach, contracting private vendors to audit legacy systems ahead of broader cloud migration rather than building the tooling in-house.

DC's approach looks closer to London's model than to Seoul's. The OCTO has been working with the DC Geographic Information System program, based out of 1100 4th Street SW, to cross-reference property image records using metadata matching rather than full hash comparison — a less computationally intensive method suited to the city's older server infrastructure. The effort is folded into the broader DC Data Strategy, a framework the Bowser administration has been advancing since at least 2023. Progress has been uneven. Agencies with newer content management systems, such as the Office of Planning, have found the audit relatively straightforward. Agencies still running Windows Server 2012-era environments have not.

What the DOGE Effect Is Actually Doing to DC's Data Layer

The timing matters. Since January 2025, the federal government's efficiency-cutting initiative has resulted in significant workforce reductions at agencies that historically provided informal technical support to city systems — particularly at GSA, which manages shared government technology contracts affecting both federal and DC municipal operations. When those liaison relationships fray, duplicate records compound faster. The NoMa neighborhood's rapid development has added pressure as well: the DC Department of Buildings processed a record volume of permit applications in that corridor through 2025, and inspectors have flagged instances of inspection photographs being uploaded multiple times to different case files, requiring manual reconciliation.

Philadelphia and Baltimore, cities facing comparable legacy infrastructure constraints, have each launched partial deduplication efforts in recent years, though neither has completed a system-wide audit. Philadelphia's Streets Department began a targeted image cleanup of its pavement marking database in March 2025. Baltimore's approach has been ad hoc, addressed piecemeal during individual system migrations rather than through any unified program.

For DC residents and contractors who use city digital portals — whether pulling property records at the Recorder of Deeds office on Pennsylvania Avenue or checking permit status through the DC OneStop portal — the practical upshot is that search results and record retrieval should become more accurate as the audit progresses. The OCTO has indicated the current phase of the audit is scheduled for completion before the end of fiscal year 2026, which closes September 30. Anyone who spots mismatched or duplicated images in a city record can flag the issue directly through the DC 311 service request system, which routes technology complaints to the relevant agency.