Analytics glossary
Every metric on the trip dashboard is computed from your raw GPS points. This page explains what each one means, how it's calculated, and what it doesn't capture.
Distance
The total length of your route, in kilometres. Computed by the Haversine formula across consecutive GPS points: each pair of adjacent points contributes a great-circle distance, and the total is their sum. Same number you'd get from a fitness tracker, give or take GPS noise.
Moving time
Total time during which you were actually moving, as opposed to stopped at a viewpoint, café, or hostel. We classify any pair of adjacent points whose mean speed is below a threshold (per transport mode — about 0.4 km/h for walking) as "stopped" and exclude that interval from moving time.
Stopped time
The complement of moving time. Useful for backing out a realistic "trip duration including breaks" — moving time alone undercounts real elapsed time on long days.
Average speed
distance / moving time. Excludes time spent stopped, so the number
matches your honest pace, not your slow-due-to-coffee average.
Elevation gain / loss
Cumulative metres climbed and descended along the route. We smooth the altitude track first (raw GPS altitude is noisy — easily ±5 m per fix) and then sum positive and negative changes. The smoothing is why the number is usually lower than what your watch reports, but it's closer to physical reality.
Naismith's rule (terrain-adjusted distance)
Naismith's rule estimates how long a hike "feels" by adding 10 minutes per 100 m of climbing to the flat-distance walking time. We invert it to give you an equivalent flat distance — what your route would cost on perfectly flat ground. A 20 km flat walk and a 12 km walk with 800 m of climbing might both yield ~20 km equivalent.
This is what makes mountain trips and coastal trips comparable.
Terrain difficulty index
A normalized score from 0–100 based on Naismith equivalent vs. raw distance. 0 = perfectly flat. 100 = a vertical staircase. Useful for ranking trips on the leaderboard fairly.
Pace efficiency
naismith equivalent / actual distance × 100. Tells you how hard
your route was per kilometre traveled. 100% = flat ground; 130% = a
lot of climbing.
Energy expenditure (kcal)
A rough estimate using a metabolic equivalents (MET) lookup per transport mode and a 70 kg reference body weight. Walking ≈ 4 MET, running ≈ 8 MET, cycling depends on speed. We don't account for your actual weight, fitness, wind, or the quality of last night's sleep — treat the number as a comparator, not a calorie counter.
Transport mode classification
We classify each point as walking / running / cycling / driving / public transport / boat / flying based on:
- Speed (sliding window mean over the last few points).
- Acceleration smoothness.
- iOS motion activity if the source device provides it.
The classifier is conservative on transitions — a single fast point in a walking sequence won't flip the whole sequence to driving. Per- trip overrides are available in the admin.
Stops
Stops are auto-detected as gaps where you stayed within ~30 m of a centroid for at least 5 minutes. Each stop has a centroid (lat/lng) and a duration. Useful for distinguishing "rest stops" from "I'm just walking slowly."
Daily totals
The dashboard shows distance, elevation, and active hours per calendar day in your organization's timezone. Days with zero movement are shown as rest days; partial days at the trip start/end get partial values.
Need help? Contact support · Where Is Tereza?