DC's Battle Against Duplicate Street Imagery Lags Behind London and Seoul — But a Fix Is Coming

Washington DC's street-level mapping infrastructure has a problem it shares with few other capitals its size: thousands of duplicate georeferenced images sitting across at least three separate public-facing databases, none of which talk to each other cleanly. The District of Columbia Office of the Chief Technology Officer, which oversees dc.gov's open data portal, acknowledged the issue in a spring 2026 internal review, though a formal remediation timeline has not been made public.

The timing matters. The Trump administration's push through the Department of Government Efficiency to consolidate federal IT spending has frozen or delayed several inter-agency data-sharing agreements that the District relied on to flag and purge redundant imagery. Municipal tech staff and federal counterparts at agencies including the General Services Administration are essentially operating in parallel silos while budget negotiations drag on through the summer.

What Duplicate Imagery Actually Costs a City

The problem is less glamorous than a pothole on Georgia Avenue NW, but the practical cost is real. City planners at the Office of Planning, which has been overseeing rezoning reviews in Anacostia and the NoMa corridor near New York Avenue NE, rely on street-view image archives to document pre-construction baselines. When duplicate images — sometimes taken weeks apart and indexed under identical coordinates — enter those archives, the record becomes legally murky. A single block near the Florida Avenue Market redevelopment site in Eckington has, according to a February 2026 District data audit summary referenced in a DC Council Committee on Technology oversight memo, more than 40 georeferenced images attached to overlapping bounding boxes.

Globally, the comparison is not flattering for Washington. Transport for London completed a systematic duplicate-image purge across its Streetscape data layer in late 2024, cutting redundant records by roughly 34 percent according to a TfL data governance report published that December. Seoul's Smart City division, operating under the Seoul Digital Foundation, deployed an automated deduplication pipeline in 2023 that processes incoming street imagery against a hash-based fingerprinting system before any file enters the city's open GIS archive. Neither city had to navigate the kind of federal-municipal jurisdictional friction that defines nearly every technology decision in Washington.

The District sits on federal land. That foundational fact means that even imagery captured by DC government vehicles along streets like Pennsylvania Avenue SE or Martin Luther King Jr. Avenue SW can overlap with data held by the National Park Service, the Architect of the Capitol, or the Smithsonian Institution's own geographic systems. Deduplication requires sign-off across entities that do not share a common data standard.

What the District Is Planning — and When

The OCTO has been piloting a perceptual hashing tool, similar in concept to what Seoul deployed, on a limited dataset covering the Capitol Hill and Navy Yard neighborhoods since March 2026. The pilot was funded under a $1.2 million allocation within the District's fiscal year 2026 technology modernization budget, a figure drawn from budget documents posted to the DC Council's website ahead of the May 2026 budget vote.

The pilot is scheduled to expand citywide by the first quarter of fiscal year 2027, which begins October 1, 2026 — assuming federal data-sharing agreements are resolved before then. That is not a certainty. Several coordination meetings between OCTO and GSA representatives have been postponed since February, according to the same DC Council oversight memo.

For residents and urban researchers who rely on street-level imagery through tools like the DC GIS Open Data portal at opendata.dc.gov, the practical advice for now is straightforward: treat any georeferenced image tagged before January 2024 with caution when using it for construction baseline or legal documentation purposes, and cross-reference against the District's separate 311 photographic complaint archive, which runs on an independent update cycle. It is imperfect redundancy, but until the deduplication pipeline goes citywide, it is the best available check on a database that has outgrown its governance structure.