Ingest FIT files for calibration

Use this workflow when you want TRIPS to build a local calibration dataset from your own historical .fit activity files.

This article is for the ingest procedure itself.

If you still need to decide whether calibration is worth doing, read Optional calibration.

If ingest has already finished and you need to judge whether the dataset is usable, read How to use diagnostics after FIT ingestion.

Before you start

Use FIT files that are reasonably representative of the kind of travel you want to plan for.

If you are still deciding what belongs in the folder, read:

Best results come from files that include:

  • hiking, backpacking, or mountain travel rather than unrelated activities
  • moving time, distance, elevation, and heart rate
  • multiple outings across a range of grades
  • typical pack loads and pacing for your real use

Do not use a folder dominated by:

  • running, cycling, or gym sessions
  • incomplete heart-rate coverage
  • highly unusual one-off efforts
  • activities that do not resemble the trips you want to plan

Basic workflow

  1. Open the Calibration tool from the planner.
  2. Go to the Ingest tab.
  3. Select a folder containing one or more .fit files.
  4. Review the preflight message before continuing.
  5. If the folder size looks acceptable, choose Continue Ingest.
  6. Wait for TRIPS to finish building the local calibration snapshot.

What to do immediately after ingest

After ingest finishes:

  1. Open the FIT File Ingest Summary.
  2. Check whether the ingest completed without blocking warnings.
  3. Continue to the diagnostics article for dataset review.

Use How to use diagnostics after FIT ingestion for the actual go/no-go decision about dataset quality.

Important note about persistence

FIT ingest is treated as local workspace data in your current browser.

In practice, that means:

  • the same browser can often restore a derived calibration snapshot after refresh
  • raw FIT files are not synced across devices
  • some later validation or export actions may require re-upload after refresh

If a workflow depends on the original uploaded FIT bytes, assume re-upload may be required unless the files were uploaded again in your current browser session.

For related troubleshooting, see:

What to do next

After ingest completes, continue to:

Still need help? Send a Little Note to Backpacking Light Send a Little Note to Backpacking Light