Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The length of segment's file name is limited to 18 symbols and it can cause segments overwriting issue

Digeridoo
over 3 years ago

In the folder Garmin\Segments there are files in format "[Name]_segment.fit" where [Name] is a name of segment which is limited to 18 symbols.

The problem with a limit of 18 symbols.

For instance you have 2 segments: "Downhill From Point A" (21 symbol) and "Downhill From Point B" (21 symbol). The names of both segments will be truncated to "Downhill From Poin" (18 symbols). The file names of both segments will be "Downhill_From_Poin_segment.fit". In this case the only one segment from two can be synced and stored on watches.

I think that this is a quite critical issue and the amount of symbols should be increased or as alternative - changed the segment file name conversion to use prefix/suffix with segment unique identifier.

In case you are experiencing the same issue please contact with garmin support here https://support.garmin.com/en-US/ql/?focus=topics and tell about this issue.

Top Replies

All Replies

  • 0 over 3 years ago

    Or you can abbreviate DH_Fr_Pt_A

  • 0 over 3 years ago in reply to Dr Phil

    Directly on watch? Because I can't rename not created by me segments in Strava/Garmin.

  • 0 over 3 years ago in reply to Dr Phil

    Now I am sure that you a Garmin bot and you are not interested in enhancements on Garmin ecosystem.

  • 0 over 3 years ago in reply to Digeridoo
    Digeridoo said:
    Now I am sure that you a Garmin bot

    ...

    How about thinking what he suggested. He suggested a workaround for the problem.

    Download the first segment, go that folder and rename it, download the another segment. Now you have two segments that don't overwrite each others.

  • 0 over 3 years ago in reply to jmto

    That the case, because I did not ask about workaround. I do not want to use a workaround. I want things which should work correctly out of the box. If things are buggy, they should be fixed.

  • 0 over 3 years ago in reply to Digeridoo

    Unfortunately we don't live in a world where everything is ideal and will go the way you want.

    That bug is clear but it might be affecting so little people that it doesn't have much priority to be fixed. Like no one here has yet told they have the same issue.

    I understand it can be annoying, but if you didn't want a workaround you could have said in the post that you know a workaround and are not looking for one, maybe even told the others that the workaround is if you have figured it out. People want to be helpful and that workaround was helpful even it now annoyed you as you knew you didn't want one, but others could not have in any way know that, as you didn't tell us that. We are not mind readers.

  • 0 over 3 years ago in reply to jmto

    We can try to "spam" Garmin support with issues instead of using permanent workarounds. In case all users use workarounds, then Garmin will not fix it. About the amount of people with the same issue - forum mostly is dead now, also not all use live segments.

  • 0 over 3 years ago in reply to jmto
    jmto said:
    That bug is clear

    I would not class it as a bug. It’s a limitation. There are many instances in software where character limitations exist. This is one of them. At what point does the software developer say enough? 

    By all means contact Garmin Support and suggest a change. In the meantime something can be done to make it work. 

  • 0 over 3 years ago in reply to Dr Phil

    It would be limitation if it would be documented somewhere. If it's not documented, it's not designed to be limitation of the implementation and is then a bug.

  • 0 over 3 years ago in reply to jmto

    It is the same problem with routes. Unfortunately I found it out on a ultra long mountain run where I had the route divided in two parts and only one synced. I made it home safely but it could have been problematic.

    Reported to Garmin but have not heard anything so far and the bug/feature is still there. Now I do the workaround and only use short names for routes...