{
  "$type": "site.standard.document",
  "createdAt": "2026-04-20T22:44:00+01:00",
  "description": "Claude is also a valuable companion, well, not on the moors per se, but at your desk before you go out onto the moors, to escape from Claude.",
  "path": "/stream/claude-code-for-fell-running",
  "publishedAt": "2026-04-20T22:44:00+01:00",
  "site": "at://did:plc:swxoj3wjlwodcqs5ipmvgnug/site.standard.publication/3mnv7gbn3czno",
  "tags": [
    "Claude",
    "AI",
    "Running",
    "The Fellsman"
  ],
  "textContent": "I’ve got a big run coming up, and I want to be prepared, so I created a GPX file to load onto my watch so that I can follow a little red line across the Yorkshire Dales.A little red line alone is a big help, but a bigger help would be to have the checkpoints on the watch as well, so that when it’s been dark for hours and I’m stumbling through peat hags, I can know that I’m only 2 km away from Capplestone Gate. Or whatever.The problem is that manually adding checkpoints to a GPX file is a tedious prospect in Garmin Connect. The solution is that I have a monthly subscription to the Do Tedious Things For Me robot.Claude Code made short work of the GPX file: I pasted in a screenshot from the event handbook listing the OS grid references for each of the checkpoints, and it parsed those checkpoints first into a CSV and then interpolated them into the GPX file itself. Names and lng/lats, and, with a little further prompting, elevations for each of the waypoints.I uploaded this file to Garmin Connect but found that some of the waypoints were missing; Claude discovered that the grid references provided (to 100m precision) weren’t always exactly on the plotted route. It tweaked the file; I reuploaded: success.",
  "title": "Claude Code for fell running",
  "updatedAt": "2026-04-20T22:44:31+01:00"
}