A triathlon training log
Garmy vault/Guides/A triathlon training log
Guides/obsidian-triathlon-training-log.md

A triathlon training log in Obsidian from Garmin

Properties
sports
runbikeswimstrength
blocks
statsdashy-chartheatmapprogresscountdown
fields
run_km run_min bike_km bike_min swim_km swim_min strength_min
needs Dashy
needs a Garmin key
checked on
Garmy 1.1.2

Run, bike, swim and strength per week, a month calendar, a year map by sport and monthly goals, from the activities on your Garmin watch. Garmy loads the activities and writes the blocks. This page shows what they are and what each key does.

Weekly training minutes as grouped bars per sport and a November month calendar with a dot per sport
Weekly bars and a month calendar, on demo data.

What Garmy reads from your watch

Garmy reads your Garmin activities and sums them per local day into seven properties. Several workouts on one day add up, even when Garmin returns them on different pages.

SportGarmin activity typesProperties
Runrunning trail_running treadmill_running track_running virtual_run street_runningrun_km run_min
Bikecycling road_biking indoor_cycling mountain_biking gravel_cycling virtual_ride e_bike_fitnessbike_km bike_min
Swimlap_swimming open_water_swimmingswim_km swim_min
Strengthstrength_trainingstrength_min
Multi-sport is not split

A triathlon recorded as one multi-sport activity is not divided into swim, bike and run, so it adds nothing to those three sports. Other activity types, such as hiking or yoga, are not counted either. Record the legs as separate activities if you want them in the log.

1Build the training part

Run Garmy: Build a Garmin dashboard, load the period you want and on Choose keep Training. The Sports chips list only the sports found in your data, so a swim chip appears once a swim is in the history. Untick a sport to leave it out.

The Choose step: a library of dashboard kinds, from Everything and Morning glance to Run, Bike, Swim and Strength, Everything selected
The Choose step. Sports are listed from your own data.

2Cards for the last 7 days

Garmin dashboard.md
```stats
columns: 4
source: Garmy/data
period: 7d
items:
  - { label: Run, field: run_km, agg: sum, precision: 1, unit: " km", icon: 🏃, compare: true, better: up }
  - { label: Bike, field: bike_km, agg: sum, precision: 0, unit: " km", icon: 🚴, compare: true, better: up }
  - { label: Swim, field: swim_km, agg: sum, precision: 1, unit: " km", icon: 🏊, compare: true, better: up }
  - { label: Strength, field: strength_min, agg: sum, precision: 0, icon: 🏋️, compare: true, better: up }
```
  • period: 7dThe last 7 days.
  • agg: sumKilometres for run, bike and swim, minutes for strength.
  • compare: trueShows the change against the period before. Written once you have 14 days of data.
  • precisionDecimals: one for run and swim, none for bike and strength.

3Weekly bars

Minutes per sport, a bar group per week. With 28 days of data or more the bars are weekly. With less, Garmy draws daily bars.

Garmin dashboard.md
```dashy-chart
source: Garmy/data
type: bar
bucket: week
range: 119d
agg: sum
title: Training minutes
series:
  - { field: run_min, label: Run, color: green }
  - { field: bike_min, label: Bike, color: blue }
  - { field: swim_min, label: Swim, color: cyan }
  - { field: strength_min, label: Strength, color: orange }
```
  • bucket: weekOne group of bars per week.
  • range: 119dYour history rounded down to whole weeks, at least 28 days and at most 182.
  • seriesOne bar per sport, coloured green, blue, cyan and orange.
Weekly training minutes as grouped bars for run, bike, swim and strength, and a November month calendar
Weekly bars and the month calendar, on demo data.

4Month calendar and year map

Two heatmaps follow. The month calendar needs 7 days of data, the year map 60. Each day is coloured by the sport with the most minutes that day. The heatmap guide goes through both.

5Monthly goals from your own numbers

Garmy sums each sport over your last 28 days, adds 10 percent and rounds up to a round number. That becomes the goal for the calendar month. It needs 28 days of data, and a sport with nothing in those 28 days gets no goal.

Garmin dashboard.md
```progress
source: Garmy/data
period: month
columns: 2
items:
  - { label: Run, field: run_km, agg: sum, goal: 200, unit: " km", icon: 🏃 }
  - { label: Bike, field: bike_km, agg: sum, goal: 500, unit: " km", icon: 🚴 }
  - { label: Swim, field: swim_km, agg: sum, goal: 10, unit: " km", icon: 🏊 }
  - { label: Strength, field: strength_min, agg: sum, goal: 500, icon: 🏋️ }
```
A year map by sport and monthly goals for run, bike, swim and strength as progress bars
The year map and the goals, on demo data.

6A countdown to the next race

In the wizard's Options, name a folder where every race is a note with a date property, such as Races. Garmy adds a countdown card.

Races/Half marathon.md
---
date: 2027-05-16
---
Garmin dashboard.md
```countdown
columns: 2
items:
  - { label: Next race, field: date, source: Races, pick: next, icon: 🏁 }
```
  • pick: nextDashy reads date in every note of the folder and counts to the soonest one still ahead. The card shows that note's name.
  • source: RacesThe folder you gave the wizard.

If you leave the folder empty, the countdown is skipped.

Rebuild it as the season goes

The first dashboard after a few days of data has cards only. Run Garmy: Rebuild the dashboard in this note after a month and the bars, year map and goals appear. A sport you start later is picked up too, unless you switched it off in the wizard.