You have the GPX file. You have the app. You have a phone that was fully charged an hour ago. Then, at a fork above the tree line, the blue dot drifts, the screen dims, and the line points into a patch of scree that looks nothing like a trail. This is where phone navigation usually fails, and it is almost always preventable before you leave the car park.
Start with the route file, not the app
A GPX file is not a map. It is a set of coordinates: a track of where someone walked, a route of planned turns, or a handful of waypoints. Open the file at home in the app you will use on the hill. Zoom in until you can see the whole day. Check the start point, the finish, and every junction where the line changes direction. If the track cuts straight across switchbacks, it may be simplified or badly drawn. Treat it as a hint, not a survey.
Track or route?
A recorded track shows where a person actually went, including detours and mistakes. A planned route may follow paths that no longer exist on the ground. Read the file’s name and source. An official park route, a guidebook download, and a stranger’s uploaded loop are not equal. If the line crosses a closure or a private property boundary, delete it from your plan.
Rename the file so it makes sense on a small screen: “Saturday – Passo X to Rifugio Y” is better than “track_2024_final.gpx”. Add waypoints for the trailhead, a reliable water point, and two escape routes. Keep the original file untouched; save the edited version separately.
Save the map, not just the line
A GPX line without a stored map is just a thin line on a blank background. Before you leave, download the map area you will walk, not only the corridor around the route. Include the valley below, a nearby road, and an alternative descent. If the weather turns, you may need to leave the planned line sooner than expected.
Use the offline map function in your app and choose a scale that shows paths, contours, and land cover. Download at home on Wi-Fi, then switch the phone to airplane mode and open the map at the trailhead. If tiles are missing, you will see grey squares; fix that before you start walking. Some apps keep offline maps for a limited period and some need periodic online verification, so check the download settings rather than assuming it will work forever.
Test it before you need it
Walk a short local loop with the phone in airplane mode. Learn how to open the map, centre on your location, measure distance, and drop a pin without a signal. On the hill is the wrong time to discover that the map layer you saved was a road map without trails.
Make a one-page route plan
A route sheet is a small piece of paper, or a note on the back of the map, that tells you what you expect to happen. It takes ten minutes to make and it keeps the phone in your pocket.
- Trailhead and parking, including the road name and any turnoff.
- Planned route with key junctions and distances between them.
- Expected total time, plus a turn-around time.
- Escape routes and the nearest road or valley.
- Water points, huts, and shelters that are likely to be open.
- Emergency contact and the local mountain rescue number.
Write down the GPX file name and where it is stored on the phone. If you are hiking with someone else, send them the file and the route sheet before you leave. A second copy on a partner’s phone is useful, but it is not a substitute for paper; phones get dropped, wet, and cold.
On the trail, the phone stays in your pack
The phone is a backup. The paper map and compass are the primary tools, with the GPX line used to confirm a decision at a junction. That order matters. If you follow the screen continuously, you stop reading the ground: the shape of the valley, the direction of the sun, the path that is actually under your boots.
Keep the phone in airplane mode or battery saver, with the screen brightness low. Check it at junctions, at path crossings, and when the trail becomes unclear, then put it away. Start tracking at the trailhead if your app allows it; the recorded track is a useful record if you need to retrace steps. Mark the car park as a waypoint. In cold weather, keep the phone in an inside pocket and carry a small power bank, because batteries lose capacity quickly when they are cold.
When the screen and the trail disagree
A GPX line is a record of where someone went, not a promise that the ground still looks the same. Trails are rerouted, bridges wash out, and winter snow can hide a path for months. If the line points through a closure, a scree slope, or a river with no bridge, do not follow it just because the screen says so. Stop, compare the paper map, the contours, and what you can see.
GPS accuracy is not uniform. Under cliffs, in deep valleys, and in dense trees, the blue dot can wander by tens of metres. A straight line on the screen may cross a cliff edge or a property boundary that is obvious on the map. If you are off track, stop early. Walk back to the last certain point rather than cutting across country to rejoin the line. If you are genuinely unsure, stay on the trail you know and turn around; a shorter day is better than a search and rescue call.
A simple pre-hike checklist
- Phone charged, with a power bank and cable.
- GPX file opened and saved in the app.
- Offline map downloaded and tested in airplane mode.
- Paper map and compass, plus a route sheet.
- Headlamp, water, warm layer, and a small first-aid kit.
- A plan for turning back if time or weather changes.
Use the phone as a backup, not a crutch
Good navigation is a habit, not a download. Before the hike, spend ten minutes checking the file, saving the map, and writing the route sheet. On the trail, look up, read the ground, and use the phone to answer a specific question: “Is this the junction?” rather than “Where am I?” If the screen dies, the paper map still works. If the paper map blows away, the phone may still work. Carrying both is not old-fashioned; it is what gives you the confidence to walk without staring at a screen.
Photo: DariuszSankowski / Pixabay
