Telemetry questions often become confusing because “GPS data” can mean several different things. A camera may contain embedded metadata, a phone may record a GPX track, and a sports device may store a richer FIT activity — all from the same trip. This FAQ provides a practical way to think about those sources.

What is embedded camera telemetry?

Some action cameras store sensor information alongside the video. GoPro, for example, uses GPMF metadata. The advantage is timing: video and sensor data originate from the same recording session, so a compatible application can often avoid a separate manual sync step.

What is GPX?

GPX is a common exchange format for GPS tracks. It is useful because many phones, navigation devices and sports applications can export it. The tradeoff is that GPX usually represents an external timeline that must be aligned with the video if the camera did not record it directly.

What is FIT?

FIT is widely used by sports devices and can contain activity data beyond simple latitude and longitude. Depending on the recording device, it may include cadence, heart rate, power and other measurements. Whether an editor can use those values directly is a separate question from whether the file contains them.

Which source should I keep?

Do not reduce everything to a single “master” too early. If you have original camera metadata plus a sports-device activity, archive both. Storage is cheap compared with discovering later that the one export you kept omitted the field you now want.

How do I synchronize an external track?

Choose a distinctive event that appears in both timelines. Good examples include a stop followed by acceleration, a sharp turn, a jump or another visually obvious action. A single matching point establishes an offset; two or more points help reveal whether you also have drift.

Why does telemetry look correct at first and wrong later?

That can indicate true drift rather than a fixed offset. Check whether the video was converted to a different frame-rate interpretation, whether timestamps were altered, or whether the telemetry is being sampled against edited timeline time rather than source time.

What happens after trimming or speed changes?

Simple trimming should preserve the relationship if both media and telemetry are referenced correctly. Speed ramps, freeze frames and reverse playback require more care because source time no longer advances at the same rate as timeline time. A strong telemetry workflow should define what happens in those cases instead of merely displaying a gauge on an untouched clip.

Should missing GPS points be interpolated?

Small gaps may be smoothed for presentation, but a long recording interruption should not automatically become a straight route line that implies travel along an unrecorded path. Good visualizations distinguish filtering from invented data.

What should a useful compatibility chart include?

• Camera and recording setup
• Telemetry source: embedded, GPX, FIT or other
• Editor/tool version
• Direct import or extraction required
• Automatic or manual synchronization
• Behavior after trim, split and speed changes
• Available gauges and units
• Metadata preservation after export or conversion

This is the model Action Video Lab will use for telemetry testing. “Supported” is not a useful answer unless the entire workflow is described.