Support · GPX

A usable track needs time, coordinates, and continuity.

LensPin currently reads GPX 1.1 track points. Each usable point needs valid latitude, longitude, and a timestamp so a camera capture can be aligned to the route.

Reviewed

Required point shape

<trkpt lat="…" lon="…">
<time>…</time>

Need to create or export the file first?

Start with the GPX acquisition guide for iPhone, Apple Watch, Garmin, COROS, and Suunto.

Accepted input

  • A readable GPX 1.1 XML file.
  • One or more trkseg sections containing trkpt entries.
  • Valid latitude and longitude on each usable point.
  • A valid time value on each usable point.

What does not work

  • A route drawn without timestamps.
  • Waypoints alone when no timed track points exist.
  • A malformed XML file or unsupported text encoding.
  • A file whose points all have missing or invalid coordinates or times.

Segment boundaries matter

LensPin preserves the GPX file's original track segments. It also splits a segment at an implausible jump faster than 350 m/s. It never interpolates a photo across either kind of boundary.

Maximum point interval

Your matching setting controls how far apart surrounding GPX points may be and still support a suggestion. A visually connected line with a large time gap is treated as sparse or unavailable evidence, not as proof of continuous travel.

Common messages

File cannot be read

Confirm it is a local, accessible GPX file and that another app can open or export it again.

Invalid GPX format

The XML structure is malformed or the expected GPX track elements are missing.

No timed track points

The file may contain a route shape but no points with both a valid coordinate and time.

No continuous coverage

The file imported, but the selected photo time lies outside the track or across a segment or point gap.

Before changing the file

  1. Check whether the camera clock, not the GPX time, needs an offset.
  2. Confirm the trip date and time zone with one photo whose place you remember.
  3. Inspect original segment boundaries in the recording app.
  4. Avoid merging unrelated segments simply to force a match.

How to get a timestamped GPX file →
Return to the complete GPX workflow →