How I make my hiking guides with AI, from my own films and GPS
My 58 hiking guides are built with AI from my own films, GPS tracks and notes, checked by a second AI, and sold as PDFs with GPX files of each route.
I make long films about hiking alone, mostly for YouTube: about 250 over ten years, from the Dolomites to Patagonia to the Karakoram. People often ask in the comments how to do the hike themselves. This fall I started answering that with a guide for each route, built with AI, first Codex and now Claude, from things that already existed. Here's how.
How it started, in my own words
Making hiking guides was always the plan, and I'd tried a couple of times without it really working. Most recently I made guides on Gumroad, Substack and Patreon, and had a little success with those, mostly because my Alta Via 1 video was taking off on a few social platforms, so there was traffic going there. I made a bunch of sales.
Then, in the airport about to head out to Norway, I realized how good AI, specifically Codex, was at making the guides for me and gathering my information to build them: my AllTrails recordings, my itinerary, everything I'd said in the videos. So I set it loose to make one good guide, and I realized I could eventually do this for close to 50 of them. It took a good month to get them all to a point where I liked them, and maybe another week to build out the website and the payment workflow and everything that goes with selling guides. The guides are one of the main reasons I have a website now.
It felt really good. I was pleasantly surprised at how good the first guide came out, and that made me realize there was a lot of potential for this to be a real product. So much of the selling and marketing could be automated too, which excited me. But I've done the hard work: going on these hikes, capturing the photos and videos, recording the AllTrails activity, making the behind-the-scenes sections of the videos where I talk about my experience. There's a lot of unique, valuable information in these guides. AI let me organize it in one clean format and add the missing pieces and helpful things I wouldn't have thought of. If I make a hiking guide on my own, it's usually just from my perspective, but a lot of other people out there trying to do these hikes would get something different from a guide made for them. I think it's a really good product, and I plan to keep improving it.
How a guide gets made, in 6 steps
- Gather what exists: my film, my AllTrails GPS recordings, my photos, the film's description and my trip notes.
- Write a plain record of what I actually did, day by day and often hour by hour.
- Work out the numbers from my GPS: distance, climb, high point and time.
- Draw the maps from my GPS, with an elevation profile for every day.
- Build it in one design shared by every guide.
- Have a second AI check it against official sources.
Then it goes on sale as a PDF, with my GPX files in the same download.
The rule: only my own trip
When we rebuilt my old Alta Via 1 write-up as a proper guide, Claude asked me for twenty minutes of new input, like which hut I liked best. I said no: "I've already given personal accounts in my YouTube videos, and I want these guides 100% built with AI now."
So my voice comes only from what I've already said or written: my films, their descriptions, my old write-ups, my GPS, photos and receipts. Claude never invents an opinion, a rating, a meal or a feeling. When a guide says "I," I did it.
The record also fills gaps. On the Salkantay Trek (the film) I didn't know what the shuttle drop-off was called. My GPS starts there, and the map data names it: Challacancha, above Mollepata.
The same rule picks the routes. Claude ranked my films in KraigOS, the database we built to run my work: most-watched first, but only routes I walked with my own GPS. So the list opens with Hornstrandir in Iceland (its films have about 5.4 million views), and there's no Kilimanjaro guide: in that film I turned back before the summit.
The numbers come from my GPS
Every distance, climb and high point is worked out from my GPS files the same way, with the elevation smoothed so small wobbles don't count as climbing. Apps count differently. For Lofoten (the film), AllTrails shows about 20,500 feet of climbing; the guide says about 17,900, and explains why.
GPS has limits too. On the K2 Base Camp trek (the film), my GPS read 5,467 meters at the Gondogoro La. Most published sources say 5,585. The guide gives both and says to plan for the higher one.
The GPX files, one per day plus the whole route, work in AllTrails, Gaia GPS, Garmin or Organic Maps. Timestamps are stripped: you get the line I walked, not when I walked it.
Maps drawn from the GPS
A script draws every map: my GPS line over open elevation data (Mapzen's Terrain Tiles), with lakes, rivers, glaciers and peaks from OpenStreetMap, and no label sitting on the route. Each day's elevation profile shows where the climb is before you start it.
The first maps were, in my note at the time, "grey and boring," so every map was redrawn in one colour style with the route in red, the same relief as my animated map videos.
One design for every guide
My note on the first draft: the content was pretty good, but it "could be designed nicer and have better and more photos." Claude laid out the same pages two ways. I picked the minimal one: white, black and grey with one red, taken from the Alta Via trail signs. The cover is always the film's YouTube thumbnail.
Every guide has the same parts, so once you've used one you know them all:
- Up front: the trip at a glance and straight answers to the five planning questions Claude found in all 272 comments on my two Alta Via 1 films (narrated and ambient): how many days, when to go, how to get beds in the huts, am I fit enough, and what will it cost.
- Each day: usually a big photo, the day's numbers, what happened in my words, and links to that day in my film.
- At the back: what I carried, how to load the GPX files, a dated list of things to check before you go, and a trip sheet to print.
One build script makes every PDF, so a layout fix for one guide fixes all 58.
A second AI checks the first
Before a guide goes on sale, a separate Claude session that didn't write it checks every fact that could change against official sources, every number against the GPS, and the safety details. Newer guides also get a pass from Google's Gemini. The main session then checks the source for every serious finding itself before anything changes. On the Salkantay guide it caught:
- A closing time. The Machu Picchu sanctuary entry at Hidroeléctrica, on Day 3, is open only 7:30 a.m. to 4:30 p.m. (the park service). A slow walker could arrive after it closes. The guide says so now.
- Words I never said. A draft had me calling Machu Picchu "one of the most unique places I've been." In the film I said "you got to visit this spot, it's really unique." The guide uses my words.
The time-sensitive checks run again on launch day. When the Laguna 69 guide went on sale on October 4 (the film), a forest fire had just stopped visits to the lake, so the guide said so from day one. Anything about my story, my opinions or the price comes back to me.
No affiliate links
None in any guide. Where a company was part of my trip, the guide says so: my Salkantay trip was with a local company that helped sponsor the film.
Where to get them
Only on my website: $19 each, or in bundles by region or all together. The PDF and GPX files come in one download, and new editions come to the same link. Every guide's page shows real pages from inside and a free day by email. Not useful? Email me within 30 days for a refund.
What I learned, and what's next
Apps and GPS don't agree on climbing, so pick one method and use it everywhere. And a second AI catches what the first one misses, including words I never said.
Next: sharper photos from my full library, free to buyers as an update, and the next route, Colorado's San Juan Mountains, which is nearly ready.
FAQ
Are the guides written by AI?
Yes. AI builds them, first Codex and now Claude, from my own films, GPS recordings, photos and notes, and never invents an opinion or experience. A second AI checks the facts before a guide goes on sale.
Where does the information come from?
My films, my AllTrails GPS recordings, my photos and my old write-ups. Things that change, like opening hours, permits and prices, are checked against official sources and dated.
What's in a guide?
A PDF with the trip at a glance, straight answers to the big planning questions, every day with its own map and elevation profile, what I carried and a printable trip sheet, plus GPX files.
Are there affiliate links?
No. If a company was part of my trip, the guide says so.
How much is a guide, and how do I get one?
$19 each on my website, or in bundles. The PDF and GPX files download right away, and there's a 30-day refund.
Is there a free sample?
Yes. Every guide's page shows real pages from inside, and you can get one day free by email.