GARMIN-FORERUNNER-TOOLS(1)

okay so bestie, we're in the General Commands Manual, and the page itself is GARMIN-FORERUNNER-TOOLS(1) — yes it's one lowercase command name living under a big shouty umbrella title, that's just the arrangement, we don't question it 💅

🎀 NAME 🎀

garmin_save_runs — she retrieves track logs from a Forerunner device. that's it, that's the whole job, and she eats every single time 🏃♀️✨

🦋 SYNOPSIS 🦋

garmin_save_runs

so like. garmin_save_runs goes and retrieves track logs from a Garmin Forerunner that's plugged into a USB port, and then saves all of that information into files. no cap 🫶

the files land with the extension .gmn, and they get named by the run's start time — for example '20070121T151814.gmn'. and before you even ask: the .gmn file format is a binary file format, and you can unpack it with the garmin_dump or garmin_gmap utilities. she is substantially more efficient than that bloated XML format Garmin uses. we said what we said 😭

when she's done, the output of garmin_save_runs tells you exactly where on your filesystem those actual .gmn files got saved. the default? a whole directory tree organized by year and month, sitting right under the current directory. organized queen, we're obsessed 📁✨

wanna send her somewhere else instead? set the environment variable GARMIN_SAVE_RUNS to whatever directory you like and she'll go there. that's the override, that's the whole override 🧚

⚠️ heads up bestie: existing files are not overwritten. she will not clobber your babies. periodt.

🌈 SEE ALSO 🌈

• garmin_get_info(1)
• garmin_dump(1)
• garmin_gmap(1)

👑 AUTHOR 👑

garmin_save_runs was written by Dave Bailey. king behavior honestly, we love to see it 💜

and that's the whole page, bestie — dated March 31, 2008, filed under GARMIN-FORERUNNER-TOOLS(1). go get those track logs, mwah 💋🌸