How Minneapolis's Duplicate Image Problem Grew From a Minor Glitch Into a City-Wide Records Headache

Minneapolis city staff are now deep into a remediation effort to purge thousands of duplicate images from municipal digital archives, a problem that grew quietly for more than a decade before reaching a scale that forced administrators to act. The work, centered on records held by the Department of Community Planning and Economic Development and the city's 311 service portal, has exposed how fragmented data practices across Hennepin County's largest city created redundancy on a significant scale.

The timing matters. Minneapolis is midway through a broader digital infrastructure overhaul tied to its 2023 Technology Action Plan, a multi-year initiative to modernize how the city stores, retrieves, and shares public records. Duplicate imagery — photos of zoning inspection sites, neighborhood development projects, code violations, and public event documentation — has emerged as one of the plan's more stubborn obstacles, because bad data archived years ago doesn't simply disappear when new systems go live.

How the Backlog Built Up

The roots of the problem trace back to the mid-2010s, when individual city departments operated on separate content management platforms with no shared deduplication protocols. The Minneapolis Police Department, Public Works, and the Parks and Recreation Board each uploaded photographs independently, often with inconsistent metadata tagging. When the city began migrating legacy files into a unified cloud-based repository starting around 2019, duplicate files migrated alongside the originals.

The Northside neighborhoods — particularly Jordan and Near North, which saw intensive code-enforcement photography during the post-2008 foreclosure crisis — generated some of the densest clusters of redundant files. Properties along Penn Avenue North and on blocks adjacent to Farview Park were among the most-photographed during that period, and inspectors working from different departmental systems sometimes uploaded the same site images multiple times under different file names. By the time the city's IT staff ran a full audit in late 2024, preliminary estimates put the number of duplicate image files in the hundreds of thousands, though the city has not yet published a final verified count.

The Hennepin County assessor's office, which shares certain property-record imagery with Minneapolis through a data-sharing agreement, flagged the duplication issue in a 2023 intergovernmental review. That flag helped accelerate the city's decision to dedicate staff time and contract resources to the cleanup.

What Remediation Actually Looks Like

City staff are using a combination of automated hash-matching software and manual review to identify and remove duplicates. The automated pass handles straightforward byte-for-byte copies. The harder cases — photographs that are near-identical but not exact, such as two shots of the same building taken seconds apart — require human judgment about which version carries better metadata or higher resolution.

The Minneapolis Digital Services team, operating out of City Hall on South 4th Street, estimated in its fiscal year 2026 budget documentation that the remediation project would consume roughly 1,800 staff hours across two fiscal years. External software licensing for the deduplication tools added a line item to the city's IT budget, though the specific contract value has not been disclosed in public filings reviewed for this report.

For residents and neighborhood organizations, the practical effect is mostly invisible — nobody browsing the city's public permit portal on a day-to-day basis notices whether the backend holds one photo of a construction site or three. But for journalists, researchers, and attorneys filing data-practice requests under the Minnesota Government Data Practices Act, duplicate files have historically inflated response times and costs. Under state law, agencies may charge for staff time spent fulfilling records requests, and wading through redundant imagery adds to that burden.

The cleanup is expected to wrap up in phases through late 2027. Once complete, the city plans to implement automated deduplication at the point of upload, a step that should prevent the backlog from reconstituting itself. Residents with questions about specific records requests can contact the city's data practices office through the Minneapolis 311 system, either by phone or through the city's online portal at minneapolismn.gov.