How to import a GPX file into Yamareco

The short answer

When creating or editing a 山行記録 (a hike record) on Yamareco, look for an option to attach or upload a track log rather than draw the route by hand. A GPX file dropped in there gets read point by point — Yamareco pulls the distance, the elevation gain and the line on the map straight out of the file's own coordinates, rather than asking you to trace anything yourself.

Where the GPX file comes from in the first place

A GPX file only exists because something recorded the walk and wrote the points down — latitude, longitude, elevation, and usually a timestamp on each one. Most GPS recorders have an export or share action that does exactly this. TrailCam can export a single route or an entire history this way, in GPX 1.1, which is the version most mapping and record-keeping tools expect.

Getting it into Yamareco

This is the part Yamareco does differently from a lot of mapping apps: it already assumes the track came from somewhere else. The whole site is built around people recording with whatever device or app they had on them and bringing the result in afterward, so a track-log upload is not a hidden or unusual feature — it sits right where a hike record gets created, whether that is on the website or inside the app. There is generally no need to hunt for it in the iPhone share sheet the way you would with an app built to receive files that way; the upload lives inside Yamareco's own record-creation flow instead.

What actually lands, and what it does not

Because Yamareco's whole model already expects the track to have come from elsewhere, an uploaded GPX file becomes a genuine, complete record rather than a plan waiting to be walked — the distance, elevation gain and route line attached to it are read directly from the points in the file, not recalculated by tracing something by hand or guessed from a course someone else built.

What it does not do is bring across anything the GPX format has no field for. Photos, video clips and voice notes captured on the original walk live outside the file entirely. Yamareco's reports are built to carry photos and a written account of the climb alongside the route, but none of that comes from the GPX file itself — it only ever contributes the line, the distance and the elevation. Anything else has to be added to the record separately, the way it would be for any hike written up after the fact.

Things that trip people up

• Expecting the numbers on the finished record to differ from the original track — they should not, since Yamareco is reading the same coordinates the original app recorded, not recalculating the route from a different source.
• Looking for the upload as a share-sheet destination the way it works for a handful of other apps — the upload lives inside Yamareco's own record-creation flow instead, not as something the file gets shared to from outside.
• Assuming photos taken along the way will show up automatically once the GPX file is in — they will not, because GPX has no field for embedded media; they have to be added to the record on their own.
• Elevation gain looking slightly different from what the original recording app reported — worth checking rather than assuming an error, since a site with its own map data can read elevation from its own terrain model instead of the raw values sitting in the file.

Why bring a track into Yamareco at all

Recording and reporting are two different jobs, and plenty of people are happiest splitting them: one device or app captures the walk while it is happening, and a separate site turns that capture into a written record afterward, with the map and the numbers already filled in from the file rather than typed by hand. TrailCam records a route on an iPhone the whole time you are out, and exports it as GPX 1.1 or CSV, either for a single walk or your entire history — the file this whole process starts from. Export is part of the optional TrailCam Pro upgrade; the app itself is free to download.