ViewRanger will provide topo maps of the entire trekking area, but these would be of limited use without the route highlighted. The GHT is infrequently trekked, so there’s relatively few digital resources available. For the more popular ares, the ViewRanger topo maps often include footpaths - but for much of the trek there is nothing plotted on the map.
I’ve tried to bring all the available GPS resources together in this section:
- Robin Boustead published a collection of waypoints.
- Himalayan Adventure Labs also publish a collection of waypoints which include some of (but not all of) Robin’s.
- Seth Wolpin and Doc McKerr both recorded tracks of their thru-hikes, which Himalayan Adventure Labs merged into a set of tracks with excellent notes.
Seth’s track is a great resource, but some sections deviate significantly from our intended route. Robin’s waypoints follow our route, but aren’t connected with a track. I wanted a better option covering the whole route and following the Himalaya Map House paper maps. I also wanted each day of our itinerary to be a separate route segment. Finally I wanted each segment to match up with our paper flashcards (see the Navigation - Flashcards article), so I could extract the stats and elevation profile. To create this I used gpsies.com, which is an invaluable online service. A GPX route can be created by simply drawing points onto the map. A handy time-saver is the GraphHopper feature, which automatically adds a section of route by following footpaths. Not all the footpaths found on the topo maps have routable paths, but most do. Where footpaths weren’t drawn on the map I’ve estimated the position of the trail from the 1:150k scale Himalaya Map House paper maps.
While creating the flashcards I created 115 separate GPX files in this way, then merged them into a single GPX file containing 115 route segments. It should be noted that this route is only as accurate as the highlighted route on the paper maps, which will not be 100% perfect. However, most of it matches up almost perfectly with Seth’s recorded track, so I’m optimistic that it’s a good enough estimation.
I also merged and de-duplicated the waypoint databases from Robin and Himalayan Adventure Labs, and normalised the formatting of the names. I created a set of km markers for each day, which are useful for emergency navigation, and assigned each waypoint to the nearest marker to generate a unique code.
You can find the final files here:
- Routes - All 115 daily routes merged into a single file in GPX or KML format. If you need the routes as 115 individual GPX files, here’s a zip.
- Markers - All 1432 km markers in GPX or KML format. I’ve found a frustrating limitation of 1000 waypoints on the Garmin Fenix 5 watch. I can’t find any way around is, so I’ve created a set of km markers containing only one in 3 markers. So each day has a marker at 0km, 3km, 6km etc. This gives 516 markers, added to the 475 waypoints gives 991 in total. You can find the reduced marker file in GPX format here.
- Waypoints - A file containing all 475 waypoints in GPX and KML format can be found in the Himalayan Adventure Labs file repository, which is linked on their Interactive Map page. Look for the Dave Brophy’s files directory, and the files are called waypoints.gpx and waypoints.kml.
- Tracks - A single file containing the 10 Himalayan Adventure Labs tracks in GPX and KML formats can be found in their file repository, which is linked on their Interactive Map page. Look for the Dave Brophy’s files directory, and the files are called himalayan-adventure-labs-tracks.gpx and himalayan-adventure-labs-tracks.kml.
If you’d like to know how I manipulated the GPX files, here’s the source code.
Here’s a demo of how to load KML routes into Google Earth, which gives an excellent 3D visualisation: