Features

Reference overview · last updated 1 August 2026

Velometry turns one description template into rich, personal Strava write-ups — filling in the ride metrics that matter, automatically. Here is what the app does today, area by area.

Strava & login

You connect through Strava's official OAuth2 flow — that single action is your login, so there is no separate account and no password. Velometry reads your activities on your behalf and refreshes its access automatically when tokens expire. You can revoke access from your Strava settings at any time.

Strava webhooks notify Velometry the moment a new activity lands. As soon as a new activity is created, Velometry renders your template and writes the finished description straight to that activity on Strava — hands-free. The work runs in the background, so Strava gets its instant acknowledgement while your description is generated and published a moment later.

Rides only. Velometry writes descriptions for bike rides — outdoor rides and indoor/virtual rides, including gravel and MTB, which Strava reports as ordinary rides. Runs, swims, walks and e-bike rides are left completely alone: nothing is computed for them and nothing is written to them. A season average built from cycling has no meaning on a run, so rather than print a misleading number, Velometry stays out of the way.

Metrics

Metrics are organised into families, and Velometry only computes the families your template actually uses — a family with no matching tokens triggers zero Strava calls.

Wind Factor Premium · Free

The signature family. From an activity's GPS track, the wind-factor engine at windfactor.cc computes how much the wind was helping or hurting you and breaks it down:

• {wind_factor} — the overall head / side / tail balance for the ride, as a signed number centred on zero: minus means the wind fought you, plus means it pushed you, and the further from zero the stronger the effect (-0.86 on a mostly-headwind day). It scales with your speed as well as the wind, because drag grows with the square of how fast you ride;
• {head_wind_percent}, {side_wind_percent}, {tail_wind_percent} — the percentage shares;
• {head_wind_factor}, {side_wind_factor}, {tail_wind_factor} — the same signed factor per component: headwind is never positive, tailwind never negative, and sidewind sits near zero because a crosswind barely pushes along your direction of travel (for its strength use {side_crosswind});
• {average_wind_speed}, {average_wind_direction}, {side_crosswind} — wind speed and directions;
• {wind_direction_indicator} — a compass arrow (↗) for where the wind blows.

Premium in quality, free to use. Velometry sends only the GPS streams and receives the wind breakdown back. For what these numbers mean and how they are worked out, see wind data on Strava.

Ride top segments Arrives later

The same wind analysis, narrowed to the segment efforts that landed in a leaderboard's overall top 10 — so a KOM comes with the context of what the wind was doing while you took it:

• {ride_koms}, {ride_top10s} — how many KOMs and top-10 efforts this ride produced;
• {ride_koms_wind_factor}, {ride_top10s_wind_factor} — the average wind factor across those efforts, on the same signed scale: -0.42 means you took them into the wind, 0.18 means it was helping;
• {ride_koms_list}, {ride_top10s_list} — the segments themselves, one per line, crown first and keycap digits for the rest:

👑 Dół (siodło) Kopytówka | WF: 1.88
👑 Paszkówka - Kopytówka | WF: 1.71
2️⃣ Leńcze od Podolan | WF: 0.21
2️⃣ Leńcze pod Kościół-Grabie | WF: 0.73

Those two are blocks rather than single values, so give them a line of their own in the template. The layout is the one windfactor.cc writes itself, so nothing changes shape if you came from there.

Strava does not hand out segment ranks the moment a ride uploads — they land a few minutes later. Velometry does not paper over that with a placeholder or a misleading zero: a line whose numbers are not in yet is left out of the description entirely, and the description is rewritten with the full line once they arrive (two attempts, over about seven minutes). The same rule covers a ride that simply had no KOM: nothing to say, nothing written. Put these tokens on their own line and the rest of your description is never affected.

Year to date

Season totals for your rides, computed as of the activity itself — a retro description shows the YTD state from the moment you rode, not "up to today". Everything is calculated live and converted to sensible units (km, m, km/h, kJ, and saddle time as 143h 20min):

• {distance_ytd} — total distance this year;
• {elevation_gain_ytd} — total climbing this year;
• {avg_speed_ytd} — time-weighted average speed;
• {avg_power_ytd} — time-weighted average power (rides with a meter; n/a otherwise);
• {avg_speed_ytd_impact}, {avg_power_ytd_impact} — how much this ride shifted each average (signed);
• {ride_count_ytd}, {active_days_ytd} — how many rides, and on how many separate days;
• {moving_time_ytd} — time actually spent riding this year;
• {avg_distance_ytd} — your average ride length;
• {climb_rate_ytd} — metres climbed per kilometre ridden, so a hilly season reads high even if the totals don't;
• {distance_rank_ytd} — where this ride ranks by distance among every ride this year;
• {avg_hr_ytd} — time-weighted average heart rate (rides with a strap; n/a otherwise);
• {energy_ytd} — total energy burned in kilojoules;
• {moving_time_ratio_ytd} — the share of your total time out that was actually spent moving.

This week

The same fifteen measurements over a shorter window: from Monday 00:00 of the week your ride belongs to, up to that ride. The week is Monday-to-Sunday and resets every Monday, so a Sunday-evening ride still closes the week it belongs to rather than opening the next one. Every token is its year-to-date twin with _ytd swapped for _week:

• {distance_week}, {elevation_gain_week}, {moving_time_week} — the week's totals;
• {ride_count_week}, {active_days_week} — rides this week, and on how many of the seven days;
• {avg_speed_week}, {avg_power_week}, {avg_hr_week}, {avg_distance_week}, {climb_rate_week} — the week's averages;
• {avg_speed_week_impact}, {avg_power_week_impact} — how much this ride shifted the week's averages (signed);
• {distance_rank_week}, {energy_week}, {moving_time_ratio_week} — where the ride ranks this week, energy burned, and your moving-time share.

Description templates

You keep one template, and it is your own words plus metric tokens: write a normal sentence in your own style and drop in placeholders like {wind_factor} wherever you want a live number. On each ride the tokens become real values and every other word stays exactly as you wrote it, so you are never limited to bare tokens. Add a token by typing a {token} by hand, or click one from the available-metrics list, grouped by family with one metric per row showing its token and an example value with units, so you can see how it renders before adding it. Saving validates every placeholder and rejects unknown ones, so a template can't silently break.

The editor also offers predefined templates — ready-made starting points that load into the editor with one click, ready for you to tweak: a full WindFactor breakdown, a wind one-liner, a year-to-date season summary, a wind + season combo, a narrative “headwind hero”, a week-so-far recap, week versus season side by side, a climber's log, an engine-room readout of power and heart rate, a distance-rank “ride of the year?”, a coffee-stop audit of your moving-time share, and a maximalist three-line combo. All fifteen are shown with their rendered output on the Strava description ideas page.

Once saved, your template runs automatically on every new ride: Velometry fills in the real numbers and publishes the description to Strava for you. Every generated description signs off with //velometry.cc.

Admin panel

Signing in takes you straight to the admin panel, which opens on the template editor. It's a focused workspace: your template on one tab, predefined templates on another, your recent rides on a third, and nothing else to configure. On a phone the three tabs move to a bar fixed at the bottom of the screen, so every view stays one tap away.

Changed your template? Apply it to earlier rides. The Recent rides tab lists your last 10 rides, each with a Regenerate button: Velometry re-renders your current template for that ride and writes the fresh description straight to Strava, replacing the old one. Handy after you tweak the wording — no need to wait for the next upload.

Privacy & data

Velometry is built to hold as little as possible. Metrics are computed on demand and, in line with the Strava API Agreement, nothing derived from your Strava activities is persisted. We store only what's needed to run the service — your Strava identity, the access tokens, and your template. No Strava data is ever used for analytics, advertising, AI training, or shared with third parties. The public website uses strictly necessary cookies plus — only if you opt in — Google Analytics for anonymous usage stats; your Strava data is never sent to Google.

Revoke any time, and your data is gone. The moment you disconnect Velometry from your Strava account (or delete your Strava account), Strava notifies us and we automatically and permanently erase everything we hold for you — your Strava identity, access tokens, stored webhook events, and your template. The same erasure runs on request to privacy@velometry.cc. All we keep afterwards is a minimal record that the deletion happened (your athlete id and a timestamp, nothing from your activities), so we can certify the erasure to Strava.

Full details are in the Privacy Policy and the Cookie Policy.

Guides

Two longer reads go deeper than this overview:

• Strava description ideas — all fifteen predefined templates with the description they produce on Strava, plus what makes a description worth reading.
• Wind data on Strava — why Strava shows no wind, how the head / side / tail split is derived from your GPS track, and what the wind factor actually measures.

Connect with Strava