OFFLINE VECTOR COMPILATION
Long-distance navigation fails the moment it relies on an active cellular handshake. My routing methodology is built on a strict baseline: The map must exist entirely inside the machine.
The 6-Stage Route Compiling Process
01. Google My Maps: Plot points of interest and rough route using Google My Maps.
02. Strava: Plot baseline point-to-point tracks, utilising platform snap-to-road logic to establish raw distance, elevation profiles and utilise the best roads.
03. .gpx: Export the raw coordinate string to strip away proprietary platform UI layers.
04. Google My Maps: Upload the raw .gpx track as a base layer to create an editable master spatial canvas.
05. Custom Waypoints: Manually plot critical survival infrastructure along the track (supermarkets, potable water taps, bivouac & camping zones). Assign strict colour-coding to each waypoint class to allow for 1-second visual triage in the field under fatigue.
06. Maps.me (.kml): Export the canvas as a lightweight .kml file and compile it directly into local mobile vector storage. Zero cell-tower reliance.
.jpg)
FIELD HARDWARE NOTE // COCKPIT REDUNDANCY (2017)
Pre-dating modern Quad-Lock ecosystems, cockpit device mounting was engineered by taking a lighter and burning two anchor slots through the rear of a rigid polycarbonate phone case, and cinching it to the stem with 4.8mm nylon cable ties.
Primary routing ran on this cockpit terminal; an identical, fully compiled backup phone sat powered-down inside the frame pack. If the primary unit suffered a catastrophic descent impact, navigational downtime was limited to a 60-second hardware swap.