Fort Worth Trek 100
September 20, 2025Fort Worth, TexasReading activity…
The shape of the ride
Four signals. One shared timeline.
A loop through North Texas
Recorded GPS route · no map tiles
Effort, not just distance
Based on FTP 255 W · max HR 185 bpmTraining load
Calculated from the recorded power stream
Your best sustained efforts
Full windows · no bridging pauses or power gaps
Heart rate zones
Five zones · percentage of maximum heart rate
Power zones
Seven Coggan zones · percentage of FTP
What the ride tells us
Observations from your data, not a templateComparing power-to-heart-rate efficiency.
The story is loading
Calculating pacing, cardiovascular response, and time on the road.
A lap-by-lap look
Device distance laps · mostly 8.05 km / 5 mi| Lap | Distance¹ | Timer | Elapsed¹ | Avg speed | Avg power | Avg HR | Gain¹ |
|---|---|---|---|---|---|---|---|
| Parsing lap records… | |||||||
Good analysis starts with honest data
Device comparison & methods
| Metric | This analysis | Device session | Why they may differ |
|---|
Time, pauses & sensor coverage
FIT timer events define active intervals, independently of speed. Moving time is timer-on time above 0.5 m/s (1.8 km/h). Calculations use one-second, left-held samples only across recording intervals ≤2 seconds. Missing or invalid sensors stay missing, never zero. Recorded zero power and cadence are retained; zero HR is invalid. Averages and zones use valid timer-on seconds, including coasting.
Normalized Power & best efforts
NP is the fourth root of the mean fourth power of complete 30-second rolling power averages. Rolling windows restart at every pause or missing power sample. Best efforts are complete, continuous 5 s, 60 s, 300 s and 1,200 s arithmetic means. IF = NP / 255. TSS = timer seconds × NP × IF / (255 × 3,600) × 100; it estimates the full timer duration from available power.
Elevation & distance
Enhanced FIT altitude and speed take precedence. Gain uses a 5-point median altitude filter and 3 m turning-point hysteresis, split at gaps over 10 s; small oscillations are ignored. Distance is the sum of nonnegative recorded odometer increments, rejecting resets and increments implying over 40 m/s. It is not a straight-line GPS estimate. Raw elevation remains visible on the chart.
Decoupling & zone definitions
Pa:HR = 100 × (EF₁ − EF₂) / EF₁, where EF is mean power / mean HR on paired valid timer-on seconds. Halves divide total timer time equally, not elapsed time or distance; all riding, including warm-up and coasting, is included. This is descriptive, not a controlled endurance test. HR bands: <60%, 60–<70%, 70–<80%, 80–<90%, ≥90% of max (sub-50% included in Z1). Coggan upper power boundaries: 55%, 75%, 90%, 105%, 120%, 150%, then >150% FTP. Zone percentages use valid sensor time.
Binary parsing & integrity
The in-page parser reads FIT definitions, byte order, compressed timestamps, base-type invalid sentinels and developer-field lengths. Header and file CRCs are checked. Unknown messages are safely skipped; developer fields are not used for these calculations.
Charts & route
Charts show 10-second elapsed-time bins, independently averaged per sensor (not used for metric calculations). Missing bins remain gaps; time view shades timer pauses. The distance view compresses stops. Hover or use arrow keys for the exact second and a linked route marker. The route is a local north-up equirectangular projection, with gaps and implausible GPS jumps disconnected. No tiles or external libraries.