Ingest FIT files for calibration

Use this workflow when you want TRIPS to learn from your own historical .fit activity files instead of relying only on system defaults.

Calibration is optional. FIT ingest is most useful when you have enough representative hiking or backpacking data to make personalization worthwhile.

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:

Prepare a FIT folder for calibration
Which FIT files should I include for calibration?

Best results usually 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

Calibration is less useful when the dataset is 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

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

What to check after ingest

Review the dataset summary and look for:

enough usable moving windows
reasonable uphill and downhill grade coverage
heart-rate coverage that is not too sparse
no obvious mismatch between the files and your intended trip style

If the summary looks weak, it is usually better to improve the dataset than to force the calibration.

Important note about persistence

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

In practice, that means:

the same browser can usually 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:

Understand FIT ingest warnings
Why do I need to re-upload FIT files after refresh?

What to do next

After ingest completes, continue to:

How to use diagnostics after FIT ingestion
Review calibration outputs
How to use the calibration workspace tabs