Directly usable telemetry saves me the most time. I stop adding gauges if the workflow needs too many separate tools.
That would be extremely useful, especially if the metadata and recording setup are documented.
That matches my priorities. The number of extra telemetry steps matters more to me than having every possible color tool.
For an honest route display I would break the line across a real recording/data gap rather than imply travel along a path that was never recorded.
Fair point. Storage is cheap compared with discovering later that the one export I kept omitted a field I now want.
That split is useful: embedded data when available, external track when the camera file is not the best source.
Yes for many projects. The main requirements are a usable track and a reliable way to align its time with the video.
Keep the original video, the original activity/telemetry files and any project/export files that show how they were aligned. Old metadata is much hard...
Keep the original activity source so you can rebuild the overlay without another generation loss.
No. Keep the original camera files and activity data. An exported delivery file should be treated as a rendered result, not as a metadata archive.
A brief stop followed by a clear acceleration works well because it is obvious both in the video and speed trace.