Washington writes rules other cities adopt, and is itself governed from outside. The Open311 standard now used from Boston to Bengaluru began as an API for D.C.'s own 311 — and the District's registered endpoint no longer answers, while San Francisco's still does. Its sewers are rebuilt to a federal court's timetable, its subway and its bike share belong to regional authorities rather than the city, its first-in-the-nation building energy standard took effect only after congressional review, and in January 2026 the US Department of Transportation moved to prohibit its traffic cameras outright. What the District controls directly, it instruments heavily: 546 enforcement cameras, acoustic gunshot sensors since 2006, and a subsidy that puts police-registered cameras on private buildings.
The atlas documents 10 projects in Washington D.C., the earliest dating to 1976: 1 scaled back, 9 still running without a verdict. Every entry carries an evidence grade — the strongest here is peer-reviewed (1 entry) — and links its sources.
Three entries that show what Washington D.C. is actually doing.
Computed from the 10 entries below — a profile, not a score.
Automation came first and then went away. The Metro opened in 1976 with trains that drove themselves between stations, and WMATA switched the whole network to manual within about a day of the Fort Totten collision that killed nine people in June 2009. The investigation blamed track circuits that stopped detecting a standing train — part of the protection layer, which kept running — not the driving mode that was turned off, and none of the NTSB's 25 recommendations asked for the shutdown. Enforcement automation went the other way in the same era: red-light cameras from August 1999 and speed cameras from 2001, the latter carrying one of the field's few control-group evaluations — mean speeds down 14 percent against Baltimore control sites, and vehicles more than 10 mph over the limit down 82 percent.
Between 2004 and 2010 the District built the interfaces. The Office of Unified Communications took over 311 in 2004, and by July 2009 the city was on the second draft of its own 311 API; by May 2010 D.C. and San Francisco were the two cities agreeing the GeoReport v2 specification together. A 2008 law began requiring large buildings to report and publicly disclose their energy and water use, the data layer that a decade later would carry the emissions standard. Capital Bikeshare opened in September 2010 with 49 stations, replacing a 120-bike pilot that had been paid for with advertising rights and drew about 1,700 subscribers before closing — a contract, its former transport director said, in which one line at the end outlined the private partner's lack of commitment.
The heavy engineering arrived by court order. A 2005 federal consent decree with the EPA and the Justice Department obliges DC Water to end combined sewer overflows, and every District property pays for it by measured impervious area rather than by water used — $24.23 per equivalent residential unit a month in 2026. The Anacostia tunnel went into service in March 2018, and the utility reports overflows to that river down about 90 percent. A 2015-16 modification offered the softer path: green infrastructure that could have eliminated the Rock Creek storage tunnel altogether. DC Water broke ground on the Piney Branch Tunnel in July 2026 anyway.
Since 2014 the District has been writing obligations that its own record does not always match. Mayoral orders in 2014 and 2017 created a duty to publish and made every agency inventory and grade its data; by the 2024 reporting, 78 agencies listed 2,330 datasets, 1,061 of them classified open — and 298 of those were still not online. The terms of use dedicate District data to the public domain under CC0, while the catalogue's own metadata mostly ships an attribution licence and occasionally none at all. The building energy performance standard, effective March 2019 and described by its regulator as the nation's first, is a percentile rather than a cap: it sits at the median for each property type, so roughly half of every category starts below the line — but the first compliance cycle only closes at the end of 2026, so nothing has been assessed. And the camera subsidy put nearly 28,000 privately owned cameras on the map by 2024 while publishing, as its only outcome figure, 31 requests for footage in a year.
On a time axis, by the year each one started — 1976 to 2022. Pick a dot to read what it was.
✔ Every published entry is checked against the public sources it cites before publication.
Editorial links between Washington D.C.'s own entries — the city as a system, not a list.
Plans and announced trajectories — not yet documented results.
Three deadlines fall within the next eighteen months, and each answers a question the District has so far left open. The first BEPS compliance reports are due in spring 2027, which is when anyone will learn whether a building that missed its target actually pays the shortfall-proportional charge of up to $10 a square foot. The Potomac River Tunnel has a substantial-completion date of 2028 against a consent-decree deadline of February 2030 — a schedule set by a court, not by a budget. And the camera programme faces a threat it cannot engineer around: the US DOT moved in January 2026 to prohibit automated enforcement in the District and a House committee advanced a ban in March, neither yet law, while the collection problem persists at the state line — Maryland and Virginia plates draw roughly two thirds of the tickets and neither state penalises its own residents. The quieter test is whether the District repairs the interface it invented: its Open311 endpoint has gone dark, with no announcement and no replacement.
Where Washington D.C. appears in the atlas's own analysis.
Three cities the atlas reads next to Washington D.C. — the reason first, then the entries it rests on. Chosen by hand from the Washington D.C. threads below, not counted out of them.
Two North American cities of the automated-then-not: both resignalled their metros and still keep an operator in the cab, both promise open data their own metadata contradicts, and their speed cameras went opposite ways.
Washington rides on docks Montreal's manufacturer built, and both show what happens when the thing you depend on is not yours: one bought its supplier out of bankruptcy, the other cannot even site its own speed camera.
Mirror images on open data: Washington promises the public domain and ships something else in its metadata, Miami legislated nothing and ships a clean deed on almost everything — and both wrote Open311 code that has since gone dark.
Every editorial link from Washington D.C.'s entries into another city, strongest first. Each one is a statement about two projects, not about two cities — the three above are the ones the atlas is willing to make at city level.
1001 Smart Cities (2026). “Smart-city projects in Washington D.C., United States.” The Smart City Atlas. https://1001smartcities.org/cities/washington-d-c/ (last verified 2026-08-27). Data: CC BY 4.0.
The underlying data is free to reuse with attribution — see the open data page.