You found a route. The file says 33 kilometers, 1,000 meters of climbing, a squiggle on a map. You load it onto your head unit, and tomorrow morning you'll find out everything else the hard way.
That's how most rides on unfamiliar roads begin, and it's why the first hour of them is quietly tense. The file told you the shape of the ride. It told you nothing about the ride itself.
What a GPX file doesn't tell you
A GPX file is a list of coordinates. It knows where the route goes and roughly how high. Here's what it doesn't know:
- What the surface actually is. "Gravel" spans everything from champagne hardpack to fist-sized rock that wants a mountain bike. A route that's 55% gravel rides completely differently depending on which 55%.
- Where the water is — and whether the spigot at the trailhead runs in October.
- Where your phone dies. Front Range canyons, like remote roads everywhere, have long dead zones. The moment you'd most want to call someone is precisely when you can't.
- Where you'd bail. Weather moves fast in the mountains. Knowing the one road that drops you out of the high country in five minutes changes how bold you can afford to be.
- Whether the store is open. Nothing reorganizes a ride like planning lunch around a general store that closes on Tuesdays.
Every experienced rider solves this the same way: they ask a friend who's ridden it. The friend at the trailhead is the real route preview — the surface truth, the water beta, the "watch the second corner on the descent." The entire pre-ride problem is that most of us don't have that friend for most routes.
The five things to check before any unfamiliar ride
If you take nothing else from this post, take the checklist. Before riding somewhere new:
- Surface mix, from someone who has ridden it — not from map shading. Tire choice and time estimates both hang on this.
- Water points, with seasonal caveats. Two bottles' range in July is not two bottles' range at altitude on a south-facing climb.
- Cell coverage gaps. If there's a dead zone, tell someone your plan before you enter it. This is the cheapest safety habit in cycling.
- Bail-out roads. Find the one road that shortcuts home, and know where it leaves the route.
- The stop. Where's the food, what are its hours, and does it take cards? Half of route culture is knowing which store has the lemonade.
Write those five answers on a piece of tape on your top tube if you have to. The point is to start the ride already knowing them.
Ride it with your thumb first
We built rideSOLTA because we think the route preview should be the product, not a research project across six tabs.
Every route on the site is a visual story you can scrub: drag anywhere on the elevation profile and the photos, the map, and the beta follow your thumb — the climb you're worried about, the view that justifies it, the store at the top. The five checklist answers are pinned to the route at the exact kilometer where they matter. You can try it on our founding route right now — ride the whole thing in about a minute, then decide what your legs think.
Two things we do differently, on purpose:
- Every route is ridden, written, and vouched for by one person with a name. Not an average of strangers — a curator whose notes read the way a friend's would, because that's the standard: what I'd tell you at the trailhead.
- The files are free. GPX and FIT, no account required. The preview is the product; the file is yours either way.
Start with the Colorado Classics — three rides, three surfaces, one range — or just explore the routes. And wherever you ride this weekend: fill both bottles, and tell someone your plan.