Everyone in Chapin is talking about traffic. This study measured the street network itself — every intersection, every dead-end, every forced detour — and found a different problem than the one being argued about. And a much cheaper fix.
By Jimmy Ardis · Carolina Redesign · July 2026
The region's answer to Chapin's congestion is a $75–80 million widening of Columbia Avenue. This study asks a question that project never asked: why does every trip end up on Columbia Avenue in the first place?
The answer is in the map. Chapin's streets form a tree, not a web — 963 dead-ends, one of the most funnel-shaped networks a town can have. Trees put every leaf's traffic on the trunk. And you cannot widen your way out of a tree.
Chapter One · The Diagnosis
A town of 963 dead-ends
We built a complete graph of the Chapin community's street network — 482 miles of streets and 1,510 intersections across the town, the Amicks Ferry peninsula, Timberlake, White Rock, and Ballentine — and measured how it actually connects. (Little Mountain, Peak, and Pomaria are separate municipalities and are excluded.)
Three vital signs, and none of them are close to healthy:
38.9% of all street-ends are dead-ends. 963 cul-de-sacs and stubs against 1,510 true intersections. More than one in three streets simply stops.
Link-node ratio: 1.126. Planners score network connectivity by the ratio of street segments to intersections. A connected grid runs 1.6 or higher. Chapin sits at 1.126 — deeply dendritic. A tree.
Median detour factor: 1.708. For trips of half a kilometer to 3.5 km, the median Chapin journey drives 1.708× the straight-line distance. Ten percent of trips drive 3.336× — nearly four miles of road for one mile of geography. Traditional towns run 1.2–1.35.
Some of this is geography — Lake Murray severs the map, and no street grid can cross a cove. But the lake explains only the edges. The interior pattern — subdivision after subdivision, each with one entrance, each turned away from its neighbors — is a choice. It was the standard American choice from about 1950 onward. Chapin simply built a lot of it, fast.
963
dead-ends in the network
38.9%
of street-ends go nowhere
1.708×
median detour vs straight line
3.336×
detour for the worst 10% of trips
Chapter Two · The Funnel
Where the tree puts its traffic
Network science has a tool for finding the streets a network forces trips onto: betweenness centrality. Run it on Chapin and the answer is exactly the streets everyone already complains about.
Amicks Ferry Road carries the highest forced load in the study area by a wide margin — the peninsula's single spine, with thousands of homes and no alternative. Then Broad River Road and Dutch Fork Road (the only spines serving White Rock and Ballentine), Chapin Road, Columbia Avenue, Old Lexington Highway. These streets aren't busy because people love them. They're busy because for most trips, the network offers no other legal path.
This is what engineer Walter Kulash called vertical thinking about traffic: when the trunk congests, thicken the trunk. It has a fifty-year track record, and the record is that widened arterials fill again — because the widening does nothing about why every trip needs the arterial. Lateral thinking asks the other question: can trips spread across more paths? That's not a bigger road. It's a better-connected network.
To be clear about Columbia Avenue
The widening and bypass now underway will genuinely help — and this study doesn't argue against it. It argues the widening alone is temporary relief. New growth (a thousand homes are coming at Brighton/Palatin alone) will refill the widened road unless the network around it starts connecting. The connectors below are how the town protects an $80 million investment with one more mile of pavement.
Chapter Three · The 120-Foot Problem
Near-misses: the connections that almost exist
We taught the computer to find every place in greater Chapin where two streets nearly touch but don't connect — dead-ends within a few hundred feet of each other, separated by a strip of woods and a property line.
It found 153 distinct near-misses. After filtering out anything that crosses water, I-26, or the rail line, 42 street-buildable candidates remain. The single best example: two street-ends that sit about 120 feet apart — while the drive between them today is more than two and a half miles, so far around that connecting them would save nearby trips an average of over five miles of driving, each way. A hundred and twenty feet of pavement versus five miles of driving, every trip, every day, forever.
These gaps are not engineering problems. Most are a few hundred feet of flat, buildable ground. They're ownership and intention problems — the connection was never required when the subdivisions were platted, so it never happened. Which means the fix costs almost nothing by road-building standards. It just has to be chosen.
Chapter Four · The Portfolio
What 1.35 miles of street buys
Take just the top ten connectors — 1.35 miles of new neighborhood street, in total. Reconnect the network and re-run every measurement. Here's what changes.
Forced load on Chapin's arterials, before and after
Betweenness mass by street · same trips, reconnected network · top-10 connector portfolio
Betweenness centrality (sampled, distance-weighted) aggregated by street name. "Forced load" = the share of shortest paths the network routes over each street. Portfolio = top 10 street-buildable connectors, ~1.35 miles of new local street in total.
Every arterial in town gets lighter. Chapin Road's forced load falls 46%. Old Lexington Highway falls 23%. St. Peters Church Road falls 43%. Columbia Avenue — the road getting the $80 million — falls 37%. Even Amicks Ferry, pinned by lake geography, sheds 27%.
The town-wide median detour factor drops from 1.708 to 1.678, and the worst-10% trips improve from 3.336× to 2.884×. And 102 more homes come within a one-mile walk of a school, a grocery store, or downtown — a 2.7% gain in walk-access, from pavement measured in feet.
The $80 million project widens the trunk. The 1.35-mile project shrinks the tree. The second protects the first.
About cut-through traffic — the honest answer
The first objection to any connector is "strangers will race through my street." It's a real concern with a real answer: design. These are not bypasses — they're 20-mph neighborhood lanes: narrow, tree-lined, with tight corners, built to be convenient at low speed and miserable at high speed. Connectivity distributes trips; geometry disciplines them. Towns that do both get quieter streets than towns that do neither — because today the alternative isn't calm, it's every single trip queuing on the same three arterials.
The mile that isn't a mile
Here is the network's effect on school walkability, measured directly. 1,206 homes sit within one mile of Chapin Middle School as the crow flies. Only 344 of them can reach it within one mile of actual walking. The other 862 — 72% — are severed by network shape alone: the homes are close, but the streets between them don't connect. Chapin High severs 69% of its nearby homes; downtown severs 61%; Chapin Elementary, the best of the set, still severs 44%. Lake Murray Elementary — measurable for the first time now that real Richland County parcel data is in the model — turns out to be one of the better-connected schools in the study, and it still severs 52%: 1,415 homes within a crow-flies mile, 675 within a walking mile. This is why every school morning looks like a car-line study — not because the homes are far away, but because the network makes near homes far.
Chapter Five · The Bigger Map
Greenways: the network under the network
Streets aren't the only web. Chapin has a second network waiting in plain sight: its creeks, its rail corridor, and its utility easements — continuous, gently graded corridors that touch nearly every neighborhood.
Overlay them and a town-scale greenway system draws itself: creek arms reaching from Lake Murray up between the subdivisions, the rail line running through the middle of town, existing paths ready to be stitched in. Where a street connector is politically hard, a walking-and-bike connection along a creek is often easy — no cars, no cut-through fear, and it delivers much of the same access. A child who can bike to school on a greenway is a car off Columbia Avenue at 7:40 a.m.
This is the forward-looking layer of the study: a Chapin where the street web and the green web grow together — where growth arrives (it will) onto a network that spreads it instead of stacking it. The town is still small enough to choose this. That window is measured in years, not decades.
The intervention map — nothing but the fixes
The existing street grid is deliberately hidden here. What remains is the entire opportunity set in one view: gold — the 42 street-buildable connectors; terra, dashed — near-misses blocked by water, I-26, or rail, where a street can't go but a footbridge or crossing could; green — creek corridors, the greenway raw material; navy, dashed — the rail line and utility easements, natural bikeway alignments; dotted — paths that already exist, waiting to be stitched in. Click any line for detail; toggle layers in the legend.
Every dead-end, every forced-load street, all 60 candidate corridors (42 street-buildable), and the greenway raw material — on an interactive map. Toggle the portfolio on and watch the numbers change.
A sharp piece of reader feedback sent us back to the data with one more question: when a subdivision gets approved and its traffic lands on the arterials — who actually pays for those roads? In South Carolina, the answer is almost never the government that approved the subdivision.
South Carolina runs the fourth-largest state-maintained road system in America — about 41,000 centerline miles. Roughly 53¢ of every road-mile dollar in this state is a state responsibility, against a national norm around 19%. And it isn't just interstates and US highways: the state system reaches all the way down to two-lane neighborhood collectors. Amicks Ferry, Columbia Avenue, Old Lexington Highway, St. Peters Church Road, Three Dog Road — every one of them is a state secondary route.
Every street in greater Chapin, by who maintains it
Terra — state-maintained (SCDOT): interstates, US and SC routes, and the S- secondary system. Gray — everything else: county, town, and private/HOA streets. Click any line for its name and class.
Maintainer
Classification: network edges matched against SCDOT's State_Highways inventory (an edge is "state" when most of its geometry lies within ~30 m of a state route centerline). Statewide shares: FHWA Highway Statistics, table HM-81 (2024).
55%
of greater Chapin's 483 street-miles are state-maintained
90%
of all trip-forcing (forced load) runs on state-maintained roads
19 of 20
of the most load-bearing streets are SCDOT's responsibility, not the town's
Put those three numbers together and the incentive problem comes into focus. The land-use decisions are local: a subdivision plat approved here, a rezoning there. But 90% of the traffic consequence lands on roads the local governments don't maintain. When the entity that approves growth doesn't carry the cost of the congestion it creates, the discipline that once forced careful decisions — can we afford the roads this pattern requires? — simply never activates. The bill is real; it just arrives in Columbia, in the state's pavement budget, instead of at town hall.
It also explains, in one map, why the connectors in Chapter Four never get built. Every candidate connector is a local street — it would be funded by the town, a developer, or a neighborhood — while nearly all of its benefit shows up as relief on state assets: Chapin Road's forced load falls 46%, Columbia Avenue's 37%. The actor who would pay is not the actor who saves. A serious connectivity program here almost certainly means SCDOT participation — the agency with the most lane-miles to protect has the most to gain from a town that stops forcing every trip onto its arterials.
There's a longer story about what happens when a city does pay for its own streets — Charleston studied one annexation for a full year in 1849, when its street bill was its own. We're telling that story in a coming study.
Methodology, briefly
Study area. A community-based polygon: the Town of Chapin, the Amicks Ferry peninsula, Timberlake/Dreher Island, White Rock, and Ballentine. Little Mountain, Peak, and Pomaria — separate municipalities in Newberry County — are excluded, as is Irmo proper.
Network. Street graph built from OpenStreetMap (drivable public streets; service lanes and driveways excluded), largest connected component: 2,734 nodes, 3,079 edges, 482 street-miles. Detour factors sampled over 400 origin–destination pairs 0.5–3.5 km apart. Trip-forcing measured with distance-weighted edge betweenness centrality (sampled). Walk-access measured as homes (16,419 residential parcels) within one network-mile of schools, supermarkets, or downtown. Coverage note: home locations are real parcel records on both sides of the county line — 9,398 Lexington County residential parcels from the county's public GIS, plus 7,021 Richland County residential parcels from the SC Department of Transportation's statewide parcel compilation (2024 vintage). Richland County itself publishes no public parcel service; the state's compiled layer carries its records. A Richland parcel counts as a home if it is assessed as an owner-occupied residence (the 4% class) or carries a heated dwelling of at least 300 sq ft on non-commercial land. Lake Murray Elementary, excluded from an earlier draft while Richland coverage was proxy-only, is now measured with full parcel data. The walking graph is the drivable street network — dedicated footpaths are mapped separately in the greenway layer and would only improve these numbers where they exist.
Connectors. Candidates are pairs of network points within ~260 m straight-line whose road distance is at least 4× longer (or unreachable within 4 km). Candidates crossing water, I-26, or the rail line are flagged and excluded from the buildable set. Portfolio impacts re-run the same measurements with the top ten buildable connectors added (assumed built length = 1.3× the straight-line gap). Connector lines are corridors for further study, not proposed alignments — several cross private property, and nothing here should be read as a claim on any parcel.
Maintenance classification. Street maintainer classes come from overlaying SCDOT's State_Highways route inventory on the network graph: an edge counts as state-maintained when most of its geometry lies within ~30 m of a state route centerline; all other public and private streets are classed together as local. Statewide comparisons from FHWA Highway Statistics table HM-81 (2024).
Frame. Vertical-vs-lateral traffic thinking after Walter Kulash; connectivity standards after CNU and Strong Towns. Analysis pipeline: Carolina Redesign (OSM → graph via NetworkX → impact simulation), the same open pipeline behind our Brighton analysis and the Charleston series.