Changing Display Units Mid-Season: What Recalculates and What Stays Historical
5 min read
Changing display units mid-season? Learn what usually changes on screen, what may stay historical, and the checks to run before trusting the new numbers.
On this page
Treat unit changes as a display-layer setting until you verify raw exports, timestamps, and stored fields.
I could not locate PubMed-indexed literature that documents how consumer training platforms handle mid-season display-unit changes. This guide is a practical data-check workflow, not a physiology claim or a platform-wide rule.
Switching from kilometers to miles, meters to feet, or one power view to another often changes what you see first. Treat that switch as a display-layer setting until you prove the stored data changed.
Raw ride files usually include fields such as timestamps, GPS traces, and sensor values. Because platform rules differ, check the file rather than guessing from the chart labels.
If you use N+One, start with your unit settings in N+One and then check the profile values that shape targets. The key point is simple: the label can change while the stored field may not.
Treat the unit switch as display-only until proven otherwise.
Export one raw file before changing more settings.
Check timestamps, GPS fields, and raw sensor values.
Verify thresholds and zones after the switch.
Photo by Fredo Gerdes on Unsplash.
A platform may recalculate values that are built from stored fields and shown on demand. Distance, speed, pace, elevation labels, and unit-based zones are common places to check.
Some summary screens may update right away because the app can redraw the same file through a new unit lens. That does not prove the original file was rewritten.
For N+One users, align this check with profile weight, FTP, and zones. If your displayed threshold changes, confirm whether the platform converted the stored value or only changed the label.
Check distance, speed, pace, and elevation displays.
Open zones after the switch and compare values.
Do not infer raw-file changes from charts alone.
Export one file and inspect stored fields.
Keep training targets stable while you confirm what changed.
In N+One terms: the numbers’ labels change; the training signal you recorded stays the same until the stored data says otherwise.
I couldn’t find peer-reviewed PubMed evidence directly addressing how platforms recalculate historical metrics when you change display un…
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Historical integrity matters because coaches and athletes compare work across time. If a display change rewrites nothing, your past files can still be used as the audit trail.
Original files, timestamps, and stored numeric fields are the first items to protect. If you share data with a coach, note the switch date before any trend review.
When reviewing form, avoid judging a new chart scale as new fitness. Use trend checks without cherry-picking so the unit shift does not drive the story.
Keep original FIT, TCX, GPX, CSV, or JSON files.
Write down the unit-change date in your log.
Tell your coach before comparing past blocks.
Save screenshots only as display records, not proof.
Run three checks before you make training changes from the new numbers. First, open a recent ride and confirm timestamps and raw fields look sensible.
Second, check the threshold or zone values that shape daily targets. A platform may show converted numbers, stored numbers, or both depending on its design.
Third, export one file and inspect it outside the summary page. If needed, use your N+One data export options to compare fields before and after the switch.
Open one recent ride file.
Check raw timestamps and sensor fields.
Compare threshold and zone displays.
Export one file after the change.
Record what changed and what did not.
The goal is steady training while the data layer gets checked.
In N+One terms: keep intensity targets stable; change only the labels unless you explicitly convert.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Privacy and your data — How N+One collects, uses, and lets you control your cycling data—exports, deletions, integrations, and where to get help.
- Two-Factor Authentication and Account Security for N+One Users — Set up two-factor authentication for your N+One account, choose a secure backup method, and build a simple recovery plan before travel or race day.
- Multi-Device Login With N+One: Phone, Tablet, and Garmin Companion App — Set up N+One across phone, tablet, and Garmin Companion with a cautious checklist, troubleshooting steps, and a one-week verification protocol.
Once the data check is clean, choose one rule for the rest of the season. Either keep the new display units locked, or document each change with enough detail to audit later.
If you work with a coach, share the date and the values that changed on screen. You can also use read-only plan sharing so the coach can see the same context.
For ongoing review, keep your weekly check plain and repeatable. Pair this workflow with the N+One weekly review so charts do not outrun the data.
Lock one display unit for the season when possible.
Write down both old and new threshold displays.
Share the switch date with your coach.
Reprocess only files needed for a clear task.
The most common trap is a silent conversion. Your chart looks clean, but a stored threshold or exported summary may not match what you think changed.
Paired devices can also keep their own unit settings. Change the setting on the head unit, app, and connected platform before you compare numbers.
If the mismatch persists, revert the setting and re-export the original file. For account-level questions, use N+One help and support rather than making a training call from unclear data.
Check platform and device settings separately.
Compare old and new threshold displays.
Re-download the original ride file when unsure.
Ask support whether exports rewrite stored values.
Step 1 — Immediate, same day: Open one recent ride on the platform and confirm raw sensor numbers, GPS coordinates, and timestamps match the original device export. Note the displayed threshold value and the pre-change value in your log.
Step 2 — Short term, next 7 days: Keep training intensity the same. If the platform shows converted threshold values, accept the converted number only after you record both values and the change date.
Step 3 — Recheck at 14 days: Export one or two session files and inspect fields to see whether exports preserved raw values. Reprocess only the files needed for a specific analysis, and document the conversion factors used.
Single decisive move: Keep intensity steady, trim session volume slightly for seven days while you confirm data integrity, then resume your normal plan when the export check is clean.
Treat unit changes as a display-layer setting until you verify raw exports, timestamps, and stored fields. Your next move is not to change training targets; it is to confirm what the platform recalculated and what stayed historical.
Do not assume it will. Treat the change as display-only until you export a file and compare stored fields, timestamps, and platform summaries.
No. A unit switch alone is not a training signal. First verify whether the platform converted your stored threshold or only changed the visible label.
Check unit settings on both devices and the platform. Paired devices can keep local settings, so align them before comparing rides.
Only do that when you need consistent units for a specific analysis. Preserve originals so you still have an audit trail.