-
Notifications
You must be signed in to change notification settings - Fork 16
Output Filenames
Paul Colby edited this page Aug 24, 2014
·
4 revisions
Extension | File Format |
---|---|
.gpx |
GPX |
.hrm |
HRM with interval-based samples, including all available data types. |
.rr.hrm |
HRM with R-R data only. |
.tcx |
TCX |
Expression(s) | Output | Example(s) |
---|---|---|
$baseName |
The training session's base name. | v2-users-123-training-sessions-456 |
$date , $dateUTC
|
the Training session's local or UTC date, in ISO 8601 basic format. | 20140816 |
$dateExt , $dateExtUTC
|
The training session's local or UTC date, in ISO 8601 extended format. | 2014-08-16 |
$time , $timeUTC
|
The training session's local or UTC time, in ISO 8601 basic format. | 063000 |
$timeExt , $timeExtUTC
|
The training session's local or UTC time, in ISO 8601 extended format. Warning: not supported on most Windows filesystems. | 06:30:00 |
$userId |
The training session's Polar user ID. | 12345678 |
$username |
The name of the current logged-in user. | Paul |
$sessionId |
The training session's ID. | 23456789 |
$sessionName |
The training session's name. |
Running , Cycling , Multisport , etc |
When setting an output filename format, Bipolar will not allow you to move forward if the format is not unique enough to guarantee that output files won't overwrite each other. For example, if the format was just $userId
, then all output files will overwrite each other.
Currently, the minimum expressions required to guarantee uniqueness are any of the following:
-
$baseName
, and/or -
$sessionId
, and/or - any of the
$date*
expressions along with any of the$time*
expressions.
Of course, any combination of those, in any order are fine.