Skip to main content

← All posts

Release Notes

Streets to the Trailhead, Trails from There

· 6 min read

If you have ever pulled up a paper trail map next to a highway map, you already know the shape of this update. The road map gets you to the parking area at the mouth of the canyon. The trail map takes over from there. Overlook can now do that in one place, on the same screen, offline, with the trail you picked drawn right on top of the roads that got you to it.

A laptop and a phone side by side, both showing Overlook's map view. A blue road route runs from a campground to a red pin near Telluride, and a longer purple track loops through the mountains for the trail portion. The phone version shows the same map with a Drive southeast on Mary E Campground banner at the top and 9:58 AM arrival, 17 minutes remaining, 11 miles across the bottom.
Blue is the road route to the trailhead. Purple is a GPX trail we loaded. Same map, same screen, no cell signal.

Two kinds of navigation, one screen

Most of the trips we take end up mixing two different modes of getting somewhere. There is the road part, where you want turn-by-turn directions on a route that respects the size of your rig and the highways you are willing to take. Then there is the off-road part, where turn-by-turn is not really the right idea. You are following a known trail, a forest service road, a two-track, a shore route somebody else already scouted and shared. What you want there is a line drawn on the map that says, this is the way, stay near it.

Until now, Overlook did the second half well. You could load a map of a region and see where you were on it. What was missing was the first half. Now both are in the same picture. A road route in blue, a trail in whatever color you gave it, one map, both offline.

Load a trail, give it a color

Trails on Overlook are just GPX files. That is the file format almost every hiking, off-roading, and paddling site hands out when you download a route. You already have folders full of them, probably. Or you can grab them fresh from any of the trail communities you already follow.

Go to the Trails page, drop a GPX in, give it a name, pick a color. That is the whole flow. The name is how you find it later. The color is how it draws on the map so it stands out against the roads and terrain underneath. There is a full color picker if you want a specific shade, and a row of ten presets if you just want to tap and go.

Loaded trails live on your rig. Not in the cloud, not on someone else's server. You can delete them, restore them from trash, or clear them all out. The whole library is yours.

Get to the trailhead with real routing

Once a trail is loaded, the map view knows about it. Tap Navigate on the trail and Overlook lines up a route from where you are to the start of the trail, drawn on real roads. That blue line in the screenshot is exactly that. It is the drive from a campground near Rico, up through the passes, to a pin where the trail begins.

The route respects the mode you pick. Drive is the default. There is an RV mode for when you are hauling something big and want a route that stays on roads that make sense for it.

The top of the map shows the next instruction, road name and distance to the turn. The bottom shows arrival time, minutes remaining, and distance. On a phone, that whole bottom strip collapses into a slim drawer so the map stays as big as possible, and pulls back up when you want the full turn-by-turn list.

Follow the trail once you get there

When the pavement runs out, the purple line is already drawn. That is your trail. You do not have to load anything. You do not have to switch modes. You just keep driving, and the map keeps updating your position along the track you brought with you.

A drawn line is doing more work than it looks like. It is the reason you know you are on the right two-track when the map data does not show every logging road. It is why you can tell at a glance that a fork goes the wrong way. It is a reference you built ahead of time, riding along with you, that does not depend on anyone else being in the loop.

One trail draws on the map at a time for now. Swap between them from the Trails page whenever you want to look at a different one.

Everything else keeps running

Nothing about this replaces what the rest of the rig is doing while you drive. That matters more on a two-track than it does on a highway.

The house battery is still monitored while the fridge and the lights and whatever recovery gear you are running pull off of it. You can see what the panel is pulling in from the sun at the same time as you are watching the trail.

Cabinet sensors are worth their own line here. They live in the gear bins in the back and on the door of whatever hard case you keep your kitchen in. If a latch pops loose on a rough section, Overlook tells you before the contents are on the trail behind you. That same sensor can go on a rooftop tent latch. If it comes up while you are moving, that is exactly the kind of thing you want to hear about right away, not after you have driven another mile with it flapping.

Air quality inside the cab or the topper stays armed too. That is a real one on trails where you are running with windows cracked and dust is a constant.

All of it lives in the same app as the map. You are not juggling a road app, a trail app, and a rig monitor app. A tap moves you from the map to the battery page to the air quality page and back. Down the road, the plan is to surface the critical numbers as an overlay right on the map so you do not have to tap away at all. For now, it is one app and one tap away.

Any device on your rig's wifi

Overlook is a web app. There is no App Store or Play Store download, no permissions to accept, no update prompts, no account to make. If your device has a browser, it can run Overlook. Android, iOS, Windows, Mac, Linux. It does not care. The layout adjusts to whatever screen it lands on. Phone, tablet, laptop. Portrait or landscape. It looks and feels right on the one you already carry.

Parked the night before, that is a laptop at the dinette or camp table with the big map, looking over tomorrow's trails and pulling up GPX files. When it is time to move, that is your phone in the cupholder or a tablet on the dash. Passengers can pull the same map up on a tablet from the back seat and follow along, call out upcoming turns, or spot where the trail leaves the road ahead. No more "are we there yet." They can see the arrival time on their own screen and watch the miles tick down themselves. Different screens for different moments, all pointing at the same Headwaters, all showing the same map and the same live position.

Still offline. Still yours.

None of this needs a cell signal. Not the road routing, not the trail drawing, not the map itself. Once you have a map region loaded and the trails you care about uploaded, you can drive out of every bar on the map and everything keeps working. That is the whole point of building this on your rig instead of somewhere else.

It also means the trails you upload are not going anywhere. There is no account to sign in to. There is no analytics ping when you look at the map. There is no company on the other side of the connection that knows where you are going. It is a route you brought, on a map you loaded, on a computer you own.

What's next

Voice cues are still on the way for the road half. Address handling on the small residential streets is still being sharpened. On the trail side, we are looking at the natural next steps. Multiple GPX layers visible at once. Distance-along-track and estimated time to the end of a trail. An option to search for gaps between where you are and where the trail starts and get a routing preview for that gap alone.

For now, though, the through-line works end to end. You can load a trail, drive to it, and follow it, all from one map that lives on your rig and does not need the internet. That is a real capability that was not there a week ago.

If you want the next round of updates in your inbox when they land, the form below is how.