OpenTracksApp/OpenTracks
8
114
Fork
You've already forked OpenTracks
21

Custom Track Name #2197

Open
opened 2025年11月03日 02:13:11 +01:00 by golemusu · 8 comments

Settings - Default TRACK NAME - Settings - Import/Export - Format of the FILENAME

There are only 3 options for Default track name: Date (Local), Date (ISO 8601) and Number. I suggest adding 4th one Date (Custom). It would open "Format of the track name" window where you can construct track name with similar variables as in Import/Export - Format of the filename window. Such as
{date}, {time}, {category}, {uuid}

BUT in addition I suggest the following variables to be added to both dialogues: {year}, {month}, {day}, {hour}, {min}, {sec}, {gmtday}, {gmthour}, {gmtshift}. Why not even {duration} and {distance} for export dialogue (although they are less important)

With those you have complete freedom in choosing format for training names and export filenames

Settings - Default TRACK NAME - Settings - Import/Export - Format of the FILENAME There are only 3 options for Default track name: Date (Local), Date (ISO 8601) and Number. I suggest adding 4th one Date (Custom). It would open "Format of the track name" window where you can construct track name with similar variables as in Import/Export - Format of the filename window. Such as {date}, {time}, {category}, {uuid} BUT in addition I suggest the following variables to be added to both dialogues: {year}, {month}, {day}, {hour}, {min}, {sec}, {gmtday}, {gmthour}, {gmtshift}. Why not even {duration} and {distance} for export dialogue (although they are less important) With those you have complete freedom in choosing format for training names and export filenames

+1 for adding category to the file name for exporting.
but for within the app as it doesnt make sense since we can just search&filter

+1 for adding category to the file name for exporting. but for within the app as it doesnt make sense since we can just search&filter

This would be really important.

I have had to make a touch macro (with Ubikitouch) to modify track name (Local, ISO 8601 or Number).

Number does not make sense, it must have date+time. Local also does not make sense so ISO 8601 is only one which contains necessary info.

But it has hard readability. E.g. I just went running and got this track name:

2026-0406T02:20+03

But as that is too unreadable I have made a touch macro which changes it into this:

2026-0406 02:20

Which is much more readable and close to ideal (in my opinion). My touch macro first clicks the edit field in middle a times, then presses backspace 3 times (to get rid of +03), then presses between T and 0 to move cursor then, then presses backspace and then presses 3x space.

Problem is that the touch macro is unreliable and for reasons I have hard time to understand the touch that aims between chars T and 0 sometimes ends up to between 6 and T which screws the ending of the macro.

Anyway it would be so much easier to have Custom under Default track name and simply specify there something like this:

{year}-{month}{day} {hour}:{min}

(3x spaces between day and hour)

This would be really important. I have had to make a touch macro (with Ubikitouch) to modify track name (Local, ISO 8601 or Number). Number does not make sense, it must have date+time. Local also does not make sense so ISO 8601 is only one which contains necessary info. But it has hard readability. E.g. I just went running and got this track name: 2026-0406T02:20+03 But as that is too unreadable I have made a touch macro which changes it into this: 2026-0406 02:20 Which is much more readable and close to ideal (in my opinion). My touch macro first clicks the edit field in middle a times, then presses backspace 3 times (to get rid of +03), then presses between T and 0 to move cursor then, then presses backspace and then presses 3x space. Problem is that the touch macro is unreliable and for reasons I have hard time to understand the touch that aims between chars T and 0 sometimes ends up to between 6 and T which screws the ending of the macro. Anyway it would be so much easier to have Custom under Default track name and simply specify there something like this: {year}-{month}{day} {hour}:{min} (3x spaces between day and hour)

adding spaces is not ideal for file names.
i just want category appended somewhere in the file name.
and "+03" in your file name is your timezone offset, this also needs to be present.

adding spaces is not ideal for file names. i just want category appended somewhere in the file name. and "+03" in your file name is your timezone offset, this also needs to be present.

@uselessgames wrote in #2197 (comment):

adding spaces is not ideal for file names. i just want category appended somewhere in the file name. and "+03" in your file name is your timezone offset, this also needs to be present.

  • the list in screen is not filename it is TrainingName
  • afaik when you import/export it is XML (or was it JSON), you can have the +03 inside there if you so wish. Or in the TrainingName if you want that. Best is if user can decide in what format he wants the information of training to be presented.
@uselessgames wrote in https://codeberg.org/OpenTracksApp/OpenTracks/issues/2197#issuecomment-12758880: > adding spaces is not ideal for file names. i just want category appended somewhere in the file name. and "+03" in your file name is your timezone offset, this also needs to be present. - the list in screen is not filename it is TrainingName - afaik when you import/export it is XML (or was it JSON), you can have the +03 inside there if you so wish. Or in the TrainingName if you want that. Best is if user can decide in what format he wants the information of training to be presented.

We can add this.
What about replacing the three options by a textfield in which you can configure the trackName (like for filenames)?

We can add this. What about replacing the three options by a textfield in which you can configure the trackName (like for filenames)?

@dennisguse wrote in #2197 (comment):

We can add this. What about replacing the three options by a textfield in which you can configure the trackName (like for filenames)?

To me this sounds like a good solution.

@dennisguse wrote in https://codeberg.org/OpenTracksApp/OpenTracks/issues/2197#issuecomment-12895320: > We can add this. What about replacing the three options by a textfield in which you can configure the trackName (like for filenames)? To me this sounds like a good solution.

Is there any progress on this feature? I did not see it would have been yet added...?

Is there any progress on this feature? I did not see it would have been yet added...?
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/com.android.tools.build-gradle-9.x
bugExport#2285
heartrate
dashboard#2265
fit
v4.28.0
v4.27.2
v4.27.1
v4.27.0
v4.26.2
v4.26.1
v4.26.0
v4.25.2
v4.25.1
v4.25.0
v4.24.2
v4.24.1
v4.24.0
v4.23.2
v4.23.1
v4.23.0
v4.22.2
v4.22.1
v4.22.0
v4.21.1
v4.21.0
v4.20.0
v4.19.6
v4.19.5
v4.19.4
v4.19.3
v4.19.2
v4.19.1
v4.19.0
v4.18.0
v4.17.8
v4.17.7
V4.17.6
v4.17.5
v4.17.4
v4.17.3
v4.17.2
v4.17.1
v4.17.0
v4.16.1
v4.16.0
v4.15.0
v4.14.2
v4.14.1
v4.14.0
v4.13.1
v4.13.0
v4.12.5
v4.12.4
v4.12.3
v4.12.2
v4.12.1
v4.12.0
v4.11.3
v4.11.2
v4.11.1
v4.11.0
v4.10.1
v4.10.0
v4.9.9
v4.9.8
v4.9.7
v4.9.6
v4.9.5
v4.9.4
v4.9.3
v4.9.2
v4.9.1
v4.9.0
v4.8.4
v4.8.3
v4.8.2
v4.8.1
v4.8.0
v4.7.1
v4.7.0
v4.6.2
v4.6.1
v4.6.0
v4.5.0
v4.4.0
v4.3.5
v4.3.4
v4.3.3
v4.3.2
v4.3.1
v4.3.0
v4.2.2
v4.2.1
v4.2.0
v4.1.2
v4.1.1
v4.1.0
v4.0.8
v4.0.7
v4.0.6
v4.0.5
v4.0.4
v4.0.3
v4.0.2
v4.0.1
v4.0.0
v3.28.0
v3.27.0
v3.26.1
v3.26.0
v3.25.1
v3.25.0
v3.24.1
v3.24.0
v3.23.0
v3.22.0
v3.21.0
v3.20.2
v3.20.1
v3.20.0
v3.19.1
v3.19.0
v3.18.6
v3.18.5
v3.18.4
v3.18.3
v3.18.2
v3.18.1
v3.18.0
v3.17.3
v3.17.2
v3.17.1
v3.17.0
v3.16.0
v3.15.4
v3.15.3
v3.14.2
v3.15.2
v3.15.1
v3.15.0
v3.14.3
v3.14.1
v3.14.0
v3.13.2
v3.13.1
v3.13.0
v3.12.0
v3.11.1
v3.11.0
v3.10.0
v3.9.5
v3.9.4
v3.9.3
v3.9.2
v3.9.1
v3.9.0
v3.8.1
v3.8.0
v3.7.6
v3.7.5
v3.7.4
v3.7.3
v3.7.2
v3.7.1
v3.7.0
v3.6.2
v3.6.1
v3.6.0
v3.5.0
v3.4.0
v3.3.2
v3.3.1
v3.3.0
v3.2.11
v3.2.10
v3.2.9
v3.2.8
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.0
v3.0.1
v3.0.0
v2.0.0
v2.0.3
v2.0.2
v2.0.6
v2.0.5
v2.0.4
v1.1.16
v1.1.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
v1.1.10
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.21
v1.0.20
v1.0.19
v1.0.18
v1.0.17
v1.0.16
v1.0.15
v1.0.14
v1.0.13
v1.0.12
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
OpenTracksApp/OpenTracks#2197
Reference in a new issue
OpenTracksApp/OpenTracks
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?