Chalk Line
The street didn’t kill them by accident. The design did.
Channel: Chalk Line
Tagline: The street didn’t kill them by accident. The design did.
Niche: Consumer-facing pedestrian and cyclist death accountability — an automated public-interest site that turns federal crash data into city scorecards, road-segment danger maps, SUV/pickup impact analysis, hit-and-run rankings, and brutally clear weekly dispatches explaining which streets keep killing people outside cars, where, and why.
Target audience: Urban residents, parents with kids who walk to school, cyclists, runners, neighborhood groups, journalists, planners, local politicians, homebuyers, traffic-safety nerds, Strong Towns people, Vision Zero advocates, and ordinary humans who would very much like crossing the road not to feel like a side quest. In raw scale terms: 7,314 pedestrians and 1,166 pedalcyclists were killed in U.S. traffic crashes in 2023 alone. That is 8,480 nonmotorist deaths in one year — not a niche issue, a national design failure with local addresses.
Why now: The numbers are obscene, the audience is primed, and the product still does not exist. NHTSA’s FARS data shows pedestrian deaths are up 78% since the 2009 low point, and IIHS says they now account for 18% of all traffic fatalities. Smart Growth America’s Dangerous by Design 2024 found 7,522 people walking were killed in 2022, a 75% increase since 2010, with Memphis reaching a horrifying 5.14 pedestrian deaths per 100,000 people. Meanwhile, the social and political conversation has finally shifted: “stroad,” “Vision Zero,” and “traffic violence” have escaped planning-Twitter and entered mainstream city politics. But the public UX is still miserable — PDFs, annual reports, advocacy blogs, local news after one crash, then nothing. The raw ingredients for a killer data-journalism product are sitting in a free federal API.
Channel Soul: Chalk Line is a bitter little crossing guard ghost with a traffic cone for a hat and a forensic hatred of phrases like “accident-prone corridor.” No — it is not “accident-prone.” It is designed to let speed survive contact with human bodies. The voice is sharp, statistical, local, and furious in a useful way. Not anti-car performance art. Not sanctimonious cycling cosplay. This is receipts-driven street autopsy. Visual identity: ambulance white, asphalt black, sodium-vapor yellow, stop-sign red, faded crosswalk stripes, police-report typography, and ghost-bike line art. Running bits: Stroad of Shame, Hit-and-Run Hour, Ghost Bike Index, SUV Receipt, and Crosswalks & Consequences.
Content Example: Sample headline: Memphis Didn’t Become America’s Deadliest Metro for Pedestrians by Bad Luck. It Built Too Many High-Speed Streets Masquerading as Places.
Americans are still trained to talk about people killed while walking as if they were struck by weather. A tragedy. A terrible accident. A sad but random event. The data is much ruder than that. In Dangerous by Design 2024, Memphis ranked as the deadliest large metro area for pedestrians in the United States, with a pedestrian death rate of 5.14 per 100,000 people. That is not chaos. That is a system printing the same answer over and over.
What keeps showing up in these deaths is not mystery but geometry. Wide arterials. Long crossing distances. Slip lanes that reward speed. Commercial corridors built like mini-highways, then sprinkled with bus stops, apartment entrances, dollar stores, fast food, and schools as if human feet were a rounding error. Federal data can tell you the victim’s age, the hour, the lighting conditions, the road class, the speed environment, whether the driver fled, whether the striking vehicle was a pickup or SUV. What it often cannot do is tell the truth in plain English: this road was built to move cars fast through a place where people had to exist.
That is Chalk Line’s whole job. Not to mourn abstractly. To identify the repeating physical patterns that turn ordinary errands into mortality risk. If one corridor keeps producing nighttime deaths, if one city’s fatality curve bends upward while it keeps widening arterials, if one state has a grotesque hit-and-run problem, then those are not isolated stories. They are design fingerprints. And fingerprints are useful because they point back to someone’s hand.
Data Sources:
- NHTSA Crash API / FARS API — the core free dataset: crash-level fatality records from 2010 onward, including pedestrians, cyclists, vehicle types, crash time, county, road conditions, location, person type, hit-and-run, lighting, weather, speed-related factors, and more
https://crashviewer.nhtsa.dot.gov/CrashAPI - NHTSA FARS annual downloads — downloadable historical files back to 1975, ideal for long-term trend lines, metro retrospectives, and yearly snapshots
https://www.nhtsa.gov/file-downloads?p=nhtsa/downloads/FARS/ - FARS Encyclopedia — official national stats and structured query views
https://www-fars.nhtsa.dot.gov/ - Smart Growth America – Dangerous by Design — metro-level pedestrian danger rankings, public framing, equity analysis, and benchmark methodology
https://www.smartgrowthamerica.org/dangerous-by-design/ - IIHS Pedestrian Fatality Statistics — curated federal-data analysis including national trend context and hit-and-run share
https://www.iihs.org/topics/fatality-statistics/detail/pedestrians - U.S. Census / ACS / population tables — per-capita city, county, metro, and demographic rate calculations
- FHWA highway / roadway classification data — identify arterials, principal roads, and network context
- OpenStreetMap + TIGER/Line — map road geometry, cross streets, road classes, sidewalks, speed tags, and corridor pages
Automation Pipeline:
- Schedule:
- Weekly: rebuild national, state, metro, and city scorecards from the current FARS snapshot
- Weekly: publish one flagship data dispatch plus multiple local “worst corridor” pages
- Monthly: recalculate vehicle-type trends, hit-and-run rankings, nighttime death patterns, and demographic gaps
- When annual FARS releases drop: generate a full-season reset package with new rankings, maps, and comparison stories
- Collect:
- Pull FARS records via NHTSA Crash API and/or annual bulk downloads
- Pull benchmark context from Smart Growth America/IIHS reference tables
- Pull population denominators and road network layers
- Pull OpenStreetMap attributes for corridor classification and crosswalk/sidewalk context
- Process:
- Compute a custom Chalk Score for metros, cities, counties, and corridors using per-capita deaths, trend direction, hit-and-run share, nighttime risk, and outside-vehicle fatality concentration
- Cluster deaths onto named corridors and intersections
- Detect patterns by vehicle profile: SUV, pickup, sedan, motorcycle, truck
- Generate editorial findings such as: “nighttime deaths rose here,” “pickups are overrepresented on this corridor,” “this metro improved after dieting arterials,” or “this county keeps producing hit-and-run fatalities”
- Use AI to turn structured findings into plain-English story drafts, then pair them with deterministic charts and source-linked methodology
- Generate:
- Metro report cards with grades and trend arrows
- Corridor death maps with “most lethal mile” callouts
- Hit-and-run leaderboards by city/state
- Time-of-day radial charts and road-type breakdowns
- “SUV Receipt” graphics comparing striking vehicle categories
- AI-generated editorial covers: ghost-bike posters, chalk-outline crosswalk art, redacted police-report motifs, schematic stroad diagrams
- Publish:
- Static Astro site with national home, metro pages, state pages, city pages, road corridor pages, and weekly dispatch archive
- Pre-rendered charts and cached map tiles for speed
- Auto-deploy through GitHub Actions to Cloudflare Pages or GitHub Pages
Tech Stack:
- Static site: TypeScript + Astro
- Data collection: Node.js scripts in GitHub Actions
- Storage / analysis: DuckDB + Parquet + JSON exports
- Charts: D3 / Observable Plot
- Maps: MapLibre GL + PMTiles / TopoJSON
- Image generation: SVG templates + AI editorial poster prompts
- CI/CD: GitHub Actions
- Hosting: Cloudflare Pages or GitHub Pages
Monetization Model:
- Channel 1: Donations / memberships — this is exactly the kind of civic utility people fund when it becomes part of their city’s information diet
- Channel 2: Premium local alerts — ZIP-code or corridor alerts for journalists, advocates, neighborhood groups, and parents
- Channel 3: Pro research packets — downloadable metro or corridor briefs for local newsrooms, nonprofits, attorneys, transportation consultants, and safe-streets campaigns
- Channel 4: Sponsorships — careful partners only: urbanism newsletters, mapping tools, bike/security brands, local media software, traffic-calming vendors; absolutely no auto industry cope-sponsorship nonsense
- Projected month-1 revenue: $100–$400
- Projected month-6 revenue: $2,000–$6,000 with local SEO traction, a strong mailing list, and a few high-value metro pages that become citation magnets
Launch Complexity: 4/5 — The data exists and is rich, but the hard part is turning crash records into trustworthy corridor-level storytelling instead of ugly database soup. Content Quality Score: 5/5 — Deeply useful, emotionally legible, highly visual, and tied to a question millions of people already ask: why does this road feel like it wants me dead? Automation Score: 4/5 — Core data updates are not real-time, but the long historical corpus plus weekly/localized story generation makes the content machine strong and sustainable. Revenue Potential: 4/5 — Great donation logic, strong B2B/pro tier for civic users, decent sponsorship path, limited affiliate upside but excellent trust moat. Total: 17/20
Why This Will Work: Chalk Line works because it turns a sprawling moral problem into a repeatable local product. People do not search for “national traffic safety externalities.” They search for “why are pedestrians dying in Memphis,” “most dangerous roads in Phoenix,” “cyclist deaths in my city,” and “is this intersection safe.” That is long-tail SEO gold with real civic urgency behind it. It also has community gravity: urbanists, neighborhood groups, and local reporters are desperate for sourceable, screenshot-friendly evidence. The product becomes both a public service and a movement tool. Better yet, it compounds: every city page, every corridor page, every annual comparison strengthens the moat.
Risk & Mitigation:
- Risk: FARS is not a live feed; there is reporting lag.
Mitigation: Be honest. Position Chalk Line as the best public record of patterned fatality risk, not a live incident ticker. - Risk: Corridor-level matching can be messy when crash coordinates are imperfect.
Mitigation: Use confidence labels, snapped geometry, and never fake precision. - Risk: The tone could slide into doom-porn.
Mitigation: Balance autopsy with utility: fixes that work, cities improving, before/after road diets, safer design examples. - Risk: Local political blowback.
Mitigation: Publish methodology, source every claim, expose raw numbers, and show comparisons openly.
Direct link: https://github.com/bullwinkle/HustleIdeas/blob/master/ideas/2026-04-09-0500.md