DC Lags Behind London and Seoul in Tackling Duplicate Image Sprawl Across City Databases

Washington DC's Office of the Chief Technology Officer is sitting on an estimated backlog of hundreds of thousands of duplicate images spread across at least four separate municipal databases, according to city procurement documents reviewed this spring. The redundancy is costing the District in server storage contracts and slowing down public-facing services from permit processing in NoMa to housing inspections in Anacostia — and peer cities overseas have moved faster to clean it up.

The issue has sharpened this year partly because of cascading disruptions from the Trump administration's Department of Government Efficiency restructuring. Federal agencies that historically shared data infrastructure with District systems — including the General Services Administration's regional offices on F Street NW — have pulled back on joint data-management agreements. That has pushed DC's own technology office to audit what it actually holds, and what it holds twice, three times, or more.

How Other Cities Are Handling It

London's Government Digital Service began a systematic deduplication sweep of its planning and licensing image archives in 2023, contracting with a specialist data firm to reduce redundant files across 33 borough councils. Seoul's Smart City Division launched a parallel effort through its Digital Mayor's Office in late 2024, targeting street-level imagery used in zoning and infrastructure planning. Both programs set measurable targets: London aimed to cut duplicate records by 40 percent within 18 months; Seoul's initiative focused on images tagged to specific geographic coordinates, where duplication rates in some districts reportedly ran above 60 percent before remediation began.

Amsterdam took a different approach, embedding deduplication protocols directly into its intake workflow for new permit images starting in January 2025, so the problem stops accumulating rather than requiring periodic clean-up campaigns. Berlin's Senate Department for Urban Development adopted similar intake rules the same quarter. DC has no equivalent intake standard currently in place.

That gap matters because Washington is adding new visual data constantly. The District Department of Transportation's MoveDC program, the DC Historic Preservation Office's ongoing survey work in neighborhoods like Capitol Hill and Shaw, and the Office of Planning's Comprehensive Plan implementation all generate photographic records. Without deduplication at the point of entry, each of those streams compounds the backlog.

What DC Is — and Isn't — Doing

The DC Office of the Chief Technology Officer has a data governance framework, the District's Data Policy, last updated in 2021, that acknowledges the problem in general terms but sets no binding timelines or reduction targets for image-specific duplication. A fiscal year 2026 technology modernization line item in the Mayor's budget proposal, released in March, allocated funding for broader database consolidation work, though the document did not break out image deduplication as a separate program.

The practical consequences show up unevenly across the city. Agencies processing high volumes of visual records — the Zoning Commission, the Department of Consumer and Regulatory Affairs on K Street NW, and DDOT — carry the heaviest duplicate loads, according to a city council technology committee briefing held in April. Each redundant image consumes storage that the District pays for through commercial cloud contracts, and retrieval times for legitimate records slow when systems must sort through multiple copies.

Residents filing permit applications or requesting inspection records through the city's online portal at 1100 4th Street SW have reported inconsistent results when the same property appears under multiple image tags — an experience that is particularly acute in fast-changing neighborhoods like Congress Heights and the H Street NE corridor, where building records have been updated repeatedly over short periods.

City technology officials have signaled that a formal deduplication strategy will be part of a broader data infrastructure review expected to conclude by the end of fiscal year 2026, which runs through September 30. That would put DC roughly three years behind London's timeline and at least two years behind Seoul's. For now, the District's approach remains reactive — cleaning up after the fact rather than stopping the duplication before it starts. Other capitals have demonstrated that the latter is achievable; Washington has yet to make the institutional commitment to get there.