Curvature is the factor everyone talks about. It's also the factor most route-scoring tools lean on exclusively, because it's cheap to calculate from GPS geometry alone — count the turns, measure their radius, done. But if you've ridden in the mountains, you know curvature isn't the whole story. Some of the most memorable rides are on roads that aren't especially twisty but feel absolutely enormous. That feeling has a name, and MotoScore scores it separately: vertical exposure.
What vertical exposure measures
Vertical exposure is the perceived drop on either side of the road — how much open space falls away to the left or right of where you're riding. It's not the same as elevation change (which is how much the road itself climbs or descends along its length). A road can have zero elevation change for miles while still being hair-raising because of what's next to it.
MotoScore computes vertical exposure by combining:
- Terrain slope perpendicular to the road direction, sampled from USGS elevation data
- How close the road runs to a ridgeline or cliff edge, derived from the same elevation model
- Whether the exposure is one-sided or two-sided — a ridge road with drops on both sides scores higher than a shelf road with a wall on one side
The result is a number from 0 to 100 that captures how exposed the road feels, not just how high it is.
Why GPS geometry alone can't capture it
This is the crux of the issue. A 2D route file — latitude, longitude, maybe elevation along the road — tells you the shape of the path you'll take. It tells you nothing about what's next to that path. Two roads with identical GPS traces can feel radically different in person:
- One runs along a forested shelf with a rock wall on the right and trees on the left
- The other runs along a ridge with 2,000 ft drops on both sides
Same geometry, same curvature, same elevation change. Completely different experience. Any scoring system that only looks at the line on the map will rate them identically, and that's been a persistent failure of route-quality tools for years.
Vertical exposure fixes this by sampling the surrounding terrain rather than the road itself. It's computationally heavier, but it's the only way to tell a ridge road from a forest road.
The Skyline Drive example
Skyline Drive in Cañon City, Colorado is the cleanest demonstration of why exposure matters. It's only about three miles long. It has modest curvature — some bends, but nothing a sport rider would call twisty. Elevation change is moderate. On a pure curvature-and-elevation model, it scores unremarkably.
It is also one of the most extraordinary roads in the state. The entire route runs along a knife-edge ridge with sheer drops on both sides. At some points the road is narrower than the ridge itself and you can see straight down several hundred feet on either side without turning your head. It's the kind of road that makes people genuinely nervous the first time they ride it.
MotoScore's earlier three-factor model rated Skyline Drive around a 52. The six-factor model — which adds vertical exposure, altitude ceiling, and scenic impact — puts it at 86 for a touring profile. That jump isn't an algorithm tweak; it's the model finally measuring the thing the road is actually famous for.
The opposite case: a twisty forest road
Consider the inverse — a backroad in the Ozarks that winds through dense forest for 40 miles. Tight switchbacks, constant curvature, genuinely technical riding. On a sport profile, curvature alone would push the score above 85.
Vertical exposure on that same road is close to zero. The road is bracketed by trees; you can't see more than twenty feet off the shoulder in any direction. There's no drop, no ridge, no view. The score the six-factor model produces reflects this — the curvature stays high but the final number is tempered, usually landing in the high 70s on a touring or ADV profile.
That's not a bug. It's the model saying: this is a great riding road, but it's not a once-in-a-lifetime road. Both descriptions are true.
How the factors interact
Curvature and vertical exposure aren't opposites; they're orthogonal. A road can score high on both (the Million Dollar Highway: tight switchbacks cut into a cliff face), low on both (most rural highways), or high on one and low on the other. The interesting case is the combination.
MotoScore weights the two factors depending on profile:
- Sport profile leans on curvature — you want turns first and foremost
- Touring profile balances the two — curvature matters, but so does the view and the feeling of space
- ADV profile weights exposure slightly higher than sport does, because ADV riders are often riding for the landscape as much as the dirt
The practical consequence: a heavily curved forest road might score 88 for a sport rider and 76 for a touring rider. A less-curved ridge road might score 74 for a sport rider and 88 for a touring rider. Both roads are excellent. Which one you'll find excellent depends on what you're riding for — and that's what the profiles are for.
When exposure outweighs curvature
A few heuristics, from experience more than from the algorithm:
- If a road crosses a significant pass or summit, exposure is almost always the dominant factor in what makes it memorable
- If a road is under 10 miles long, curvature rarely wins — you're not on it long enough for technical demand to define the ride
- If you're planning a long day and want variety, mixing high-curvature and high-exposure segments is almost always better than maxing one of them
The reverse is also true. On a racetrack-adjacent canyon road, curvature is the whole point and exposure barely matters — the score the model gives you reflects that, and so will your ride.
So what do you do with this?
When you're planning a route and the score surprises you — either higher or lower than you expected — look at the per-factor breakdown in the sidebar. If the number is higher than it "should be," it's usually exposure or scenic impact carrying it. If it's lower than expected on a technical road, the curvature is doing most of the work but the surrounding terrain isn't contributing. Both signals are useful, because they tell you what kind of road you're actually planning to ride — not just how twisty it is on paper.